rpiece error

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going on
here?

It looks like your system isn't case sensitive. Rpiece is interpreting that as a request for a rendering in 1M parts.

Mark

···

On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going on
here?

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Hi Mark,

But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?

···

On Thu, March 4, 2010 2:14 pm, Mark Stock wrote:

It looks like your system isn't case sensitive. Rpiece is
interpreting that as a request for a rendering in 1M parts.

Mark

On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see
them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going
on
here?

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

===================
Rob Guglielmetti
www.rumblestrip.org

Rob,

That's the easiest explanation for the symptoms that you are seeing. I hope someone else can explain why it got triggered on your system.

Mark

···

On Thu, 4 Mar 2010, Rob Guglielmetti wrote:

Hi Mark,

But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?

On Thu, March 4, 2010 2:14 pm, Mark Stock wrote:

It looks like your system isn't case sensitive. Rpiece is
interpreting that as a request for a rendering in 1M parts.

Mark

On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see
them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going
on
here?

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

===================
Rob Guglielmetti
www.rumblestrip.org

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Hi Rob,

Are you setting -X and -Y in @args? Are you using a syncfile with -F?

-Jack

···

--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction

Mark Stock wrote:

Rob,

That's the easiest explanation for the symptoms that you are seeing. I hope someone else can explain why it got triggered on your system.

Mark

On Thu, 4 Mar 2010, Rob Guglielmetti wrote:

Hi Mark,

But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?

On Thu, March 4, 2010 2:14 pm, Mark Stock wrote:

It looks like your system isn't case sensitive. Rpiece is
interpreting that as a request for a rendering in 1M parts.

Mark

On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see
them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going
on
here?

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

===================
Rob Guglielmetti
www.rumblestrip.org

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Hi Jack,

I am specifying -x and -y (lowercase) in the args, and specifying a syncfile
with -F (in args). Mark thinks that my system is somehow interpreting -x
1024 -y 1024 as -X 1024 and -Y 1024.

?

···

On 3/4/10 2:59 PM, "Jack de Valpine" <[email protected]> wrote:

Hi Rob,

Are you setting -X and -Y in @args? Are you using a syncfile with -F?

-Jack

--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction

Mark Stock wrote:

Rob,

That's the easiest explanation for the symptoms that you are seeing. I
hope someone else can explain why it got triggered on your system.

Mark

On Thu, 4 Mar 2010, Rob Guglielmetti wrote:

Hi Mark,

But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?

On Thu, March 4, 2010 2:14 pm, Mark Stock wrote:

It looks like your system isn't case sensitive. Rpiece is
interpreting that as a request for a rendering in 1M parts.

Mark

On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see
them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going
on
here?

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

===================
Rob Guglielmetti
www.rumblestrip.org

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Hey Rob,

Well it does seem a bit odd. I believe that rpiece defaults to -X = 4 and -Y = 4, if nothing is specified on the command line.

It does look like too many copies are being forked though, thus all the bash shells getting spawned and the error message for fork indicating that no more resources are available.

Perhaps as one test it would be worth explicitly setting -X and -Y and seeing what happens? Is this a standard system you are running on or a cluster of some sort?

-Jack

···

--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction

Guglielmetti, Robert wrote:

Hi Jack,

I am specifying -x and -y (lowercase) in the args, and specifying a syncfile
with -F (in args). Mark thinks that my system is somehow interpreting -x
1024 -y 1024 as -X 1024 and -Y 1024.

?

On 3/4/10 2:59 PM, "Jack de Valpine" <[email protected]> wrote:

Hi Rob,

Are you setting -X and -Y in @args? Are you using a syncfile with -F?

-Jack

--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction

Mark Stock wrote:
    

Rob,

That's the easiest explanation for the symptoms that you are seeing. I
hope someone else can explain why it got triggered on your system.

Mark

On Thu, 4 Mar 2010, Rob Guglielmetti wrote:

Hi Mark,

But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?

On Thu, March 4, 2010 2:14 pm, Mark Stock wrote:
        

It looks like your system isn't case sensitive. Rpiece is
interpreting that as a request for a rendering in 1M parts.

Mark

On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see
them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going
on
here?

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

===================
Rob Guglielmetti
www.rumblestrip.org

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
      

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
    
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Actually now that I think about this, the forking has to do with something else, -X and -Y only specify how an image gets divided up not processes.... (it has been awhile since I have actually looked at how this works).

Perhaps another test would be to run (1) rpiece instance with the arguments explicitly at the command line (eg not in @args)....

-Jack

···

--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction

Jack de Valpine wrote:

Hey Rob,

Well it does seem a bit odd. I believe that rpiece defaults to -X = 4 and -Y = 4, if nothing is specified on the command line.

It does look like too many copies are being forked though, thus all the bash shells getting spawned and the error message for fork indicating that no more resources are available.

Perhaps as one test it would be worth explicitly setting -X and -Y and seeing what happens? Is this a standard system you are running on or a cluster of some sort?

-Jack
--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction
  
Guglielmetti, Robert wrote:

Hi Jack,

I am specifying -x and -y (lowercase) in the args, and specifying a syncfile
with -F (in args). Mark thinks that my system is somehow interpreting -x
1024 -y 1024 as -X 1024 and -Y 1024.

?

On 3/4/10 2:59 PM, "Jack de Valpine" <[email protected]> wrote:

Hi Rob,

Are you setting -X and -Y in @args? Are you using a syncfile with -F?

-Jack

--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction

Mark Stock wrote:
    

Rob,

That's the easiest explanation for the symptoms that you are seeing. I
hope someone else can explain why it got triggered on your system.

Mark

On Thu, 4 Mar 2010, Rob Guglielmetti wrote:

Hi Mark,

But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?

On Thu, March 4, 2010 2:14 pm, Mark Stock wrote:
        

It looks like your system isn't case sensitive. Rpiece is
interpreting that as a request for a rendering in 1M parts.

Mark

On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see
them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going
on
here?

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

===================
Rob Guglielmetti
www.rumblestrip.org

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
      

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
    
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
  

------------------------------------------------------------------------

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Is it possible the code that generates the @-file is putting an upper case '-X' in it? Is it perhaps a Windows shell?

Randolph

···

On 2010-03-04 13:21:03 -0800, Rob Guglielmetti said:

Hi Mark,

But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?

On Thu, March 4, 2010 2:14 pm, Mark Stock wrote:

It looks like your system isn't case sensitive. Rpiece is
interpreting that as a request for a rendering in 1M parts.

Mark

On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

When I issue the command, a zillion bash shells get spawned (can see
them in
top) and after a few seconds the following errors print to the screen:

./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found

...followed by a bunch of garbage characters. Anyone know what's going
on
here?

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

===================
Rob Guglielmetti
www.rumblestrip.org

--
Randolph Fritz
  design machine group, architecture department, university of washington
[email protected] -or- [email protected]

I used OSX to create a simple args file from the command line for testing purposes, so there's no case funny-stuff going on in that regard. No, not a Windows shell (not at all!). I didn't have a chance to just test with all the args on the command line today, as Jack recommended, but will try tomorrow.

- Rob

···

On Mar 4, 2010, at 8:12 PM, R Fritz wrote:

Is it possible the code that generates the @-file is putting an upper case '-X' in it? Is it perhaps a Windows shell?

Randolph

On 2010-03-04 13:21:03 -0800, Rob Guglielmetti said:

Hi Mark,
But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?
On Thu, March 4, 2010 2:14 pm, Mark Stock wrote:

It looks like your system isn't case sensitive. Rpiece is
interpreting that as a request for a rendering in 1M parts.
Mark
On Thu, 4 Mar 2010, Guglielmetti, Robert wrote:

Anyone seen this before? I issue a simple rpiece command, like:
Rpiece @args &
The args file has some basic stuff in it:
-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct
When I issue the command, a zillion bash shells get spawned (can see
them in
top) and after a few seconds the following errors print to the screen:
./rpiece: fork: Resource temporarily unavailable
./rpiece: line 3: RADIANCE: command not found
./rpiece: line 4: -vtv: command not found
./rpiece: line 7: -Y: command not found
...followed by a bunch of garbage characters. Anyone know what's going
on
here?
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

===================
Rob Guglielmetti
www.rumblestrip.org

--
Randolph Fritz
design machine group, architecture department, university of washington
[email protected] -or- [email protected]

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

You have not specified either the "-X -Y" resolution or an existing
syncfile that rpiece should use to coordinate the processes. Rpiece
should treat that as a command error but apparently it doesn't.

Anyway, add either one of the options to tell rpiece how to chop up
the image and you should be fine.

Thomas

···

On Thu, Mar 4, 2010 at 9:04 PM, Guglielmetti, Robert <[email protected]> wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

Careful, Rob.

The bash is case sensitive, but the OS X file system is not (by default).

Thomas

···

On Thu, Mar 4, 2010 at 9:21 PM, Rob Guglielmetti <[email protected]> wrote:

Hi Mark,

But my system *is* case sensitive. It's running OSX and it's a standard
POSIX compliant bash shell. You mean it's interpreting the -x as -X?

Hi Thomas,

I did specify a syncfile. Sorry I guess I left that out in my summary. There is a -F (syncfile) in the args too. The syncfile was simply created at the bash prompt with "echo 1 8 > syncfile", so it should not have any character or line ending issues. I will try leaving it all out there on the command line when I get in to the office today.

Thomas you mention that OSX is not case sensitive by default? I have never seen this behavior. How does one ensure that it is behaving in a case sensitive manner? Case insensitivity is kind of a problem with rpiece since there are -x and -X, -y and -Y options that are important!

···

________________________________________
From: [email protected] [[email protected]] On Behalf Of Thomas Bleicher [[email protected]]
Sent: Friday, March 05, 2010 2:43 AM
To: Radiance general discussion
Subject: Re: [Radiance-general] rpiece error

On Thu, Mar 4, 2010 at 9:04 PM, Guglielmetti, Robert <[email protected]> wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

You have not specified either the "-X -Y" resolution or an existing
syncfile that rpiece should use to coordinate the processes. Rpiece
should treat that as a command error but apparently it doesn't.

Anyway, add either one of the options to tell rpiece how to chop up
the image and you should be fine.

Thomas

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Hi Rob,

Thomas is referring to the fact that filenames on the default OS X filesystem are not case-sensitive, so "Foo.dat" is the same as "fOo.DaT". If you create the former, you can refer to it as the latter. It will still show up with the case you created it with, but the system silently ignores case when you refer to it. You can't have both "Foo.dat" and "fOo.dat" in the same directory -- creating the latter would overwrite the former.

This has nothing to do with what goes into a bash script, or how rpiece gets its options. Only on older Windows systems is case ignored in the command line itself. I don't know when that stopped being true, but I don't think that's true any longer.

I am as puzzled by the behavior you're seeing as everyone else. Without having all your files and scripts, though, it's pretty difficult to reproduce.

Cheers,
-Greg

···

From: "Guglielmetti, Robert" <[email protected]>
Date: March 5, 2010 6:25:02 AM PST

Hi Thomas,

I did specify a syncfile. Sorry I guess I left that out in my summary. There is a -F (syncfile) in the args too. The syncfile was simply created at the bash prompt with "echo 1 8 > syncfile", so it should not have any character or line ending issues. I will try leaving it all out there on the command line when I get in to the office today.

Thomas you mention that OSX is not case sensitive by default? I have never seen this behavior. How does one ensure that it is behaving in a case sensitive manner? Case insensitivity is kind of a problem with rpiece since there are -x and -X, -y and -Y options that are important!
________________________________________
From: [email protected] [[email protected]] On Behalf Of Thomas Bleicher [[email protected]]

On Thu, Mar 4, 2010 at 9:04 PM, Guglielmetti, Robert > <[email protected]> wrote:

Anyone seen this before? I issue a simple rpiece command, like:

Rpiece @args &

The args file has some basic stuff in it:

-x 1024 -y 1024 -vf foo.vf -o foo.hdr foo.oct

You have not specified either the "-X -Y" resolution or an existing
syncfile that rpiece should use to coordinate the processes. Rpiece
should treat that as a command error but apparently it doesn't.

Anyway, add either one of the options to tell rpiece how to chop up
the image and you should be fine.

Thomas