In Step 4 and 5 the validation and checking of the descriptor is shown using the zenodo ID (not the JSON file). However, if the tutorial is followed in order and I understood it correctly, by these steps we have not created a zenodo ID of our tool yet. Is there a reason why you didn't choose to demonstrate how the validation and checking works running bosh validate fsl-bet-final.json? Perhaps this is more consistent with the logical order of the tutorial.

The tutorial assumes familiarity with bash commands (e.g. commands like cat and grep are used but their purpose is not explained). Perhaps it would be nice to anticipate such background to the reader at the very beginning of the tutorial (and even link to some helpful tutorials like you did with JSON), or explain in more detail what these commands are doing when using them (e.g. add a sentence saying 'now we are going to display the contents of our edited JSON file' when using cat).

We are having problems with the computecanada bandwidth, the building takes longer than usual.

Sorry for the inconvenient,

Similar to this issue #11 - there are a few places where it's unclear what the expected level of familiarity with Python APIs is. It would be helpful to the reader if this expectation were clarified at the top of the notebook or if more verbose explanations were given throughout the notebook.

For instance, the user is shown how to use the bosh example command both on the command line and with the API. Instead of saying "Of course, this can all be reproduced with the Python API, for instance", there could be an explanation about arguments having to be passed in the same order on the command line as they are when using the Python API.

Likewise, it might be helpful to be more verbose when explaining that descriptor2func is a library within the overarching Boutiques module, and it has its own set of commands. The python function created by passing a Zenodo DOI to the command function is the main function corresponding to the tool associated with the DOI .

Thank you @martinagvilas for agreeing to review this submission. You can find our guidelines for review here. When your review is completed, please leave a comment on this issue saying so. If there are unresolved issues that you believe to be impeding the acceptance of the repository, please list them here.

Thank you @llevitis for agreeing to review this submission. You can find our guidelines for review here. When your review is completed, please leave a comment on this issue saying so. If there are unresolved issues that you believe to be impeding the acceptance of the repository, please list them here.

Please push on neurolibre and share the link here, so we can share with reviewers

need to check:

• docker build file
• data requirements

Hi! Thanks for submitting this very useful tutorial of boutiques.

Here goes my first issue:

When running the command bet -h in the tutorial I obtain a CalledProcessError. Specifically, I get the following output (after the printout of the command line options of bet):

When executing nifti_plotter I get a Future Warning. In detail: