Adam Pocock

I get an exception thrown when I try to create a game, which comes out of the serialization infrastructure. ```FATAL 2020-05-01 22:38:45,210 MAGE Client UI error =>[AWT-EventQueue-0] EDTExceptionHandler.handle java.lang.reflect.UndeclaredThrowableException at...

One thing to note is that OpenJDK 8 and Oracle JDK 8 use different rendering pipelines. They were unified in Java 9 (https://openjdk.java.net/jeps/265).

I assume it's a remote method call that returns an optional, hence it's serialised over the wire.

As of 4.3 all models can be serialized into protobufs and we'll use that as the sole serialization mechanism for v5 replacing `java.io.Serializable` (ONNX export will still be available for...

I don't see this behaviour when using the Java interface. How are you calling it?

Yes, the current dataset representation isn't as memory efficient as we'd like it to be, particularly when deserializing from protobufs. The protobuf deserialization path doesn't deduplicate the feature name strings...

Ok, sounds like the dense example will help you quite a bit. Moving to memory mapped IO as a supported Tribuo `Dataset` class will be hard as neither the protobuf...

That kind of `UnsatisfiedLinkError` is typically because an older version of the ONNX Runtime native library was loaded from somewhere else on your classpath, as it's after the JNI binding...

`CSVLoader` returns a [`CSVDataSource`](https://tribuo.org/learn/4.3/javadoc/org/tribuo/data/csv/CSVDataSource.html). The `DataSource` interface doesn't have much in the way of accessor methods, you should construct a `MutableDataset` from that data source which will populate the feature...

You can inspect the examples after they have been loaded to make sure the pipeline is valid. I recommend looking at `CSVDataSource` rather than using `CSVLoader` as it's more flexible....