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
It would be --metacat-query xxx and would basically be equivalent to: -e SAM_PROJECT=$(ddisp project create xxx)
which would start the project with data_dispatcher at launch time and pass its ID in SAM_PROJECT, letting the compatability
code in ifdhc 2_7 and later use data dispatcher calls to get the next file, etc.
Users would need data_dispatcher and metacat setup to use this.
The text was updated successfully, but these errors were encountered:
Request: Add Classad Attribute or ENV that indicates in the job which data handler we're using (SAM or Metacat). We should coordinate this with POMS, fife_wrap, fife_launch, FIFE devs.
We should try to isolate the metacat-specific (and while we're at it, the SAM-specific code). So our get_parser.py would, for example from metacat import BLAH) would have this arg (--metacat-query xxx`), call BLAH. The same could be done for SAM-specific options.
shreyb
removed
the
proposed
Hasn't been reviewed by the jobsub team. Don't do these until post-review (and then remove label)
label
Dec 18, 2024
It would be
--metacat-query xxx
and would basically be equivalent to:-e SAM_PROJECT=$(ddisp project create xxx)
which would start the project with data_dispatcher at launch time and pass its ID in SAM_PROJECT, letting the compatability
code in ifdhc 2_7 and later use data dispatcher calls to get the next file, etc.
Users would need data_dispatcher and metacat setup to use this.
The text was updated successfully, but these errors were encountered: