Open germanfgv opened 1 year ago
Users have noticed that after file invalidations, DAS still displays blocks and dataset runs data as if the files were still there
Lets use dataset /DisplacedJet/Run2023C-PromptReco-v2/MINIAOD as an example. This dataset initially included files from run 367661, but they were all invalidated, as can be seen here: https://cmsweb.cern.ch/das/request?view=list&limit=50&instance=prod%2Fglobal&input=file+dataset%3D%2FDisplacedJet%2FRun2023C-PromptReco-v2%2FMINIAOD+run%3D367661
Nonetheless, run 367661 still appears in DAS as belonging to the dataset: https://cmsweb.cern.ch/das/request?view=list&limit=50&instance=prod%2Fglobal&input=run+dataset%3D%2FDisplacedJet%2FRun2023C-PromptReco-v2%2FMINIAOD
This issue is already being addressed by a new DBS development: https://github.com/dmwm/dbs2go/issues/99
As DAS default behaviour is to only show valid files, it needs to be adjusted so it uses the new capabilities of the DBS API
FYI: @vkuznet @d-ylee
Users have noticed that after file invalidations, DAS still displays blocks and dataset runs data as if the files were still there
Lets use dataset /DisplacedJet/Run2023C-PromptReco-v2/MINIAOD as an example. This dataset initially included files from run 367661, but they were all invalidated, as can be seen here: https://cmsweb.cern.ch/das/request?view=list&limit=50&instance=prod%2Fglobal&input=file+dataset%3D%2FDisplacedJet%2FRun2023C-PromptReco-v2%2FMINIAOD+run%3D367661
Nonetheless, run 367661 still appears in DAS as belonging to the dataset: https://cmsweb.cern.ch/das/request?view=list&limit=50&instance=prod%2Fglobal&input=run+dataset%3D%2FDisplacedJet%2FRun2023C-PromptReco-v2%2FMINIAOD
This issue is already being addressed by a new DBS development: https://github.com/dmwm/dbs2go/issues/99
As DAS default behaviour is to only show valid files, it needs to be adjusted so it uses the new capabilities of the DBS API
FYI: @vkuznet @d-ylee