NEURON does not print (in this case) the last executed instruction after CVode.active(1) is set. And again, everything compiles without errors. The comment-out method would only work if the code was being executed - but my concern and difficulty is that the error occurs without execution (since the run() statement is never called - unless activating CVode somehow executes parts of my code ). Taking out chunks of code presents its own problems in that I will have to go over the rest of the code and remove newly dead function, object and segment calls and references - I do not mean to sound lazy, I just want to make sure it really is the only resort, since it is not an attractive option. Ok, I am starting to feel that I am really missing something here.but I will present my case anyway :) I admit I could've designed the code better suited for scaling back. If the code is truly modular, it should be a simple matter to comment out large chunks of it and embed print statements at critical points. Sorry if this is monotonous - I suspect it is probably something simple, hiding in pages of code, which is why I would rather first try to debug, rather than incrementally scale back in many different modules at once. I have followed previous similar threads looking for a way to diagnose these kind of errors, but have not found any way to track NEURON's instruction executions to find out what made it give a generic segmentation error (again, core_dump does not help - but something like WinXP's "debug" button would be awesome :) ). So what I am stuck with is a code that compiles (so no parse errors), but the runtime error is not really runtime since the run() statement never gets a chance to be called - all it takes for the error to pop up is setting CVode.active(1), after compilation. This case is a bit different from normal practices I would follow, due to the nature of the model (for ex., I had to make some rather radical changes, splitting input streams, etc) - it would've been hard to do that incrementally, it was more of a tear-down-and-rebuld kind of thing. PSPad offers syntax highlighting, this can be customized using Settings->Highlighter Settings.įor NEURON syntax highlighting files can be found at: Program Arguments (%1=selected directory)ĭ:\ProgramFiles\ComponentSoftware\CSDiff\CSDiff.exe In my case I have the following settings, please modify to fit your program locations etc. In the menu under View->Preferences (Programs Tab) you can add links to programs needed for common tasks. RapidSVN offers a nice GUI but adding the right settings will give this tool extra leverage. To benefit most from version management you have to automate a few things. General intro on best programming practices, including INTRODUCTION TO SUBVERSION Other programs that make life easier are:Ī diff program, showing differences between two files (text or word RapidSVN Subversion GUI built on Apache and wxwidgets libraries: Subversion itself, built on Apache libraries: ![]() Any way to display, debug the processes that lead to the error, to zero in on a faulty code?Ĭode: Select all For version control with subversion (under windows) please install the following, in the given order from an administrator account: Not too familiar with core_dump, but that just makes the NRN exit right away. So the question is, what should I look for in the code? The difference between a working and a broken simulation is mostly in complexity of synaptic activity.I am at a complete loss, and removing things bit by bit (back to the working version) will take years. I have never had a problem with CVode outside the NMODL field - and this time all the mod files work 100%. I also get a Signal 6 (whatever that means). However, manually activating it after compile replicates it. Setting the default to inactive removes the error. After mucking around, I traced the problem to activation of CVode. I get a segmentation violation, pointed to the end of a. ![]() Working with a rather complex model, after much additions to a previously working cell, I finally got it to compile with no errors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |