Be able to output the dl4j computationGraph.summary() for debugging purposes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 352
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
I had some problems to output the dl4j computationGraph.summary(). After configuring the logging right, I succeeded to output it for training.
But still, after deserializing the prepared dag, something like this is not possible:
NeuralNetwork.Prepared p = prepared.producers(NeuralNetwork.Prepared.class).findFirst().get().peek();
System.out.println(p.getComputationGraph().summary());
Perhaps add some additional logs or allow such a code from above (by making some more things public)?
It would also be great to be able to add some handlers/listeners for training like it is possible in dl4j (for example to save the model after every epoch, or doing some more evaluation every epoch).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing NeuralNetwork.Prepared, producers(...).peek(), and getComputationGraph() through the repository, then inspect the training path and deserialization behavior. Done would require a decided scope for exposing computationGraph.summary() and/or adding training listeners, with documented behavior and tests for the selected API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100