search

madhuneal / ppss

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

output directories do not work #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. ppss -d /root/tmp/wav -o /root/tmp/mp3s -c 'lame '
2.
3.

What is the expected output? What do you see instead?
mp3 files should go into /root/tmp/mp3s They go into /root/tmp/wav instead.

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

Please provide any additional information below.

Original issue reported on code.google.com by r3su...@gmail.com on 24 Feb 2011 at 8:34

GoogleCodeExporter commented 9 years ago 
Using Bash.  Opensuse linux. 
GNU bash, version 4.1.7(1)-release (x86_64-suse-linux-gnu)

Original comment by r3su...@gmail.com on 24 Feb 2011 at 8:43

GoogleCodeExporter commented 9 years ago

Original comment by Louwrentius on 16 Mar 2011 at 11:12

GoogleCodeExporter commented 9 years ago 
This is not how PPSS works, but I understand the confusion and I need to 
clarify this. 

I would do this:

ppss -d /root/tmp/wav -c 'lame "$ITEM" /root/tmp/mp3s/"$ITEM".mp3' 

Do not supply the output directory to PPSS but to Lame. Lame decides where to 
put the output file, so if you don't   want to use the source directory, use 
this solution.

Original comment by Louwrentius on 16 Mar 2011 at 11:23

GoogleCodeExporter commented 9 years ago 
Agreed.  That is what I am doing now and it works ok.  I agree a clarification 
should be added to avoid confusion.  It makes sense to have the program do the 
direction of output.

Original comment by r3su...@gmail.com on 18 Mar 2011 at 7:56

GoogleCodeExporter commented 9 years ago 
I take that back it still does not work.  It's the pathing is all screwed up.
Keeps putting // in there for some reason in the can't init output line.

If I take the leading / out from lame output it still does it.

Status:         FAILURE

===== PPSS Item Log File =====
Host:           chewey
Process:        7710
Item:           /data/ppss/wav/wannabe.mp3.wav
Start date:     Mar 24 01:11:43

Can't init outfile '/data/ppss/mp3//data/ppss/wav/wannabe.mp3.wav.mp3'

Status:         FAILURE

ppss@chewey:~> ./ppss -d /data/ppss/wav -c 'lame "$ITEM" 
/data/ppss/mp3/"$ITEM".mp3'

Original comment by spe...@gmail.com on 24 Mar 2011 at 6:18

GoogleCodeExporter commented 9 years ago 
Leave out the prepending path use just "$ITEM".Mp3

Original comment by Louwrentius on 24 Mar 2011 at 10:07

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I don't know.What do you think?

I can do that but what is the point to mix up all the data.
The idea would be to read input from directory and output goes in another.

/data/ppss/wav  (Inputs)
/data/ppss/mp3  (Output)

Seems the problem for most para processes would be to want all nodes to hit a 
GFS2, NFS share for common data share and ssh to nodes to distribute process 
but all mount common data for input and output  like /data in this example

Maybe just a suggestion to leave the leading paths out of the $ITEM variable.  
Let the -c options do that for more flexibility.  Let ITEM be just the filename 
alone?

And then just key on getting a standard ssh between nodes to work ok for the 
processing.

What is your take on that?  I would think less coding for you and most folks 
could work with that.  Even if they did not need nfs,gfs2 etc,  it would still 
all work if just standalone directories were used or eve sshfs etc.

Original comment by spe...@gmail.com on 27 Mar 2011 at 5:13

GoogleCodeExporter commented 9 years ago 
FYI

./ppss -d /data/ppss/wav -c 'lame "$ITEM" /data/ppss/mp3/"$OUTPUT_FILE".mp3'

Worked for my purposes as stated above.

Original comment by spe...@gmail.com on 27 Mar 2011 at 6:01

GoogleCodeExporter commented 9 years ago 
4 months after but that is how ppss should work and is designed.

Original comment by Louwrentius on 7 Aug 2011 at 9:44