-
Notifications
You must be signed in to change notification settings - Fork 62
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
Analytic solution for tapered cable #42
Comments
Turns out the maths is a bit hard! Will come back to this, but for a truncated tapered cable with a current injection at the thick end, the underlying PDE we need to solve is the following, for g(x,t), x ∈ [a, b], t ≥ 0. x·gxx + 2gx = gt + g, subject to: gx(a, t ) = 0, gx(b, t ) = -1 for t > 0, |
Path to validation output can be customized via an environment variable NS_VALIDATION_PATH_FORMAT which will substitute the following keys: %T Timestamp of invocation of install-local.sh. %H Git commit hash of nsuite (with + on end if modified). %h Git commit short hash of nsuite (with + on end if modified). %S System name, as defined in system environment script or else host name. %s Simulator name. %m Model name. %p Parameter set name. * Add git-repo-hash script to spit out short or long commit hashes. * Add pathsub script to perform pattern replacement, optionally relative to a base directory. * Record installation timestamp and system name in generated environments. * Export ns_ path variables, together with ns_timestamp and ns_sysname, in generated environments. * Set validation output path template via --output/-o option in run-validation.sh, via exported environment variable ns_validation_output_format.
Update: this is partly resolved by #842, but we don't yet have code that reproduces the analytic time-varying solution. |
This should be now a validation feature for nsuite; we can close this ticket and refer to it over there. |
Corresponding validation test is now an nsuite issue, #110. |
Better to use an analytic (series) solution for a tapered cable-only model in validation testing, than asking NEURON to generate data for this case.
The text was updated successfully, but these errors were encountered: