fncbook / fnc Goto Github PK

I noticed that you are suggesting PackageCompiler for accelerating the startup time. I am planning to teach a course with this book during Spring '22 and was planning to make a PackageCompiler script available for my students. From the manual, it looks like we just need the list of packages to include and a script to run.

using PackageCompiler
create_sysimage(["Plots"], sysimage_path="sys_plots.so", precompile_execution_file="precompile_plots.jl")

Do you think that the main test file would be sufficient to exercise all the precompilation needs?

It'd be useful to explain somewhere what sort of contributions are appropriate for pull requests. Are new chapters/sections of interest? More demo notebooks? If so, do you have specific preferences about how such contributions are structured other than general consistency with existing material?

I have a bunch of homeworks and activities organized as Jupyter notebooks using nbgrader (linked from course page). The activities are simple demonstrations with a few lines for students to contribute; we worked through them with neighbors in class. The homeworks (which I broke up into activities post-COVID) were more in-depth, like deriving the Legendre polynomials via Gram-Schmidt in L^2.

These notebooks are currently Python, but I could quickly convert to them Julia, and likely will anyway next time I teach the class for better consistency with this book. Are such resources (adjusted to be more consistent with terminology/tooling in the book) something that would be worth building as a community resource to go along with the main text of the book? I could imagine curating such resources in-repository (similar to the demo notebooks) or creating a separate repository for community-sourced supplements.

There seems to be an undefined notation under finite differences https://fncbook.github.io/fnc/localapprox/finitediffs.html as the following image shows:

The TeX command in the source is \dd{\tilde{f}}{s} so it looks like \dd is undefined.