Open cmutel opened 5 years ago
Indeed. This is not limited to biosphere exchanges. Presamples generated in one project and reuse in another will almost inevitably lead to this error. I've dealt with this by regenerating presamples for new projects, which was a very temporary solution. I am against a short-term plug that simply ignores these errors, because users may think their exchanges are being overwritten by presamples, and would be hard-pressed to know they weren't until they analysed their results. At a strict minimum, if we do this, we should provide a list of unmapped exchanges. Other options I've considered are:
It is difficult to impossible to tell ahead of time which flows a given database will use, so instead of raising a mysterious error, we need to just ignore these flows. The error I get now is: