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
One of the things I sometimes do when working on a new model is have a sort of 'scientific test suite' which automatically plots the output of each stage of the model and then dumps them into a pdf file. Maybe it would be good to have a tool that automates this, e.g. you would write calibrated_run(100*ms) instead of run(100*ms). Or even simpler, you would create a cal = CalibrationPlotter('filename.pdf') that would be a BrianObject and would do some stuff in the before and after run slots. So for example, it would plot a graph of the network, and for each object it would call brian_plot on it. For NeuronGroup it would also create a SpikeMonitor and StateMonitor (which would only record a handful of neurons to save memory).
I'm not sure how widely useful this would be. Perhaps it's too specific a use case, but it feels like something that a lot of people would benefit from doing but don't because it's effort and time taken from doing the actual modelling work, but if it was made trivially easy to do so then they might.
The text was updated successfully, but these errors were encountered:
One of the things I sometimes do when working on a new model is have a sort of 'scientific test suite' which automatically plots the output of each stage of the model and then dumps them into a pdf file. Maybe it would be good to have a tool that automates this, e.g. you would write
calibrated_run(100*ms)
instead ofrun(100*ms)
. Or even simpler, you would create acal = CalibrationPlotter('filename.pdf')
that would be aBrianObject
and would do some stuff in the before and after run slots. So for example, it would plot a graph of the network, and for each object it would callbrian_plot
on it. ForNeuronGroup
it would also create aSpikeMonitor
andStateMonitor
(which would only record a handful of neurons to save memory).I'm not sure how widely useful this would be. Perhaps it's too specific a use case, but it feels like something that a lot of people would benefit from doing but don't because it's effort and time taken from doing the actual modelling work, but if it was made trivially easy to do so then they might.
The text was updated successfully, but these errors were encountered: