The discrepency is due to historical changes in th...
# modules
j
The discrepency is due to historical changes in the nf-core modules specifications: 1. Originally it was decided to strictly split every file into a separate channel (being passed 'together' via
.multiMap()
sub channels) 2. However a lot of newcomers complained, so it was relaxed slightly for directly relevant index files to go alongside the main file. So newly made modules have this, and some that have been updated will have been updated. So we are wanting plug-and-play, but the modules get out of sync due to when they were made or updated
βœ… 1
m
I thought Fredrick mainly complained about the input format actually
I think Fredrick is on the right track to #team-maintainers
j
Didn't I respond with the same background as you πŸ˜…
f
I did
sync
some of my works in progress and ended up breaking almost 50% of my mapping/variant-calling processes. I was confused at first. Then started opening the main scripts and scouting..
πŸ‘ 1
j
Yeah I never trust that πŸ˜†
No one wants to go/have time through all >30 samtools modules to standardise the input/output channels sadly
l
This could be a project for the next Hackathon !
m
did someone say
samtools
? πŸ‘€
a
πŸ’― seems like low-hanging fruit/nice entry level with impact? Greater standardisation (at least between subtools although ideally across nf-core) makes the modules much more usable!
πŸ’― 2
m
give me some time to ask Ben what he thinks we should be aiming for, but I'm all for consistency
πŸ‘ 1
m
one tuple to rule them all?
πŸ‘ 1
j
You can't break the specs entirely
a
Would be ideal if we could have some direction before the hackathon as that is typically a time of many new modules/module updates
m
I have a proposal, how about we describe the specs, we document it, and we version it
a
You mean version the module spec? I (and others) proposed this fairly recently
βž• 2
🫣 1
m
that way we now that module X follows specs v2, module Y follows specs v3, and we know what should be updated whenever we have something
yeah, not versioning the modules repo, but the module specs
You know Arthur, you should be a maintainer
party this 1
🧐 1
πŸ˜†
j
> You mean version the module spec? I (and others) proposed this fairly recently Don't worry it's coming! Just waiting on backend website updates so we can implement it properly πŸ™‚
πŸŽ‰ 1
πŸ‘€ 1