Group level folder not created about fitlins HOT 4 CLOSED

Ah. I wonder if the better thing is to drop the session entity altogether. Unless it's desired to keep things sorted this way? I guess it's safer to not drop, but we may want to consider that things like ses- and run- that aren't going to be collapsed and do not disambiguate outputs might add pointless verbosity.

from fitlins.

Actually I was wondering about that as well. Wouldn't it be an issue if you're analyzing multiple sessions?

from fitlins.

Yes, so it would need to be dependent on whether the session is a relevant unit in later blocks. This may not be the most trivial thing to decide from many spots within a pipeline, so I'm inclined to leave it alone for now.

However, if we collapse all higher-level blocks into a single second-level, then the problem will go away. (This is my solution to everything, since it'll probably be Tal who figures out how to do it.)

from fitlins.

I'm not sure if that's because you have faith in my abilities or disregard for my sanity, but I find it troubling either way. ;)

from fitlins.