hmf edited a comment on issue #18931: URL: https://github.com/apache/incubator-mxnet/issues/18931#issuecomment-687190156
@szha Just a small comment and question on the issue of the tutorials asked by @pengzhao-intel. I am starting to look at this framework and find that I need to *hunt* down the dependencies so that the project examples work. Case in point the [MNIST example](https://docs.djl.ai/examples/docs/train_mnist_mlp.html) has a link to the [setup](https://docs.djl.ai/docs/development/setup.html). However, we still need information on the dependencies for the `ai.djl.basicdataset.Mnist` import. That important information is found [here](https://djl.ai/basicdataset/). I have not found a link to this page from the documentation. I would also like to know how are you *validate* the tutorials (I haven't checked so they may be in perfect working order). I am interested in this because I have other projects in Scala ([example](https://cese.gitlab.io/adw/docs/tasks.html)) wherein I generate a site. In one case I use for example [Laika](https://github.com/hmf/Laika) to process the Markdown. To ensure the code is working I use either [Tut](https://github.com/tpolecat/tut) or [Mdoc](https://scalameta.org/mdoc), which supersedes it to preprocess the Markdown sources. Note that all the code are in the Markdown files and are checked when they are compiled and execute (output can be placed in the source Markdown). Thus code and documentation are always in sink. Is there a way to do this in Java? EDIT: just realized that the checks above won't catch any missing references to dependencies. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
