Flair Filetree Spawn Grouping

Flair
1

Recently, since the 3.4.0 update, I feel like some of the filetree functionality surrounding Spawns has changed.

I feel like I remember that when generating Spawns >0, all of the spawned runs would be saved in a new folder with the Spawn Run name which was extremely useful.

Now it dumps all new spawns into whatever happens to be the parent folder.

Secondly, I believe it was the case that when setting a Spawn number from >0 to 0, it would previously delete any previously created .inp files associated with the Spawned runs.

Now, when setting Spawns to 0, all previous .inp files are retained.

Has this functionality changed?

4

Hi @Dirk_Bartkoski
this functionality should not have changed.
I’ve made a few test and I cannot reproduce the error you described on my system. Would it be possible to share your .flair file?

5

Thanks. To test the functionality, I just made a generic basic new .flair to make sure it wasn’t related to my specific Flair file. It has the same issue. Attached is the .flair file as well as a screenshot showing a few different attempts to generate spawned runs. It can be seen that no matter where I generate them, they do not make their own subfolder.

I am running Flair 3.4.0 on Fedora 41, KDE Plasma version 6.3.2, kernel version 6.13.5-200.fc41.x86_64

testtest2.flair (857 Bytes)

FileImage
FileImage1219×468 82.2 KB

6

Hi @Dirk_Bartkoski
I am not able to reproduce it. I did the following:

  • opened your flair file
  • added a run folder/testrun
  • set to 4 spawn jobs
  • click Start
    image
    image1280×708 76.2 KB

    and I got the following file structure
test> ll
total 8
drwxr-xr-x 6 bnv dr 4096 Mar 28 08:57 folder
-rw-r--r-- 1 bnv dr  857 Mar 28 08:54 testtest2.flair
test> tree
.
├── folder
│   ├── fluka_2072140
│   │   ├── fort.1 -> /home/bnv/cernbox/WINDOWS/Desktop/test/folder/rantestrun_01001
│   │   ├── fort.11 -> testrun_01001.out
│   │   ├── fort.15 -> testrun_01001.err
│   │   ├── fort.16
│   │   ├── fort.2 -> rantestrun_01002
│   │   ├── fort.77
│   │   ├── rantestrun_01002
│   │   ├── testrun_01001.err
│   │   ├── testrun_01001.log
│   │   ├── testrun_01001.out
│   │   └── testrun_01.inp
│   ├── fluka_2072151
│   │   ├── fort.1 -> /home/bnv/cernbox/WINDOWS/Desktop/test/folder/rantestrun_02001
│   │   ├── fort.11 -> testrun_02001.out
│   │   ├── fort.15 -> testrun_02001.err
│   │   ├── fort.16
│   │   ├── fort.2 -> rantestrun_02002
│   │   ├── fort.77
│   │   ├── rantestrun_02002
│   │   ├── testrun_02001.err
│   │   ├── testrun_02001.log
│   │   ├── testrun_02001.out
│   │   └── testrun_02.inp
│   ├── fluka_2072189
│   │   ├── fort.1 -> /home/bnv/cernbox/WINDOWS/Desktop/test/folder/rantestrun_03001
│   │   ├── fort.11 -> testrun_03001.out
│   │   ├── fort.15 -> testrun_03001.err
│   │   ├── fort.16
│   │   ├── fort.2 -> rantestrun_03002
│   │   ├── fort.77
│   │   ├── rantestrun_03002
│   │   ├── testrun_03001.err
│   │   ├── testrun_03001.log
│   │   ├── testrun_03001.out
│   │   └── testrun_03.inp
│   ├── fluka_2072250
│   │   ├── fort.1 -> /home/bnv/cernbox/WINDOWS/Desktop/test/folder/rantestrun_04001
│   │   ├── fort.11 -> testrun_04001.out
│   │   ├── fort.15 -> testrun_04001.err
│   │   ├── fort.16
│   │   ├── fort.2 -> rantestrun_04002
│   │   ├── fort.77
│   │   ├── rantestrun_04002
│   │   ├── testrun_04001.err
│   │   ├── testrun_04001.log
│   │   ├── testrun_04001.out
│   │   └── testrun_04.inp
│   ├── rantestrun_01001
│   ├── rantestrun_02001
│   ├── rantestrun_03001
│   ├── rantestrun_04001
│   ├── testrun_01.inp
│   ├── testrun_01.out
│   ├── testrun_02.inp
│   ├── testrun_02.out
│   ├── testrun_03.inp
│   ├── testrun_03.out
│   ├── testrun_04.inp
│   └── testrun_04.out
└── testtest2.flair

6 directories, 57 files

Can you please verify that the
Config → Run → Spawn Run Name
has the default value \I_\2

7

I checked the Spawn Run Name and found that, while the default value was \I_\2, Flair is not responding to modifications to the Spawn Run Name input.

It doesn’t matter what I try to use for the Spawn Run Name, it saves all the spawns exactly as before.

I think what I want is \I/\I_\2 so all the spawns will be saved into a new directory whose name is the run name.

8

I ended up resolving my issue. Very simple actually but I will put it here for future reference.

I did, in fact, want \I/\I_\2 as the SPAWN RUN NAME in the settings as this allows spawns and attached files to be automatically generated in their own subfolder.

My issue was, when I tried to change the SPAWN RUN NAME, Flair was not generating input files with the new naming convention, regardless of what it was.

Turns out, you have to generate a completely new run and spawns after changing the SPAWN RUN NAME setting to enact the new naming convention. It doesn’t rename previously generated names. This is more subtle when going from \I_\2 to \I/\I_\2 as in the Flair filetree they look identical but have different file structures when the input files are generated.

1 Like