Jonathan Manning

Great- thanks, I'll do that. I'd like to be able to have default override the faking in all cases (even if the default is set to an empty value). Probably...

Okay, so behaviour right now is like: ``` >>> from jsf import JSF >>> test_schema {'type': 'object', 'properties': {'test_field': {'type': 'string', 'default': 'default value'}}, 'required': ['test_field']} >>> JSF(test_schema).generate() {'test_field': 'quas...

+1

I [think]( https://github.com/refgenie/refgenie/issues/251) that the one-file-per asset solution, or maybe per assembly to keep dependency handling simpler, with a final index or agglomerate may be sufficient, and would keep things...

As a first step, just allowing a merge of arbitrary refgenie databases would allow work-arounds. For our use case we could assemble the assets associated with each assembly in separate...

A bit tangenital, but just to stress the point, I do think structured metadata is crucial, so you can do the queries like: "Hi Refgenie, give me a Salmon index...

Ahh- glad to hear that's the way you're thinking anyway, hopefully we can find a way of making something similar happen.

Thanks @stolarczyk , I'm testing this now and will get back to you.

I'm assuming (and some initial testing seems to confirm) that dependencies of the indexing operations (fasta, fasta_txome) do need to exist in the central database before the indexing operations. So,...

Step 4 above is giving me the familiar error: ``` > refgenie build --reduce -c /path/to/genome_config.yaml Running the reduce procedure. No assets will be built. Reducing 21 configs 0% -:--:--Traceback...