no output from optics2rad

Dear list,
I have tried to run the optics2rad script, but the only output I get
is the information behind the # in the file from optics, implying that
rcalc in the optics2rad script, do not get any information...Have
anyone experience with this?

My approach is simply to write
optics2rad followed by the name of the file from optics.
Do I need further commands to run the optics2rad script?

Br
Anne Iversen

Hi Anne,

Thanks for sharing the file. For some reason, Optics dropped a critical line from its output, making the actual scene description illegal and breaking the optics2rad translator. Both BRTDfunc descriptors were missing a critical '.' in their description. Yours look like this:

void BRTDfunc ANTELIOSILVER6mm_front
10
       0.267 0.321 0.395
       0.678 0.655 0.576
       0 0 0

0
9 0 0 0 0 0 0 0 0 0

when they should look like this:

void BRTDfunc ANTELIOSILVER6mm_front
10
       0.267 0.321 0.395
       0.678 0.655 0.576
       0 0 0
       .
0
9 0 0 0 0 0 0 0 0 0

···

------------
I don't actually know what happened to the period, but reinserting it, optics2rad works again, producing:

void BRTDfunc ANTELIOSILVER6mm
10
         rR_clear rG_clear rB_clear
         0.678*tR_clear 0.655*tG_clear 0.576*tB_clear
      0 0 0
      window.cal
0
15 0 0 0 0 0 0 0 0 0
         0.267 0.321 0.395
         0.24 0.306 0.368

-----------

Best,
-Greg

From: Anne Iversen <[email protected]>
Date: May 9, 2009 12:52:44 PM PDT

Hi Greg,
The optics-file is attached. I have also attached the output piped to a file from running optics2rad with -xv added to the first line of the script. The file contains the output from both stdout and stderr.
The csh is the standard version(from July 13 2007) supplied with Ubuntu.
Thanks,
/Anne

On Sat, May 9, 2009 at 4:01 PM, Greg Ward <[email protected]> wrote:
Can you send me your Optics file?

-Greg

---------

From: Greg Ward <[email protected]>
Date: May 9, 2009 7:01:43 AM PDT

Can you send me your Optics file?

-Greg

Hi Greg,

I seem to have run into a similar issue as reported by Anne where optics2rad only sends out the header information of the optics file. I've checked the optics file and it has the "." you describe in the correct location:

void BRTDfunc SB60 Starphire_8_front
10
       0.050 0.057 0.073
       0.795 0.815 0.777
       0 0 0
       .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60 Starphire_8_back
10
       0.044 0.051 0.037
       0.795 0.815 0.777
       0 0 0
       .
0
9 0 0 0 0 0 0 0 0 0

Anyone else having the same results?
Thanks!
Best regards,
Chris Humann

···

On May 9, 2009, at 2:21 PM, Greg Ward wrote:

Hi Anne,

Thanks for sharing the file. For some reason, Optics dropped a critical line from its output, making the actual scene description illegal and breaking the optics2rad translator. Both BRTDfunc descriptors were missing a critical '.' in their description. Yours look like this:

void BRTDfunc ANTELIOSILVER6mm_front
10
     0.267 0.321 0.395
     0.678 0.655 0.576
     0 0 0

0
9 0 0 0 0 0 0 0 0 0

when they should look like this:

void BRTDfunc ANTELIOSILVER6mm_front
10
     0.267 0.321 0.395
     0.678 0.655 0.576
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

------------
I don't actually know what happened to the period, but reinserting it, optics2rad works again, producing:

void BRTDfunc ANTELIOSILVER6mm
10
       rR_clear rG_clear rB_clear
       0.678*tR_clear 0.655*tG_clear 0.576*tB_clear
    0 0 0
    window.cal
0
15 0 0 0 0 0 0 0 0 0
       0.267 0.321 0.395
       0.24 0.306 0.368

-----------

Best,
-Greg

From: Anne Iversen <[email protected]>
Date: May 9, 2009 12:52:44 PM PDT

Hi Greg,
The optics-file is attached. I have also attached the output piped to a file from running optics2rad with -xv added to the first line of the script. The file contains the output from both stdout and stderr.
The csh is the standard version(from July 13 2007) supplied with Ubuntu.
Thanks,
/Anne

On Sat, May 9, 2009 at 4:01 PM, Greg Ward <[email protected]> wrote:
Can you send me your Optics file?

-Greg

---------

From: Greg Ward <[email protected]>
Date: May 9, 2009 7:01:43 AM PDT

Can you send me your Optics file?

-Greg

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

Hi Chris,

One problem that I see is the name of the two materials contains a space after SB60. This would need to be fixed for a valid radiance material name.

-Jack

Chris Humann wrote:

···

Hi Greg,

I seem to have run into a similar issue as reported by Anne where optics2rad only sends out the header information of the optics file. I've checked the optics file and it has the "." you describe in the correct location:

void BRTDfunc SB60 Starphire_8_front
10
      0.050 0.057 0.073
      0.795 0.815 0.777
      0 0 0
      .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60 Starphire_8_back
10
      0.044 0.051 0.037
      0.795 0.815 0.777
      0 0 0
      .
0
9 0 0 0 0 0 0 0 0 0

Anyone else having the same results?
Thanks!
Best regards,
Chris Humann

On May 9, 2009, at 2:21 PM, Greg Ward wrote:

Hi Anne,

Thanks for sharing the file. For some reason, Optics dropped a critical line from its output, making the actual scene description illegal and breaking the optics2rad translator. Both BRTDfunc descriptors were missing a critical '.' in their description. Yours look like this:

void BRTDfunc ANTELIOSILVER6mm_front
10
     0.267 0.321 0.395
     0.678 0.655 0.576
     0 0 0

0
9 0 0 0 0 0 0 0 0 0

when they should look like this:

void BRTDfunc ANTELIOSILVER6mm_front
10
     0.267 0.321 0.395
     0.678 0.655 0.576
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

------------
I don't actually know what happened to the period, but reinserting it, optics2rad works again, producing:

void BRTDfunc ANTELIOSILVER6mm
10
       rR_clear rG_clear rB_clear
       0.678*tR_clear 0.655*tG_clear 0.576*tB_clear
    0 0 0
    window.cal
0
15 0 0 0 0 0 0 0 0 0
       0.267 0.321 0.395
       0.24 0.306 0.368

-----------

Best,
-Greg

From: Anne Iversen <[email protected]>
Date: May 9, 2009 12:52:44 PM PDT

Hi Greg,
The optics-file is attached. I have also attached the output piped to a file from running optics2rad with -xv added to the first line of the script. The file contains the output from both stdout and stderr.
The csh is the standard version(from July 13 2007) supplied with Ubuntu.
Thanks,
/Anne

On Sat, May 9, 2009 at 4:01 PM, Greg Ward <[email protected]> wrote:
Can you send me your Optics file?

-Greg

---------

From: Greg Ward <[email protected]>
Date: May 9, 2009 7:01:43 AM PDT

Can you send me your Optics file?

-Greg

_______________________________________________
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

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

Hi Jack,

Thanks, good eye. Unfortunately even with the material name fixed I'm still not getting output beyond the header.

Chris

···

On May 11, 2009, at 1:03 PM, Jack de Valpine wrote:

Hi Chris,

One problem that I see is the name of the two materials contains a space after SB60. This would need to be fixed for a valid radiance material name.

-Jack

Chris Humann wrote:

Hi Greg,

I seem to have run into a similar issue as reported by Anne where optics2rad only sends out the header information of the optics file. I've checked the optics file and it has the "." you describe in the correct location:

void BRTDfunc SB60 Starphire_8_front
10
     0.050 0.057 0.073
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60 Starphire_8_back
10
     0.044 0.051 0.037
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

Anyone else having the same results?
Thanks!
Best regards,
Chris Humann

On May 9, 2009, at 2:21 PM, Greg Ward wrote:

Hi Anne,

Thanks for sharing the file. For some reason, Optics dropped a critical line from its output, making the actual scene description illegal and breaking the optics2rad translator. Both BRTDfunc descriptors were missing a critical '.' in their description. Yours look like this:

void BRTDfunc ANTELIOSILVER6mm_front
10
    0.267 0.321 0.395
    0.678 0.655 0.576
    0 0 0

0
9 0 0 0 0 0 0 0 0 0

when they should look like this:

void BRTDfunc ANTELIOSILVER6mm_front
10
    0.267 0.321 0.395
    0.678 0.655 0.576
    0 0 0
    .
0
9 0 0 0 0 0 0 0 0 0

------------
I don't actually know what happened to the period, but reinserting it, optics2rad works again, producing:

void BRTDfunc ANTELIOSILVER6mm
10
      rR_clear rG_clear rB_clear
      0.678*tR_clear 0.655*tG_clear 0.576*tB_clear
   0 0 0
   window.cal
0
15 0 0 0 0 0 0 0 0 0
      0.267 0.321 0.395
      0.24 0.306 0.368

-----------

Best,
-Greg

From: Anne Iversen <[email protected]>
Date: May 9, 2009 12:52:44 PM PDT

Hi Greg,
The optics-file is attached. I have also attached the output piped to a file from running optics2rad with -xv added to the first line of the script. The file contains the output from both stdout and stderr.
The csh is the standard version(from July 13 2007) supplied with Ubuntu.
Thanks,
/Anne

On Sat, May 9, 2009 at 4:01 PM, Greg Ward <[email protected]> wrote:
Can you send me your Optics file?

-Greg

---------

From: Greg Ward <[email protected]>
Date: May 9, 2009 7:01:43 AM PDT

Can you send me your Optics file?

-Greg

_______________________________________________
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

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

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

Hi Chris,

Why is your description missing the "glass" descriptor Optics usually produces? The optics2rad script is a bit fragile to such oversights. Maybe you just took it out for brevity.

In any case, the optics2rad script doesn't like underscores in names any better than it likes Spaces. The only underscore you can have is before the final "_glass", "_front" or "_back". The issue is not with Radiance but with the rcalc program, which looks for the end of the name by searching for an underscore. Not much way around it, I'm afraid. All three names need to be identical as well, e.g.:

void glass SB60-Starphire-8_glass
0
3 .95 .95 .95

void BRTDfunc SB60-Starphire-8_front
10
       0.050 0.057 0.073
       0.795 0.815 0.777
       0 0 0
       .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60-Starphire-8_back
10
       0.044 0.051 0.037
       0.795 0.815 0.777
       0 0 0
       .
0
9 0 0 0 0 0 0 0 0 0

···

-------------------
Cheers,
-Greg

From: Chris Humann <[email protected]>
Date: May 11, 2009 12:54:01 PM PDT

Hi Greg,

I seem to have run into a similar issue as reported by Anne where optics2rad only sends out the header information of the optics file. I've checked the optics file and it has the "." you describe in the correct location:

void BRTDfunc SB60 Starphire_8_front
10
      0.050 0.057 0.073
      0.795 0.815 0.777
      0 0 0
      .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60 Starphire_8_back
10
      0.044 0.051 0.037
      0.795 0.815 0.777
      0 0 0
      .
0
9 0 0 0 0 0 0 0 0 0

Anyone else having the same results?
Thanks!
Best regards,
Chris Humann

Hi Greg,
Thanks for the response. I did take out the glass descriptor for brevity. I may have corrupted my optics2rad script somehow as it's still a no go even with the name changes you suggested.
Chris

···

On May 11, 2009, at 2:01 PM, Greg Ward wrote:

void glass SB60-Starphire-8_glass
0
3 .95 .95 .95

void BRTDfunc SB60-Starphire-8_front
10
     0.050 0.057 0.073
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60-Starphire-8_back
10
     0.044 0.051 0.037
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

Hi Chris,

Try doing the following. Take the radiance output from optics5 and run it through xform. For example:

    xform optics_output_filename > my_glass.rad
    optics2rad my_glass.rad

-Jack

Chris Humann wrote:

···

Hi Greg,
Thanks for the response. I did take out the glass descriptor for brevity. I may have corrupted my optics2rad script somehow as it's still a no go even with the name changes you suggested.
Chris

On May 11, 2009, at 2:01 PM, Greg Ward wrote:

void glass SB60-Starphire-8_glass
0
3 .95 .95 .95

void BRTDfunc SB60-Starphire-8_front
10
     0.050 0.057 0.073
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60-Starphire-8_back
10
     0.044 0.051 0.037
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

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

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

Thanks Jack,

That was the silver bullet! Despite reinstalling Greg's script I was still getting no where. I use Textmate for all my radiance scripting and perhaps it was adding a hidden character somewhere that the c-shell didn't like.

This is great, thanks again!

Chris

···

On May 11, 2009, at 2:50 PM, Jack de Valpine wrote:

Hi Chris,

Try doing the following. Take the radiance output from optics5 and run it through xform. For example:
xform optics_output_filename > my_glass.rad
optics2rad my_glass.rad
-Jack

Chris Humann wrote:

Hi Greg,
Thanks for the response. I did take out the glass descriptor for brevity. I may have corrupted my optics2rad script somehow as it's still a no go even with the name changes you suggested.
Chris

On May 11, 2009, at 2:01 PM, Greg Ward wrote:

void glass SB60-Starphire-8_glass
0
3 .95 .95 .95

void BRTDfunc SB60-Starphire-8_front
10
     0.050 0.057 0.073
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60-Starphire-8_back
10
     0.044 0.051 0.037
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

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

--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Hi Chris,

Good glad it worked. It actually only just occurred to me that this might be a way to get a well formated radiance description that rcalc would be happy with. As Greg mentioned optics2rad calls on rcalc to do most of the work. Rcalc is very sensitive to the input format that it expects, unfortunately this can be a bit difficult to track down. Note I did also do an export of some dummy data from optics5 and this went into optics2rad without any problem. So it may be that if you are using some intermediate script in your process that it is somehow munging the format along the way. One simple thing to check for is if you have a carriage return at the last line of the input file that your script is generating or outputing for optics2rad processing.

-Jack

Chris Humann wrote:

···

Thanks Jack,

That was the silver bullet! Despite reinstalling Greg's script I was still getting no where. I use Textmate for all my radiance scripting and perhaps it was adding a hidden character somewhere that the c-shell didn't like.

This is great, thanks again!

Chris

On May 11, 2009, at 2:50 PM, Jack de Valpine wrote:

Hi Chris,

Try doing the following. Take the radiance output from optics5 and run it through xform. For example:

    xform optics_output_filename > my_glass.rad
    optics2rad my_glass.rad

-Jack

Chris Humann wrote:

Hi Greg,
Thanks for the response. I did take out the glass descriptor for brevity. I may have corrupted my optics2rad script somehow as it's still a no go even with the name changes you suggested.
Chris

On May 11, 2009, at 2:01 PM, Greg Ward wrote:

void glass SB60-Starphire-8_glass
0
3 .95 .95 .95

void BRTDfunc SB60-Starphire-8_front
10
     0.050 0.057 0.073
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

void BRTDfunc SB60-Starphire-8_back
10
     0.044 0.051 0.037
     0.795 0.815 0.777
     0 0 0
     .
0
9 0 0 0 0 0 0 0 0 0

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

--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction
    _______________________________________________
Radiance-general mailing list
[email protected] <mailto:[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
  
--
# Jack de Valpine
# president
#
# visarc incorporated
# http://www.visarc.com
#
# channeling technology for superior design and construction