-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plotting generates identical figures with different filenames #32
Comments
I agree that it not generally desirable, so I'm happy to have the clock time removed from the file name. |
I'd also add that "Pairwise species fits" is not entirely what the plots are showing (a comparison between LandR growth curves and growth curves from fitted non-linear models) -- and spaces in file names aren't great either. |
Yes, file names should be descriptive. Can you also ensure file names are prefixed by the module name? It makes it easier to associate specific figures with certain modules (and to find them as a human). |
I partially agree with this. One the one hand, yes, appending the module name would facilitate finding figures and even interpreting them. However,
I wonder if, instead, we could (in this and and other modules in which to do this) create a module parameter that governs where figures are saved (e.g. This partly addresses my point no. 1, in that the figure names would remain the same. It doesn't address no 2, as it still means changing internal code of several modules (and creating a new parameter), if we want to propagate this across modules. It fully addresses no 3, as filenames would remain as short/long as they currently are |
I think separate subdirs for each module makes more sense. That could be an easy addition to |
In that case I'll hold off creating any parameters for |
Actually, scratch that. I'll still suggest/PR a more accurate filename wrt what the figure is about. |
I implemented When called from a module, |
Plotting in
Biomass_speciesParameters@dev-stable
is currently occurring during theinit
event via:meaning that each time the
init
is run a new figure file is created, becausesim$._startClockTime
will differ.I can see the interest of doing so during module development phase, but when using this module in combination with others and when event caching is off, this creates a lot of duplicated figure files.
Is there a reason why we shouldn't overwrite the same figure with an update version?
The text was updated successfully, but these errors were encountered: