Closed berland closed 3 months ago
It makes sense. Just wondering about two things:
real.num_cpu
?
- Can it really change from realization to realization?
The previous driver would allow it if the ensemble builder built the realization in that way, but the ensemble builder will not do that currently. Even if the number of CPUs were parametrized in the Eclipse DATA deck (the num_cpu parser in the config will just not work in that case).
- Why are we sending it explicitly for the OpenPBS driver?
I put it into the abstract driver, so it should support the same signature, but the LocalDriver and the OpenPBSDriver will currently ignore it. The OpenPBS driver should be refactored to use the same num_cpu as the LsfDriver, but that will be a kind of breaking change compared to the removed C Torque driver since that is using NUM_NODES and NUM_CPUS_PER_NODE.
Issue Resolves #8095
Approach Use the Realization object which is pre-populated with the correct cpu count.
When applicable