Git Product home page Git Product logo

Comments (20)

yassineS avatar yassineS commented on July 28, 2024 2

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.

from configs.

drpatelh avatar drpatelh commented on July 28, 2024 1

Thats what I was thinking. So we can put them in nf-core/configs/docs/configuration/? Thats where they are currently kept for other pipelines.

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 nf-core/configs and document that?

from configs.

ewels avatar ewels commented on July 28, 2024 1

I moved the issue from tools to configs 🎉 (thanks, new GitHub feature)

from configs.

ewels avatar ewels commented on July 28, 2024 1

Deleted your comment @apeltzer and added the list to the original post by @drpatelh so that we get a nice completion tick-list on the issues page.

from configs.

apeltzer avatar apeltzer commented on July 28, 2024 1

Yeah thats one for @yassineS - can't work on this at the moment unforrtunately as I'm not even near that cluster ;-)

from configs.

FriederikeHanssen avatar FriederikeHanssen commented on July 28, 2024 1

added in #470 , also cleaned up the -profile cfc docs

from configs.

apeltzer avatar apeltzer commented on July 28, 2024

How about storing these centrally here together with the configs and simply refer to this repository, explaining why these are kept separately ?

from configs.

apeltzer avatar apeltzer commented on July 28, 2024

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?

from configs.

ewels avatar ewels commented on July 28, 2024

@apeltzer:

How about storing these centrally here together with the configs and simply refer to this repository, explaining why these are kept separately ?

This issue that we're commenting on here is on tools - I'm guessing you mean on the configs repository?

from configs.

ewels avatar ewels commented on July 28, 2024

Note that I think nf-core/configs/docs/ would be fine for organisation. Could have a TEMPLATE.md if we really want? Or people can just look at the existing files.

from configs.

drpatelh avatar drpatelh commented on July 28, 2024

I have added the docs for the Crick in the nf-core/configs/docs/ folder. See #7

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 nf-core/tools template. This is what we have so far:
https://github.com/nf-core/tools/blob/dev/nf_core/pipeline-template/%7B%7Bcookiecutter.name_noslash%7D%7D/docs/usage.md#custom-resource-requests

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.

from configs.

apeltzer avatar apeltzer commented on July 28, 2024

Neat! Something like a git submodule that we integrate into the nf-core/tools package maybe? Not been using these too often, but it might be possible.

from configs.

drpatelh avatar drpatelh commented on July 28, 2024

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 nf-core/configs that contains the profile name and a brief help comment. This can then be parsed in nextflow.config and rendered in the help.

I'm not sure if nextflow currently checks that the name of the profile has to be valid. I'll test that.

from configs.

matq007 avatar matq007 commented on July 28, 2024

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.

from configs.

mihai-sysbio avatar mihai-sysbio commented on July 28, 2024

For Uppmax #53 and Hebbe #54 the CI seems to report the same issue. Is there a mismatch between the documentation and the changes in the PRs?

from configs.

abhi18av avatar abhi18av commented on July 28, 2024

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

  • cfc_dev.config
  • crg.config
  • gis.config
  • hebbe.config
  • phoenix.config

Here's the template.md which can be used to create the docs for configs above.

EDIT by @maxulysse update list of missing docs

from configs.

maxulysse avatar maxulysse commented on July 28, 2024

Friendly reminder:

@FriederikeHanssen we're missing docs for the cfc_dev config
@athbaltzis we're missing docs for the crg config
@ewels we're missing docs for the hebbe config
@yassineS and @apeltzer we're missing docs for the phoenix config

from configs.

maxulysse avatar maxulysse commented on July 28, 2024

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

from configs.

jfy133 avatar jfy133 commented on July 28, 2024

Let me know if you need any advice/help @roberta-davidson!

from configs.

mihai-sysbio avatar mihai-sysbio commented on July 28, 2024

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

The list should be edited to replace hebbe by vera (docs).

from configs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.