Originally Lobster was assumed to be installed on top of a CMSSW release, and it would try to be smart about figuring out which release that was and using the information if you didn't specify it yourself (e.g. specifying the sandbox). Now that Lobster is not installed inside of a CMSSW release, we should remove any of the release detection intelligence and make sandbox a mandatory parameter of Workflow.
btovar
commented
2 months ago
Originally Lobster was assumed to be installed on top of a CMSSW release, and it would try to be smart about figuring out which release that was and using the information if you didn't specify it yourself (e.g. specifying the
sandbox). Now that Lobster is not installed inside of a CMSSW release, we should remove any of the release detection intelligence and makesandboxa mandatory parameter ofWorkflow.