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
The abagen.get_expression_data() function is the primary workflow of use in the abagen toolbox. Right now, everything else in the toolbox (besides the abagen.mouse module) supports that function. It might be nice, therefore, to allow access to the function via the command line instead of having to use it from within a Python terminal session for those who are less comfortable with Python.
Proposed solution
Add a CLI for abagen.get_expression_data() that allows users to point to their atlas image file and specify an output CSV file for the dataframe(s) returned by the function. I'm imaging something like:
abagen --output expression.csv my_atlas.nii.gz
which would use my_atlas.nii.gz to generate a region x gene dataframe that is saved to expression.csv in the current directory.
All the parameters of the function should be accessible via optional arguments to the function, and I am happy to discuss / iterate on the actual command name itself, but this might be a nice feature for some users!
The text was updated successfully, but these errors were encountered:
The issue
The
abagen.get_expression_data()
function is the primary workflow of use in theabagen
toolbox. Right now, everything else in the toolbox (besides theabagen.mouse
module) supports that function. It might be nice, therefore, to allow access to the function via the command line instead of having to use it from within a Python terminal session for those who are less comfortable with Python.Proposed solution
Add a CLI for
abagen.get_expression_data()
that allows users to point to their atlas image file and specify an output CSV file for the dataframe(s) returned by the function. I'm imaging something like:which would use
my_atlas.nii.gz
to generate a region x gene dataframe that is saved toexpression.csv
in the current directory.All the parameters of the function should be accessible via optional arguments to the function, and I am happy to discuss / iterate on the actual command name itself, but this might be a nice feature for some users!
The text was updated successfully, but these errors were encountered: