You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a substitution is created, it is not enought to simply run a job. Instead, the files in the substituted compendium must be updated. At least the display file will be different if a different data file is used.
This could happen by starting a job "in place", or by copying the files back to the compendium directory. In any case, this requires a specific type of job that only shares some steps with a regular job.
Required steps probably are image prepare, image build, image run, and copy file.
This job is started by the substituter.
muncher and informer should just as well work for providing read access and live updates for these kinds of jobs.
update API
jobs with type "overwrite"/"create_substitution"/... are not listed under /jobs
/jobs allows to filter to show only specific types, by default the type is "regular"/"check"/...
after creating a substitution it is a candidate compendium
if there is an error during the creation job, the compendium stays a candidate
if a compendium is candidate AND substituted: true, then...
the response does not contain the files property (because the files are not updated yet; but there is no access control to the files, a client may construct the URLs using file names from the base compendium..)
create issue in muncher for job types and filters (update the job model!)
implement & test
With all this in place, the substituter can then provide a comparison between base display file and substitution display file, see #121
The text was updated successfully, but these errors were encountered:
The user receives information that:
Files are substituted
The analysis has started/running/finished (including logs)
"Go to ERC" possible once the analysis is finished
What happens if the user closes the browser and comes back?
Assuming that the analysis continues in the background:
The list of compendia includes "substitution candidates" (different from normal candidates) which are currently running ERCs that emerged from a substitution.
A click on them shows a popup/window with the current logs. The user can see which step is currently ongoing.
This is the same if the analysis of the ERC failed. The user can see which step failed but does not get to the ERC view.
We provide the user with a notification that the ERC will appear in the list once the analysis is finished.
Should the substituted files not also be displayed to the user? I.e. the client shows the substituted and original files both in the listing and potentially with some side-by-side view (which could even solve #121)
nuest
transferred this issue from o2r-project/o2r-substituter
Oct 7, 2020
After a substitution is created, it is not enought to simply run a job. Instead, the files in the substituted compendium must be updated. At least the display file will be different if a different data file is used.
This could happen by starting a job "in place", or by copying the files back to the compendium directory. In any case, this requires a specific type of job that only shares some steps with a regular job.
Required steps probably are image prepare, image build, image run, and copy file.
This job is started by the substituter.
muncher and informer should just as well work for providing read access and live updates for these kinds of jobs.
/jobs
/jobs
allows to filter to show only specific types, by default the type is "regular"/"check"/...candidate
compendiumcandidate
ANDsubstituted: true
, then...files
property (because the files are not updated yet; but there is no access control to the files, a client may construct the URLs using file names from the base compendium..)With all this in place, the substituter can then provide a comparison between base display file and substitution display file, see #121
The text was updated successfully, but these errors were encountered: