Is there any documentation on prebuild? In particular, I’d like to know what I need to change so it does not look in cylc-run but instead in some sensible sub-directory of ~ on puma2. I have set the prebuild to point to ~tetts/prebuilds/u-dr496/fcm_make_um/ and that works but it is picking up files from my cylc space. I was cleaning our my old jobs and turns out my prebuild used something in my cylc-run space…
Simon
Hi Simon,
The only documentation I am aware of is in the FCM user guide and is little.
Because we have to use a 2-step fcm_make on ARCHER2 builds are split over the 2 platforms. When you specify the location of the prebuild on PUMA2 it automatically locates the other half on ARCHER2 by the contents of the fcm-make config file in that prebuild. You’d have to hack this config file to point to a.n.other location on ARCHER2 if you move both halves of the build. I have never done that and can’t say if that would work or not; there may be more stuff under the hood that I don’t know about.
Regards,
Ros.
Thanks Ros,
as ever grep is our friend!
[tetts@puma2 fcm_make_um]$ grep -i ‘cylc-run’ *.cfg
fcm-make-as-parsed.cfg:mirror.target = ln02:cylc-run/u-dr496/share/fcm_make_um
fcm-make-as-parsed.cfg:mirror.target = ln02:cylc-run/u-dr496/share/fcm_make_um
fcm-make-on-success.cfg:dest = /home/n02/n02/tetts/cylc-run/u-dr496/share/fcm_make_um
fcm-make-on-success.cfg:mirror.target = ln02:/home1/home/n02/n02/tetts/cylc-run/u-dr496/share/fcm_make_um
That, to me, suggests I should change mirror.target from ln02:cylc-run/u-dr496/share/fcm_make_um to where ever I put the prebuild. I think I just want the configuration file(s??) on puma and the rest of the stuff on archer2. So they are visible they should be on /work or I could hack point to the puma2 stuff (as you can see that from archer2).
Seem sensible?
I’ll think about that a bit and decide what to do!
Simon