Which GPU do you have and could you provide your saves files. It looks very fishy to me.

warning: `logic-ai` (bin "logic-ai") generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 50.09s
     Running `../cargo_target/debug/logic-ai`
2 3 0 1 
3 0 1 2 
0 1 2 3 
1 2 3 0 

Did not load
0: 95.65555, 0.008372713
thread 'main' panicked at 'Could not write to file: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/main.rs:297:53
stack backtrace:
<snip>

What's the required path? Is the above output something you'd expect?

I'd be very happy to help!

My GPU is a NVIDIA GeForce GTX 1650 Ti Mobile.
Here are two save files (they need to be renamed to futo.net and placed in the saves folder).
I pushed a new version of my project that should include the needed folder, so that error should no longer occur.
saves.zip

Long story short, it's a bug. Some things became private and the current automated testing is done without such an example, #190 addresses the principal issue of lacking API to manage to do it at all. On the other handside: That API is very rough and requires understanding of knowledge around capnp which is not ideal. I'll create an abstraction soon™ but until then I'd recommend to patch your project with that PR.

The example seems to store and retrieve the config, but not the actual network parameters(eg the ILayer object) itself. What would I need to change to also save and load a Layer object alongside the config?

Edit: https://github.com/spearow/juice/blob/dda9d01c1dd81f6174b0340f12eb3d4f30551488/juice/src/layer.rs#L764-L767

There is a save and load function should be what you need.

I already use the save and load functions. I implemented saving of the config, but the learning stall after a reset still happens. Should I be getting the SequentialConfig from somewhere other than when I first make it? I would guess that it is probably a bug in the save and load functions rather than not being able to save configs.

I'll dig deeper into this, on first glance save and load appear ok. I have yet to finish a unit test for a trained network with equality checks.

#190 does implement a unit test now, but the PartialEq implementation does not cover all items. The weights are checked for equiv though, so that cannot be the root of the issue. The weight_gradients are not retained, but they are only accumulations for a minibatch anyways, and are reset after each. So this investigation needs some more time.

I wrote a simple xor example from the project linked at the top. In the main function, first only run the xor_train() function, then stop it once it has learned, change the line to xor_eval(), and see that the stored weights do not produce the correct results.

I think the correct test would be:

train
...
train
eval
save
load
eval

and compare the output on the two eval invocations on the same input. Or is that what you meant?

I didn't get around to dig deeper yet

I revised the main function so that it does that, the issue still persists.
Could it have to do with the forward function itself? It theoretically should not need to be mutable, so maybe something is being overwritten there?

I think it may have to do with the loading of the bias weights. I added a third example which is just a single linear layer, and it learned to just be the identity function. When I load it from file, it has the same slope, but all the outputs are shifted. I'm guessing that there is something that is not being saved or loaded properly from the weights.

0: 0.3421242
Trained model before reload from disk:
[1.4901191e-6, 0.9999985]
Loaded net
Model after reload from disk:
[1.4076138, 2.407611]
There are 0 differences in weights.

I'll try to make some time for investigating further, personal life events just consume a lot of my spare time lately.