-
Notifications
You must be signed in to change notification settings - Fork 0
Documentation development #74
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
Open
danieljbridges
wants to merge
7
commits into
main
Choose a base branch
from
docs/backup_share
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
ffc1d6f
Error message and tightening language
danieljbridges ecfe3ba
Additional FAQ
danieljbridges 5f30fd7
Expanded Usage into sub-sections inc backup and share
danieljbridges e49ac2e
Minor changes to headings
danieljbridges 8838021
Corrections
danieljbridges 077bf05
Changed variant caller default to delve
danieljbridges cc6c1ba
Clarified order of steps
danieljbridges File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,8 @@ | ||
| **Can I stop and restart `nomadic realtime`?** | ||
|
|
||
| Yes, you can safely stop and restart `nomadic realtime`. The program keeps track of what FASTQ files have been processed, and will continue processing from where it left off. | ||
|
|
||
| **Can I run more than one instance of `nomadic` at once?** | ||
|
|
||
| Yes, but if the process generates a webpage e.g. `nomadic dashboard` or `nomadic realtime`, only one will be live. You can run multiple instances of anything else e.g. `nomadic process` that doesn't have a dashboard. | ||
|
Collaborator
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. We can fix this probably easily, so that the dashboard can also be opened twice. |
||
|
|
||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
|
|
||
| To run *Nomadic* for a sequencing run, open a terminal window and type the following: | ||
|
|
||
| ``` | ||
| conda activate nomadic | ||
| cd <path/to/your/workspace> | ||
| nomadic realtime <expt_name> | ||
| ``` | ||
|
|
||
| - `<path/to/your/workspace>` should be replaced with the path to your *Nomadic* workspace. | ||
| - `<expt_name>` should be replaced with the name of your experiment. | ||
| - You should have given your experiment the same name in *MinKNOW*. | ||
| - You should have given your metadata file this name, and put it in your workspace metadata folder (`<path/to/your/workspace>/metadata/<expt_name>.csv|xlsx`). | ||
|
|
||
| The dashboard will open in a browser window on your computer. | ||
|
|
||
| <!-- 1. Create a workspace if you have not already (`nomadic start pfalciparum`). | ||
| 2. Pick an experiment name (e.g. `2025-06-21_first-sequencing`) | ||
| 3. Start your sequencing run with *MinKNOW* using your experiment name. | ||
| 4. Put your metadata file in the `metadata` folder in your *Nomadic* workspace. Name the file with your experiment name (e.g. `2025-06-21_first-sequencing.csv`). | ||
| 5. Start *Nomadic*: `nomadic realtime 2025-06-21_first-sequencing` --> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| ## Backing up | ||
|
|
||
| To create a complete backup of your workspace e.g. to an external hard disk drive or other location accessible on or from your computer (including an ssh location): | ||
|
|
||
| ``` | ||
| nomadic backup -t <path/to/your/backup/location> | ||
| ``` | ||
|
|
||
| The backup process will also backup all minknow data so be prepared for it to take a while the first time you run it. At the end you will see a short summary: | ||
|
|
||
|
|
||
| { .centered width="75%" } | ||
|
|
||
|
|
||
| ## Sharing data | ||
|
|
||
| The results folder for an experiment (`results/<expt_name>`) contains all the outputs from *Nomadic*. Only the CSV files starting `summary` and the `metadata` folder are required to relaunch the dashboard with the `nomadic dashboard` command (see [Basic Usage](basic.md)). `Nomadic` allows easy sharing of your workspace by copying key summary `Nomadic` and `MinKNOW` files to a new location, e.g. a cloud synchronised folder. | ||
|
|
||
| ``` | ||
| nomadic share -t <path/to/your/shared/location> | ||
| ``` | ||
|
|
||
| Once shared, `Nomadic` can be run by collaborators and other members of the group as needed. | ||
|
|
||
| ## Configuring default values | ||
|
|
||
| The above settings can be saved per workspace so that you don't need to enter the details each time. To save the configuration do the following: | ||
|
|
||
| ``` | ||
| nomadic configure share -t <path/to/your/backup/location> | ||
| nomadic configure backup -t <path/to/your/shared/location> | ||
| ``` | ||
|
|
||
| Once configured you can omit the `-t` option e.g. | ||
| ``` | ||
| nomadic share | ||
| nomadic backup | ||
| ``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
We usually have it in the order minknow, metadata, nomadic, as they can prepare the metadata file while minknow is already running and that gives time for the first samples to appear. What is your reason to switch the order?
If there is no strong reason, I would say let's stick to that order, as we also use it in the cheatsheet for example. We can mention that steps 1,2 can be done in any order.