Relationship between cult-cargo temp-dir and wsclean temp-dir

[IanHeywood]

For the HI processing I run multiple wscleans in parallel on the same MS, which I think I get away with because they are always read-only operations. But for this to work I have to use the temp-dir option, otherwise one run will eventually delete the temp files of the others and the whole operation falls over. The paper mentions this:

A second exception is temporary disk storage, required by some applications (consider, e.g., WSClean and its -temp-dir option).

but only in the context of kubernetes requiring some special treatment of it. I notice in cult-cargo's wsclean-base.yml definition that temp-dir is another parameter that is not exposed, however there is a temp-dir section in base outputs. So I'm just wondering what the relationship is between the base outputs temp-dir and wsclean's temp-dir parameter.

[o-smirnov]

Cult-cargo doesn't have its own special temp-dir -- but it is defined (in a roundabout way, via wsclean-base.yml, because of the dynamic schema thing) as a legit output of the wsclean cab. At least stimela doc cultcargo::wsclean.yml shows it for me. So you should be able to just set it as normal?