[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-user] Who can I talk to about writing a target configuration?
|
Dave,
I don't know if any of this will help you...
I'm developing a target system configurations for TACC's Stampede
machine w/ Doug James which is a modified SLURM based system. So like
you I copied the generic-slurm-batch XML file to get started.
I'm working with a PTP development environment setup as described in the
PTP wiki so I have all the PTP source code in my workspace. My
edu.utexas.tacc.stampede.slurm.batch.xml file is in the
org.eclipse.ptp.rm.jaxb.contrib's project in its data directory along
with the existing LoneStar XML file. I've added the XML file to the
plugin.xml file as another extension.
<JAXBResourceManagerConfiguration
configurationFile="data/edu.utexas.tacc.stampede.slurm.batch.xml"
name="edu.utexas.tacc.stampede.slurm.batch">
</JAXBResourceManagerConfiguration>
Naturally I had to modify the XML file to the particulars of the TACC
Stampede system which included new attributes and different MPI prefix
commands, etc.
I find it very useful to see the generated batch script file contents
using the "View Script" button on the bottom of each launch tab page. In
your note below you have the "View Configuration" which I find less useful.
To see the generated batch script file in your test project directory
which should match the "View Script" then change from <script
insertEnvironmentAfter="35"> to <script insertEnvironmentAfter="35"
deleteAfterSubmit="false"> and do a Synchronize. It should also be in
the remote .eclipsesetting directory (I think).
To better see what is going on do the following: Preferences > Parallel
Tools > Target Configurations and check all entries under
Parser/Tokenizer Debugging Options and also under Command Debugging
Options. The latter shows you the command that is being executed on the
target system.
Hope this begins to help.
Bri
Dr. David E Hudak wrote:
Hi All,
After seeing the interactive debugging working on Trestles, I wanted to try it with my cluster.
So, I created a new target configuration based on the trestles configuration. I renamed it and changed the location of torque to match my system.
I tried to run a test, but got this error:
654e7784-91cf-4204-b292-4f6908ca8184: FAILED
qsub: script file 'nodes=1:ppn=32,mem=20gb,walltime=00:30:00' cannot be loaded - No such file or directory
In general, is there any documentation for people who want to create their own target configuration? Specifically, does anyone have any idea what I should try next?
Thanks,
Dave
Resource_List.mem=20gb
Resource_List.nodes=1:ppn=32
Resource_List.walltime=00:30:00
bindir=/usr/local/torque/2.5.12/bin/
control.address=oakley.osc.edu
control.user.name=dhudak
control.working.dir=/nfs/07/dhudak
current_controller=Basic.Settings
debuggerArgs=--port=51283 --host=localhost --debugger=gdb-mi
debuggerExecutablePath=/nfs/07/dhudak/.eclipsesettings/sdm
debuggerId=org.eclipse.ptp.debug.sdm
enabled_Basic.Settings=Account_Name Resource_List.mem Resource_List.nodes Resource_List.walltime destination modules mpiCommand mpiNumberOfProcesses
executableDirectory=/nfs/07/dhudak/ptp-test
executablePath=/nfs/07/dhudak/ptp-test/test
invalid_Basic.Settings=script_path
launchMode=debug
modules=#%PTP_EMS_v1%#~#%#~=
mpiCommand=mpirun
mpiNumberOfProcesses=4
mpiPrefix=${ptp_rm:mpiCommand#value} -np ${ptp_rm:mpiNumberOfProcesses#value}
org.eclipse.debug.core.SOURCE_PATH_COMPUTER_ID=org.eclipse.ptp.debug.core.sourcePathComputer
org.eclipse.debug.core.appendEnvironmentVariables=true
org.eclipse.ptp.launch.ATTR_AUTO_RUN_COMMAND=false
org.eclipse.ptp.launch.ATTR_CONSOLE=true
org.eclipse.ptp.launch.ATTR_COPY_EXECUTABLE_FROM_LOCAL=false
org.eclipse.ptp.launch.ATTR_DEBUGGER_HOST=localhost
org.eclipse.ptp.launch.ATTR_REMOTE_EXECUTABLE_PATH=/nfs/07/dhudak/ptp-test/test
org.eclipse.ptp.launch.ATTR_SYNC_AFTER=false
org.eclipse.ptp.launch.ATTR_SYNC_BEFORE=false
org.eclipse.ptp.launch.ATTR_SYNC_RULES=[]
org.eclipse.ptp.launch.CONFIGURATION_NAME=edu.osc.oakley.torque.interactive.openmpi
org.eclipse.ptp.launch.CONNECTION_NAME=oakley
org.eclipse.ptp.launch.DEBUGGER_ARGS=--port=51484 --host=localhost --debugger=gdb-mi
org.eclipse.ptp.launch.DEBUGGER_EXECUTABLE_PATH=/nfs/07/dhudak/.eclipsesettings/sdm
org.eclipse.ptp.launch.DEBUGGER_ID=org.eclipse.ptp.debug.sdm
org.eclipse.ptp.launch.DEBUGGER_SDM_BACKEND=gdb-mi
org.eclipse.ptp.launch.DEBUGGER_SDM_EXECUTABLE=/usr/local/bin/sdm
org.eclipse.ptp.launch.DEBUGGER_START_MODE=run
org.eclipse.ptp.launch.DEBUGGER_USE_BUILTIN_SDM=true
org.eclipse.ptp.launch.PROJECT_ATTR=ptp-test
org.eclipse.ptp.launch.REMOTE_SERVICES_ID=org.eclipse.ptp.remote.RemoteTools
org.eclipse.ptp.launch.RESOURCE_MANAGER_NAME=6eb9b433-c035-3609-a2b0-4a99b39baf6e
org.eclipse.ptp.launch.STOP_IN_MAIN=true
org.eclipse.ptp.launch.SYSTEM_TYPE=TORQUE
ptpDirectory=/nfs/07/dhudak/.eclipsesettings
queues=[longparallel, hugemem, batch, longserial, parallel, gpu, serial]
valid_Basic.Settings=Account_Name Resource_List.mem Resource_List.nodes Resource_List.walltime bindir control.address control.queue.name control.user.name control.working.dir current_controller debuggerId destination enabled_Basic.Settings executableDirectory executablePath invalid_Basic.Settings launchMode modules mpiCommand mpiNumberOfProcesses mpiPrefix ptpDirectory queues valid_Basic.Settings visible_Basic.Settings working.directory
visible_Basic.Settings=Account_Name Resource_List.mem Resource_List.nodes Resource_List.walltime destination modules mpiCommand mpiNumberOfProcesses
working.directory=/nfs/07/dhudak
---
David E. Hudak, Ph.D. dhudak@xxxxxxx
Senior Research Scientist
Ohio Supercomputer Center
http://www.osc.edu/~dhudak
_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user
