modlunit ?

char4040 · Post by **char4040** » Fri Jul 14, 2006 2:48 pm

I would like to check the units in my code using NEURON's modlunit; however, it doesn't seem to be working for me. When I open modlunit and select the desired file from within the working directory, the screen flashes something very quickly and returns to the "Enter filename:" window. It appears that nothing is happening if not paying attention. What does this flash mean? What should I be seeing? How can I fix it?

Charly

Post by **ted** » Fri Jul 14, 2006 4:08 pm

If it's not complaining about anything, it didn't find any units inconsistencies. For fun,
you might deliberately introduce an error just to see what happens. For example,
start with a mod file that specifies a distributed current (WRITEs a current whose units
are in mA/cm2 and has a conductance density S/cm2), and change the units of the current
to A/cm or the conductance to uS/cm.

char4040 · Post by **char4040** » Mon Jul 17, 2006 9:28 am

I have been doing just that, creating a simple mod file and changing the units to that which I know are inappropriate and should be caught by neuron. For fun I did exactly as you proposed and still only got the quick flash of the window. Changing from mA to A and cm2 to cm resulted in no complaint.

Post by **ted** » Mon Jul 17, 2006 11:17 am

Did you look at the xterm? That's where error messages are printed.

char4040 · Post by **char4040** » Wed Aug 02, 2006 9:29 am

I am running windows...

Raj · Post by **Raj** » Wed Aug 02, 2006 10:02 am

Replace nrniv.exe in the shortcut with neuron.exe and the dos boxes will remain visible if modlunit has found a mistake. At least that is what it does here (XP with nrn 5.8 Main (88)).

I suppose we call this a bug, but it is something I remembered worked well earlier. So it might be XP as opposed to W2K, NT or Win98.

char4040 · Post by **char4040** » Wed Aug 02, 2006 11:52 am

Thank you.
That appears to have fixed it; however, now the dos window stays up sometimes and sometimes doesn't...when it disappears does that simply mean that no error was found?

Post by **ted** » Wed Aug 02, 2006 12:15 pm

modlunit fails to work properly under XP on my PC too. This happens with NEURON
5.9 2006-07-14 (1461), and also with 5.9 (1434). What versions are you using, Raj and
char4040? Also, which MSWin are you using, char4040?

char4040 · Post by **char4040** » Wed Aug 02, 2006 2:09 pm

I am running the neuron 5.9 version downloaded 6.12.06 using WinXP.
I am hoping you will find this information useful.

Post by **ted** » Wed Aug 02, 2006 2:30 pm

The critical datum is not when you downloaded the file--it's the revision number and date,
which are contained in the first line of the message that NEURON prints in its xterm when
you double click on nrngui

Raj · Post by **Raj** » Wed Aug 02, 2006 2:35 pm

XP fully patched with nrn 5.8 Main (88)

As noted before replacing nrniv.exe with neuron.exe in the shortcut seems to provide a workaround.

Raj · Post by **Raj** » Wed Aug 02, 2006 2:46 pm

W2K shows exactly the same problem.

with all these versions:
NEURON -- Version 5.6 2004-5-19 23:5:24 Main (81)
NEURON -- Version 5.8 2005-5-2 13:16:27 rel5_7_159 (1)
NEURON -- Version 5.8 2005-10-14 12:36:20 Main (88)

All with the same cygwin version though:
CYGWIN_NT-5.0 rajslab 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin

Workaround works forall of them.

Post by **ted** » Wed Aug 02, 2006 3:43 pm

Raj wrote:Workaround works forall of them.

Thanks, Raj, that's particularly useful information.

char4040 · Post by **char4040** » Wed Aug 02, 2006 5:10 pm

ok- neuron version 5.9 2006-06-13 1423

Post by **ted** » Thu Aug 03, 2006 2:57 pm

The bug has been fixed--install this new version
http://www.neuron.yale.edu/ftp/neuron/v ... -setup.exe