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
Currently, all calculated metrics are written to an assessment_datasets.json file for each tool. In order to plot summary statistics outside OEB we'll sooner or later need to convert the json format into a table/dataframe, in order to tackle issues #245#290
Possible solutions
Write tsv files in parallel to the assessment json file in compute_metrics.py
advantage: if metric names change in a way that requires changes in parsing, this can be taken care of in the same script
disadvantage: script compute_metrics.py gets even more crowded
Read assessment json and convert to tsv; module in utils directory.
advantage: clean structure, clear separation of functions
disadvantage: if metric names change, parsing might be broken; debugging/updating more difficult to track
Other suggestions welcome!
If you have an opinion please comment 🙏
The text was updated successfully, but these errors were encountered:
Problem
Currently, all calculated metrics are written to an
assessment_datasets.json
file for each tool. In order to plot summary statistics outside OEB we'll sooner or later need to convert the json format into a table/dataframe, in order to tackle issues #245 #290Possible solutions
compute_metrics.py
compute_metrics.py
gets even more crowdedOther suggestions welcome!
If you have an opinion please comment 🙏
The text was updated successfully, but these errors were encountered: