#27602

Is the problem reproduceable with the most recent version of PD4ML (v351)?