search

paumailo / ephys

Automatically exported from code.google.com/p/ephys
0 stars 0 forks source link

Launching AutoClass Reporting Utility (pooling GUI) #9

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. run through autoclass
2. finishes grabbing spikes and results
3.

What is the expected output? What do you see instead?
autoclass spike viewer to load

What version of the product are you using? On what operating system?

Please provide any additional information below.

I'll check again in the morning but it seems that matlab stalls and doesn't 
complete the loading of the spike viewer (Pooling GUI) anymore.

Worked on the old machine from before, I have that one running through an 
autoclassing (takes a long time on that machine)

Original issue reported on code.google.com by ejbre...@gmail.com on 6 Feb 2013 at 10:17

GoogleCodeExporter commented 8 years ago 
Unable to replicate this issue with Pooling GUI.  If you have a ton of data, 
then it may take a while to load a channel and render all of the plots.  Just 
let it crunch.

Original comment by daniel.s...@gmail.com on 7 Feb 2013 at 4:19

GoogleCodeExporter commented 8 years ago 
I can get the pooling GUI to open once the classes have been created on the rig 
computer (New-OB1) but the AutoClass2.m file seems to just ideal on the 
autoclassing machine (JW-Autoclass) it creates the snip files, the .s.param 
&.r.param files etc.
But even just letting it sit for hours, it won't create the _Classes file 
needed for the Pooling GUI.

So I'm giving you as much information as possible, SCRATCH_AutoClass2 runs and 
launches AutoClassReport2 which gets to at least line 36:
disp('Launching AutoClass Reporting Utility')

However, it then ideals there, no errors, no movement after waiting.

I'm not sure if you can, but if you remote log on to the JW-Autoclass machine 
you should be able to replicate the issue.

Original comment by ejbre...@gmail.com on 7 Feb 2013 at 5:54

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
A program (PsExec) was originally used to launch AutoClass.  If PsExec wasn't 
installed on the system then the reporting utility wouldn't be launched.  The 
calls to PsExec were removed because they weren't totally necessary.

The reason PsExec was used initially was to allow distribution of AutoClass 
jobs on remote computers.  Maybe it can be reimplemented in the future.

Original comment by daniel.s...@gmail.com on 8 Feb 2013 at 1:35

GoogleCodeExporter commented 8 years ago 
OK, I didn't see that in the code. Sorry I missed that.

Original comment by ejbre...@gmail.com on 8 Feb 2013 at 1:37

GoogleCodeExporter commented 8 years ago 
No worries, it was extraneous, it should be all set to go now.

Original comment by daniel.s...@gmail.com on 8 Feb 2013 at 1:44