-
Notifications
You must be signed in to change notification settings - Fork 272
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
Add docs for different config profiles #6
Comments
How about storing these centrally here together with the configs and simply refer to this repository, explaining why these are kept separately ? |
Thats what I was thinking. So we can put them in If someone decides to add a custom config how much do we push to provide documentation too? It would be nice to have one per custom config but do we expect everyone to be able to write a markdown document? Maybe we provide a template in |
Yes, sounds good. I would think writing Markdown is pretty easy these days (even online WYSIWYG editors exist), so why not push for writing some basic lines describing the config then? |
This issue that we're commenting on here is on |
I moved the issue from |
Note that I think |
I have added the docs for the Crick in the We need to add docs for the rest of the configs currently hosted in the repository for consistency. Also, need to reference the documentation for these profiles in Im not sure whether its possible to get a dynamic listing of all the available profiles available to use when running the pipeline but that would be quite neat. |
Neat! Something like a git submodule that we integrate into the |
Thanks @apeltzer! I was thinking it would be nice if we could maybe automatically add the list of available profiles to the help string produced by the pipeline. Maybe we can add an extra description document in I'm not sure if nextflow currently checks that the name of the profile has to be valid. I'll test that. |
It would be super cool to maybe specify a little more how to use this config files in an existing/new nfcore solution. @apeltzer has a really nice code in nextflow.config. |
Considering that the list in the first comment is now completed already I am adding a list of configs (from https://github.com/nf-core/configs/tree/master/conf) which need to be documented still
Here's the template.md which can be used to create the docs for configs above. EDIT by @maxulysse update list of missing docs |
Friendly reminder: @FriederikeHanssen we're missing docs for the |
Yeah thats one for @yassineS - can't work on this at the moment unforrtunately as I'm not even near that cluster ;-) |
You're still listed as contact in the config, that's how I found you |
The cluster has been replaced by a new one, hpc1, but I will let @roberta-davidson comment. She is our resident expert now on all eager matters. |
Let me know if you need any advice/help @roberta-davidson! |
added in #470 , also cleaned up the |
The list should be edited to replace |
Custom configs are now hosted centrally at
nf-core/configs
. We need to think about where we host the documentation for running these config files. These are currently added on a per-pipeline basis but it would be good to also host them centrally so they are available to all pipelines.This will also probably involve refactoring the current docs to deal with this.
Documention to-do list:
The text was updated successfully, but these errors were encountered: