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
Many medium datasets, especially those published in nii.gz, provide meta information (such as sex, age, manufacturer, etc.) in the form of a CSV spreadsheet or JSON. Currently, in AMID, we have two ways of unpacking these CSVs and creating dataset fields:
The first option is cleaner as it does not require writing repetitive code:
deffield_name(_meta):
return_meta[field_name]
However, the second option results in explicitly defined methods, allowing the addition of docstrings, and visibility in documentation. For instance, right now, AMOS has many fields not visible in the documentation:
Which of these two options should we prefer?
The text was updated successfully, but these errors were encountered:
Many medium datasets, especially those published in nii.gz, provide meta information (such as sex, age, manufacturer, etc.) in the form of a CSV spreadsheet or JSON. Currently, in AMID, we have two ways of unpacking these CSVs and creating dataset fields:
The first option is cleaner as it does not require writing repetitive code:
However, the second option results in explicitly defined methods, allowing the addition of docstrings, and visibility in documentation. For instance, right now, AMOS has many fields not visible in the documentation:
Which of these two options should we prefer?
The text was updated successfully, but these errors were encountered: