Turn off jb eval

[guillaumevernieres]

I'm not 100% sure this fixes the memory issue on MSU HPC, but, while I was working on other things, I turned off the jb eval out of impatience to gain ~5+mn of runtime. I also noticed that the memory footprint is down to ~0.8TB for the 3DVARFGAT.
I'm testing with more iterations right now.

[danholdaway]

Thanks for adding this @guillaumevernieres. For backward compatibility I think it would be good to default to True. And also allow users the option to keep using the feature. Then you can set the two settings to False in your jcb settings.

[danholdaway]

By the way, when you create a jcb-algorithms PR, you also need to create an empty branch with the same name in the main jcb repo. This is unfortunately needed for the CI. It allows for the connection between jcb-algorithms and repos like jcb-gdas so that these changes can be tested against those repos. I'll try to remove that requirement soon.

[guillaumevernieres]

Roger that @danholdaway ...

It looks like this is way more than a 5 mn gain.

• 30 iterations wo j eval : 17mn
• " " with : probably 30+mn. I's still running but I'm pretty sure it will time out (only asked for 30mn on debug)

We should turn that option off by default, this has been a huge waste of resources.

[danholdaway]

I'm OK with setting the flags to e.g. jb evaluation: {{ jb_evaluation | default(false) }}