You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was talk in the past about putting GMS in front of all pipelines as part of branding.
The main argument against that was that it's possible to infer origin pretty easily without the prefix, just like how its done for most bioinformatical software. Nonetheless, it meant that some software ended up with a gms prefix, and some didn't.
The 16s_emu name isn't a great name, as evidenced by the fact that it's colloquially known as "the 16s pipeline".
As for naming suggestions I'd probably go with some variation of "EmuTax" cause its accurate but funny.
I asked ChatGPT for "Can you suggest some nice project names for a bioinformatics tool that does typing of bacteria and fungi based on 16 or ITS or similar schemes, using a tool named Emu, but preferrably not tied to the specific scheme or tool?", and got a few that don't seem terrible:
MicroMatcher
TypEmu
StrainPlane
(Threw away many more that were either too general or already very occupied names)
Same question to Claude:
Taxonix
MicroID
StrainSage
Genovista
I'm sure one can do some variations of these as well.
The project name, gms_16s, is highly descriptive, but I feel there are two slight problems with the name:
In a whim, I was thus playing around with names that is more of a stand-alone name, and connects to its roots. I came up with these:
Thoughts? Other ideas?
The text was updated successfully, but these errors were encountered: