populse / capsul

Collaborative Analysis Platform : Simple, Unifying, Lean
Other
7 stars 14 forks source link

Use BrainVISA interface to select Capsul pipeline #302

Open sapetnioc opened 9 months ago

denisri commented 8 months ago

This is partly done but we can discuss what we want exactly:

But we don't see in Axon GUI all capsul processes and pipelines if they are not redeclared in axon. Do we want more ?

denisri commented 8 months ago

Another sub-topic to be handled: completion schemas. The way to load Capsul3's completion schemas (and ProcessSchema subclasses) given a process/pipeline and the needed schemas (Bids, brainrvisa etc) is not clear yet. So far we load Morphologist schemas (hard-coded) because we only have those and they are currently part of Capsul3 (#328), but there is currently no mechanism to load additional schema parts for additional processes or toolboxes.

sapetnioc commented 8 months ago

Yes. There is a low level and not very user friendly mechanism that allows to load a schema: record the corresponding Python module in the list of modules to load in the config. But we have to work on the definition of higher level objects such as toolboxes.

Le jeu. 23 nov. 2023 à 17:39, Denis Rivière @.***> a écrit :

Another sub-topic to be handled: completion schemas. The way to load Capsul3's completion schemas (and ProcessSchema subclasses) given a process/pipeline and the needed schemas (Bids, brainrvisa etc) is not clear yet. So far we load Morphologist schemas (hard-coded) because we only have those and they are currently part of Capsul3 (#328 https://github.com/populse/capsul/issues/328), but there is currently no mechanism to load additional schema parts for additional processes or toolboxes.

— Reply to this email directly, view it on GitHub https://github.com/populse/capsul/issues/302#issuecomment-1824708588, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXLUTU6ZTLD2GLI36O3LW3YF534VAVCNFSM6AAAAAA7ETGEQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRUG4YDQNJYHA . You are receiving this because you authored the thread.Message ID: @.***>