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
@rimhajal I think the easiest way to decide if we really need to include graphing code into our package is first to design graphs in the documentation.
So the right path would be as follows (IMHO):
Write up as documentation pages long examples following 1) Maja's practice, 2) Maya's paper 3) some other source we have like Nathalie's slides ?
Alongside this documentation, when something needs to be plotted, do it with Plots.jl's standard interface (you should probably read a bit their documentation)
When this is done, if some graphs really were complicated to make, we'll consider adding some special syntax for them in the package. If all the graphs are "easy" to make, then having them in the docs alongside the code that produces them will be largely enough.
Tell me what you think
The text was updated successfully, but these errors were encountered:
@rimhajal So i guess that after what you did on the examples, there is no real need to include graphing code into the package, right ? If so, then we can simply close this issue and check/remove the corresponding boxes in the general todolist.
lrnv
changed the title
[Dicussion] Potential graphs and way to make them
[Discussion] Potential graphs and way to make them
May 2, 2024
@rimhajal I think the easiest way to decide if we really need to include graphing code into our package is first to design graphs in the documentation.
So the right path would be as follows (IMHO):
Tell me what you think
The text was updated successfully, but these errors were encountered: