Took a while to debug why hypermapper suddenly started giving bad results after not touching Spatial for a long time. It turned out the system switched from java 8 to java 11 and Spatial just quietly whispered that it couldn't load models. The try/catch statement in the model analysis that loads the pmmls is where we should print something more useful.
Info:
Spatial hash:
b567346009bbc3aa1a5fd3c061df60fb8f5eaa22 (master)
HyperMapper (dev, private - but should be up-to-date with master):
a052358b2c5ee0a52c2337f0cb51146c463aef61 (master)
Issue and cause:
All configurations in conv_shallow_for_dse were infeasible (False) - Java 11 instead of Java 8
Java 11 - did not work:
java-1.11.0-openjdk-amd64
Java 8 - worked:
java-1.8.0-openjdk-amd64
Others:
sbt script version: 1.5.2
Took a while to debug why hypermapper suddenly started giving bad results after not touching Spatial for a long time. It turned out the system switched from java 8 to java 11 and Spatial just quietly whispered that it couldn't load models. The try/catch statement in the model analysis that loads the pmmls is where we should print something more useful.
Info:
Spatial hash: b567346009bbc3aa1a5fd3c061df60fb8f5eaa22 (master) HyperMapper (dev, private - but should be up-to-date with master): a052358b2c5ee0a52c2337f0cb51146c463aef61 (master) Issue and cause: All configurations in conv_shallow_for_dse were infeasible (False) - Java 11 instead of Java 8 Java 11 - did not work: java-1.11.0-openjdk-amd64 Java 8 - worked: java-1.8.0-openjdk-amd64 Others: sbt script version: 1.5.2