Ticket 283 - Inoperative output file format conversion characters
Summary: Inoperative output file format conversion characters
Status: RESOLVED FIXED
Alias: None
Product: Slurm
Classification: Unclassified
Component: Documentation (show other tickets)
Version: 2.5.x
Hardware: IBM BlueGene Linux
: 4 - Minor Issue
Assignee: David Bigagli
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2013-05-08 06:07 MDT by Don Lipari
Modified: 2013-05-13 07:18 MDT (History)
1 user (show)

See Also:
Site: LLNL
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---


Attachments

Note You need to log in before you can comment on or make changes to this ticket.
Description Don Lipari 2013-05-08 06:07:17 MDT
The following output file format conversion characters are not working on BG/Q:  %N, %n, and %t
Comment 1 Danny Auble 2013-05-08 06:20:00 MDT
Do you mean the srun -o option?  If so I would say this is an srun issue not a bluegene plugin issue.

from http://slurm.schedmd.com/srun.html (Look for IO Redirection) last line is the important one.

For BGQ srun only supports stdin to 1 task running on the system. By default it is taskid 0 but can be changed with the -i<taskid> as described below, or --launcher-opts="--stdinrank=<taskid>". Outside of the taskid option none of the options below are available for a BGQ system.

Let me know if this is documentation needs to be updated.  If this is the srun output options you are talking about I don't think this is possible.
Comment 2 Don Lipari 2013-05-08 06:31:55 MDT
(In reply to comment #1)
> Do you mean the srun -o option?  If so I would say this is an srun issue not
> a bluegene plugin issue.
> 
> from http://slurm.schedmd.com/srun.html (Look for IO Redirection) last line
> is the important one.
> 
> For BGQ srun only supports stdin to 1 task running on the system. By default
> it is taskid 0 but can be changed with the -i<taskid> as described below, or
> --launcher-opts="--stdinrank=<taskid>". Outside of the taskid option none of
> the options below are available for a BGQ system.
> 
> Let me know if this is documentation needs to be updated.  If this is the
> srun output options you are talking about I don't think this is possible.

It is the srun option I was referring to.  And the problem is unique to BG/Q - all six specifiers work fine on our Linux clusters.  On BG/Q, %J, %j, and %s work as advertised.
Comment 3 Danny Auble 2013-05-08 06:35:58 MDT
So the line that says 

"Outside of the taskid option none of the options below are available for a BGQ system."

Is obviously not clear enough :)?  I suppose it should be spelled out better.  Since it is impossible for us to create a different file for each node or task.  

Would you agree?  If so I can change this to documentation.  If you have a suggestion of what it should read I can put it in the srun man page as well as the user guide on the bluegene page as well.
Comment 4 Don Lipari 2013-05-08 06:45:57 MDT
(In reply to comment #3)
> So the line that says 
> 
> "Outside of the taskid option none of the options below are available for a
> BGQ system."
> 
> Is obviously not clear enough :)?  I suppose it should be spelled out
> better.  Since it is impossible for us to create a different file for each
> node or task.  
> 
> Would you agree?  If so I can change this to documentation.  If you have a
> suggestion of what it should read I can put it in the srun man page as well
> as the user guide on the bluegene page as well.

Sorry.  It is confusing.  I read that "none of the options below are available for a BGQ system".  But then -o filename works fine.  So does -o filename.%s.

You can close the ticket.  I suggest moving the "not supported on BG/Q" line to refer just to %N, %n, and %t.
Comment 5 Danny Auble 2013-05-08 06:51:10 MDT
Yeah I can see how it is confusing.  It took me a couple of times reading it before I really got it.  Especially since some of the options as you mention are supported.  I'll spell it out better by each of the items so it is clearer.  I'll keep the ticket open until that happens.
Comment 6 David Bigagli 2013-05-13 07:18:41 MDT
The documentation has been fixed in the commit d510ead6c0cbd7f0e25707334b5f68642d6f36af in 2.5 branch.
Should you have a better idea how to document it please let us know.

David