You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Jupyter Notebooks are wonderful, but do have some limitations. It would be great to tap into the expertise here to figure out a reasonable set of requirements, how to configure the notebook to support these requirements (i.e., do we need extensions and if so, which ones), and then include a demo notebook with simple examples covering these requirements.
For example, we could create a subdirectory to work on both the requirements and the demo notebook. The requirements doc could be laid out as
Requirements
Markdown cells
Math equations in isolation (standard)
Math equations with labels
...
Code cells
Need certain module for reason x
...
The text was updated successfully, but these errors were encountered:
The TeX input processing in MathJax can be configured to add equation numbers to displayed equations automatically. This functionality is turned off by default, but it is easy to configure MathJax to produce automatic equation numbers...
It is also possible to set the tagging to 'all', so that every displayed equation will get a number, regardless of the environment used.
You can use \notag or \nonumber to prevent individual equations from being numbered, and \tag{} can be used to override the usual equation number with your own symbol instead...
You can use \label to give an equation an identifier that you can use to refer to it later, and then use \ref or \eqref within your document to insert the actual equation number at that location, as a reference.
The Jupyter Notebooks are wonderful, but do have some limitations. It would be great to tap into the expertise here to figure out a reasonable set of requirements, how to configure the notebook to support these requirements (i.e., do we need extensions and if so, which ones), and then include a demo notebook with simple examples covering these requirements.
For example, we could create a subdirectory to work on both the requirements and the demo notebook. The requirements doc could be laid out as
Requirements
Markdown cells
Code cells
The text was updated successfully, but these errors were encountered: