Discussion - proposal for restructure

[mtitov]

I propose to split the repo into two main parts:

• src - kernel (maybe to have a different name for it?)
• collection - prepared miniapps
  • Each collection should have its main code and all configurations per machine should be under platforms

Also we can have bin directory for CLI commands

radical-miniapp run <prepared-miniapp-name> --platform <supported-platform>
radical-miniapp exec [options]  # CLI for kernel

---

Another thought is to separate kernel and collections into dedicated packages: radical.miniapp-core, radical.miniapp-collections

[andre-merzky]

Naming (just because it's fun): I'd propose radical.miniapps-kernel and radical.miniapps (I'd drop the workflow as the apps themselves are not necessarily workflows).

Structure: I think that a split into two repos is not really needed, IMHO it's fine to keep both (kernel and apps) in one repo as long as it is well organized, maybe like this:

$ tree radical.miniapps/
radical.miniapps/
├── CHANGES.md
├── LICENSE.md
├── MANIFEST
├── README.md
├── setup.py
├── bin
|    └── radical-miniapp
└── src
    └── radical
        └── miniapps
            ├── apps
            │   ├── __init__.py
            │   ├── impeccable
            │   │   ├── __init__.py
            │   │   ├── app_1.py
            │   │   └── app_2.py
            │   ├── impress
            │   │   ├── __init__.py
            │   │   ├── app_1.py
            │   │   └── app_2.py
            │   └── xgfabric
            │       ├── __init__.py
            │       ├── app_1.py
            │       └── app_2.py
            └── kernel
                ├── __init__.py
                └── kernel.py

Running the apps with radical-miniapp run -p impeccable -n app_1 <options> sounds nice - it avoids pollution of the bin dir and makes it easy to swap apps (if options are somewhat compatible).

My $0.02

[mtitov]

summary from the discussion with Ozgur:

• keep the structure as Andre proposed (apps -> collection)
• base installation is for kernel only (e.g., pip install radical.miniapp), and install specific workflow miniapps explicitly (e.g., pip install radical.miniapp.deepdrivemd, pip install radical.miniapp[deepdrivemd,xgfabric], etc.) so the installation will be done for kernel and corresponding wf miniapps
• still need to come up with an internal structure for miniapp itself
  e.g.,

% tree collection/
collection/
└── impeccable
    ├── requirements.txt
    ├── setup.py
    └── src
        ├── __init__.py
        ├── executables
        ├── platforms
        │   ├── frontier
        │   └── polaris
        └── workflow

Open question is how should we call this package correctly: radical.miniapp, radical.workflowminiapp, radical.wfminiapp?

[mturilli]

Leaving open for @GKNB @mtitov to confirm that the work is done and the ticket can be closed.