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
for example gives me a link to request manager and has the user decided what is what.
can it be made that the exact only configuration that lead to the file creation is linked ? reqmgr has all the needed information. Is that "just" a matter of having a /config4dataset API somewhere ?
The text was updated successfully, but these errors were encountered:
Jean-Roch, I'm not sure I understand your question. Could you please elaborate more on what exactly do you expect to be seen on DAS web page. So far, for this particular dataset, DAS provides three configurations:
What do you mean by /config4dataset API, where it should be, which parameters it should accept, what it should return? The configuration files are part of CouchDB, so there is not specific API to get it and we can't add API to CouchDB. We only have the id of the document which holds content of the configuration. This is why on DAS page we return links to CouchDB documents.
looking at this again after some time, thinking that this would be ironed out by now, looks like things are not wired too properly just yet.
https://cmsweb.cern.ch/das/request?instance=prod/global&input=config+dataset%3D%2FRelValTTbar_14TeV%2FCMSSW_12_6_0_pre4-PU_125X_mcRun3_2022_realistic_v4-v1%2FMINIAODSIM
for example gives me a link to request manager and has the user decided what is what.
can it be made that the exact only configuration that lead to the file creation is linked ? reqmgr has all the needed information. Is that "just" a matter of having a
/config4dataset
API somewhere ?The text was updated successfully, but these errors were encountered: