-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Documentation overhaul #46
Comments
This was raised again in discussion in #90. I'd like to find a better place to keep documentation of math that's too lengthy and/or not relevant for docstrings. Requirements:
Nice-to-haves:
Any suggestions are welcome. |
I asked a question on julia-users to get some input for tools and platforms: https://groups.google.com/forum/?nomobile=true#!topic/julia-users/mRk0igz_uHQ |
I have seen in the docs some obscure infromation about how to select the behaviour outside the domain, i.e, decide wether or not to extrapolate. I haven't figured how to use it, however, i can see that ExtrapNaN or ExtrapError are no longer valid as arguments to extrapolate. I think that part of the docs could be improved. [I'll check the source and see if i can help] |
That would be most appreciated! |
@argelouski: I think that this section of the Readme is up to date, so that can hopefully provide some assistance, too. |
This blog post should definitely be considered, too: http://maurow.bitbucket.org/notes/documenting-a-julia-package.html |
This is to discuss changes to, and completion of, documentation for this package. Major questions are:
Some discussion started in #45 already, where the following points were raised:
I agree that it's probably a good idea to make the readme minimalistic. I'd also like to start documenting most other things in a
help>
-compatible way, so we might want to move off from the IJulia notebooks alltogether. And I feel like I have to strip down the LaTeX stuff to something with minimal dependencies, so anyone can at least compile it, but it is a very handy way to document the mathematical background of any methods we implement...The text was updated successfully, but these errors were encountered: