-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Cli #1444
Remove Cli #1444
Changes from all commits
8e990a1
0b4fef7
19da536
d20c9f8
15320ff
4e960b9
ffdcac7
080d774
27eb412
668786e
a2cba87
59823df
88d19af
2dc11a8
9c4079a
f2e0dd4
6bb5df7
2eb913b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,9 +18,6 @@ API | |
.. toctree:: | ||
spots/index.rst | ||
|
||
.. toctree:: | ||
recipe/index.rst | ||
|
||
.. toctree:: | ||
types/index.rst | ||
|
||
|
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -75,20 +75,6 @@ origin. At this point, it's trivial to create a cell x gene matrix. | |
|
||
tutorials/exec_feature_identification_and_annotation.rst | ||
|
||
Putting Together a Pipeline Recipe and Running it | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are we dropping the recipe runner? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I took out all the recipe stuff :/ should leave the runner in? |
||
------------------------------------------------- | ||
|
||
Pipeline recipes should describe the computational steps to get from the input files to the output files. Pipeline | ||
recipes should manage file input and output through the injected ``file_inputs`` and ``file_outputs`` variables. When a | ||
recipe is executed, the user should provide a list of file paths or URLs, which are loaded as starfish objects (i.e., | ||
:ref:`ImageStack`, :ref:`Codebook`, :ref:`IntensityTable`, or :ref:`ExpressionMatrix`), and provided to the recipe in | ||
the ``file_inputs`` array. Correspondingly, any results saved to the ``file_outputs`` array will be written to the | ||
file paths users provide. | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
|
||
tutorials/exec_running_a_pipeline.rst | ||
|
||
Old Content not to be deleted yet. | ||
---------------------------------- | ||
|
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can plausibly remove the Makefile rules for running
.sh
data processing examples.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ping
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed!