v1.0

(from [2753b71b85f4706448607d54a1a390b2811b9db3]) moa show now shows if a variable is defined by a parent (recursively) [#19 state:resolved] https://github.com...

fixing this is weird - it makes thinks more complicated than need be -

I suggest that in templates we'll try to use better names for parameters -

and, possibly,...

(from [7f0ecf34207d28a173f5cce22d78573623cfff72]) Merge branch 'moa.0.10' of git@ssh.github.com:mfiers/Moa into moa.0.10

• 'moa.0.10' of git@ssh.github.com:mfier...

(from [7f0ecf34207d28a173f5cce22d78573623cfff72]) Merge branch 'moa.0.10' of git@ssh.github.com:mfiers/Moa into moa.0.10

• 'moa.0.10' of git@ssh.github.com:mfier...

i.e.
show undefined vars
show inhertied vars!!!

(from [665824fcbcea8f4ec31a7b02bfd25f547143959d]) reworked - better handling of background & recursive execution [#4] https://github.com/mfiers/Moa/commit/6658...

gsMapper is broken and I dont know why

[Cfljam@pgenome 20.gsMapper]$ pwd /data/moa/onion/11.Colour_CGs/10.AcMyb1/20.gsMapper [Cfljam@pgenome 20.gsMapper]$ moa r...

(from [64332d4f5d86d7b41bde6af9b26b370036635e2a]) first implement of moa archive [#3 state:resolved] https://github.com/mfiers/Moa/commit/64332d4f5d86d7b41bde6...

Think I have a solution - make only those vars inheritable that are either defined as being inheritable or NOT in the template definition.

Thus: 'db' would be i...

(from [aafec650386b97ba19737a36ba1ec06b0094443e]) refactoring of commands callbacks. Implemented "moa run -r" [#4 state:resolved] https://github.com/mfiers/Moa...

I agree - that is somewhat confusing... need to think about that one..

I would typically organize such jobs in leaf nodes:

./10.download.from.ncbi ./20.create.b...

Creating a new blast job inside a directory calling data from NCBI leads to apparent inheritance of variables from higher level directory...
ie (blast) db is se...

Working!

(from [b3bf9a920fd70f29643a6c72b97092634679e47f]) moa unset -r implemented + a general framework for recursive execuction in moa.utils.moaRecursiveWalk - in pre...

(from [fe5c52e92320f51683a2dd4bcd31504df31b8f0a]) recursive config loading + non recursive template variables [#6 state:resolved] https://github.com/mfiers/Moa...

(from [91fb4abd20775d93923a47a4f20caa95b9fea0f4]) removed title parameter from templates and defined it in the "doc" plugin" [#7] https://github.com/mfiers/Moa...

(from [fa8bcfa031b657faba66818918028f5ec000f8da]) start of a "doc" plugin that unifies all documentation - implemented "moa blog" [#7] https://github.com/mfier...

(from [64feb64d48d68ce78eb6c21476f3f13e466bd3a5]) command tests from moa simple & moa map [#16] https://github.com/mfiers/Moa/commit/64feb64d48d68ce78eb6c21476...

this will make Moa installable on any machine that runs python - instead of it being an ubuntu specific package..

Don't really see the need for this - no advantage to create moa mv above a regular mv.... so -invalidating this..

(from [6e507865c757c528f84b98d9150bf6fc07913226]) moa cp -r seems to work ([#1 state:resolved]). https://github.com/mfiers/Moa/commit/6e507865c757c528f84b98d91...

(from [d96e03465d46bef27c7cf5fb7c2f430b84438efb]) Merge branch 'moa.0.10' of git@ssh.github.com:mfiers/Moa into moa.0.10

• 'moa.0.10' of git@ssh.github.com:mfier...

(from [e965f77c62942e2990d1aae07049e0bd7112991c]) updated the README file [#12 state:resolved] https://github.com/mfiers/Moa/commit/e965f77c62942e2990d1aae0704...

Nothing to be done - just testing integration with Github

allow 'blog posts' to be added to the moa.description - easy additions of descriptions to a job

Unify a title & project config field in a doc plugin

recursive loading of .moa/config -

• allows setting of variables for trees
• analysis nodes are almost always leaf nodes

light version of the original git plugin

• autocommit if in a git repo

make sure that traversing through trees works again

create archives of workflows

Does it work?

recursive copy moa trees