[Paraview-developers] BUG?: Where can I get "mpirun" other than the folder of a released ParaView?

[Biddiscombe, John A.]

Utkarsh

>
Alternatively, I can add a new xml attribute that says that the script blocks or doesn't. That was if the script is supposed to block and the launch indeed fails,
<

That would be the best solution., On linux when I connect to a server, it ssh's to the machine with N params, calls a script which generates the slurm job script (on the remote machine) and returns immediately, but I echo everything (the generated job script contents) to the terminal and see the submission, then slurm reports that "submitted batch job XXXXX" and you see this on screen too, so you know if it is working usually. If we have a "non blocking" tag in the xml, then all will be fine. A normal mpiexec launch is blocking, a script is not. On windows, you used (3.12 I think) to see the script echo results in the message/output window so you could see the job submission take place. But this has now gone, so I add a terminal window to paraview so that I can see the results. It'd be quite nice to have a tag to say "Send launch commands/output to output console" as well so that it was easier to see stuff.

Attached patch: No. It doesn't work, I tried standard mpiexec with forward connect, also reverse. Both failed. Forward is just a lock-up --pvservers do start, but connection is not made. Reverse shows the error msg dialog I posted earlier. Thanks for trying. 

JB





-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 10 February 2012 17:55
To: Biddiscombe, John A.
Cc: ParaView Developers
Subject: Re: [Paraview-developers] BUG?: Where can I get "mpirun" other than the folder of a released ParaView?

John,

> in pqServerLauncher lines 643 to 651 ... when I comment these out, the server connection resumes as usual and all is well.

Interesting. I always assumed all scripts will block till the pvserver was done. If that's not the common case, I am okay with removing that extra check. Alternatively, I can add a new xml attribute that says that the script blocks or doesn't. That was if the script is supposed to block and the launch indeed fails, we can report the same to the user rather than just waiting for the connection. What do you think?

> As for the pvserver launch that you just mentioned regarding args etc.

Can you try the attached patch please?

> I apologise profusely for not fixing ...

No apologies needed :). Glad you caught them sooner rather than later.

Thanks,
Utkarsh.