Nathan Sheffield

maybe just to expand on this a bit... right now we have the "genome_description" field, but perhaps we need a more structured way to describe a genome (aka namespace), that...

yes we should.

what's the status of this?

Some notes on the concurrency issue: Can we make each asset build independent? So when you build an asset, you record the information in a separate yaml file for that...

Yeah -- nicely articulated. This is exactly my vision! I've written this in my grant applications, but so far, haven't been able to convince enough reviewers that it's a good...

the challenge I'm having is that these files are showing up in the git repo, since the config file I want to version control, but the data is pointing elsewhere.

it's the fasta asset. as far as I remember it was just exactly what's in the data of the final built assets... the default folder (tag folder), the refgenie build...

I can't explain what's going on there, then. Let me take a closer look at it.

is it possibly related to whether or not that genome already exists in the config and so is being re-initailized? I noticed that not all of them do this, and...

did you notice anything here in your last round of builds?