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
Use JSON file instead of csv/tsv as input metadata file.
Just talked to some of the people at DTU who developed anti-smash and they mentioned that using csv files can lead to unexpected outcomes/ errors that may be harder to catch when you start scaling your pipeline. Some of our most common errors arise from using this format. We should consider switching to JSON instead. This will require lots of changes:
Integrate json into Nextflow
Allow users to manually add things that are converted to json (maybe something like ALE sheets)
Add checks on data types
The text was updated successfully, but these errors were encountered:
Use JSON file instead of csv/tsv as input metadata file.
Just talked to some of the people at DTU who developed anti-smash and they mentioned that using csv files can lead to unexpected outcomes/ errors that may be harder to catch when you start scaling your pipeline. Some of our most common errors arise from using this format. We should consider switching to JSON instead. This will require lots of changes:
The text was updated successfully, but these errors were encountered: