error msg while running dexen from output file

[Zengyuan]

the lux evaluation using Radiance in Houdini works. However, once it
is run on dexen, error msg appearred as follows:

ActId: 16
Transact: SlaveRecvTransaction
TransactId: 6
Input Size: 10
Slave Name: SLAVE1
Task Name: slave_tasks.eval_tasks.EvalLuxTask
--------------Task Stdout---------------
--------------Task Stderr---------------
File "C:\AkiDTS\dexen-32-hou-0.3.3.7\dexen\system\node\slave
\executor.py", line 48, in _execute
inds = slave_task.__execute__(master_state, transact.get_inds())
File "c:\users\chenzy~1\appdata\local\temp\dexen\nodes\t1_j9sals
\slave_tasks\eval_tasks.py", line 43, in __execute__
ind.eval_lux = run_houdini_eval(ind, "eval_lux.hipnc")
File "c:\users\chenzy~1\appdata\local\temp\dexen\nodes\t1_j9sals
\slave_tasks\eval_tasks.py", line 31, in run_houdini_eval
score =
score_node.geometry().attribValue(common.SCORE_ATTRIB_NAME)
File "C:\Program Files\Side Effects Software\Houdini 11.0.733/
houdini/python2.5libs\hou.py", line 15280, in attribValue
return _hou.Geometry_attribValue(*args)



Pls help.

[ckw]

Is this from one of the example files ? If not, this is probably
because one of your phenotype is an invalid one, that gives error in
the houdini network. e.g. some bad surfaces resulting in a error. You
must remember the houdini network work once does not mean it will work
10 000 times, cause the genes are always changing, so try to archive
your .bgeo to see your resultant phenotype and genotype. Debug it, put
the genotype into the houdini network again and see what is going
wrong. This is probably not a Dexen error but is your schema error.

kianwee

[Zengyuan]

ty kianwee,

I have found the problem. It is in the Houdini model file where the
attributepromote node, I didn't specify the new name "score" to
replace the old one. Now the problem is solved, everything seems
running ok.

Zengyuan

[Tungsing9]

Hi kianwee

I also encountered this problem.

ActId: 16
> > > Transact: SlaveRecvTransaction
> > > TransactId: 6
> > > Input Size: 10
> > > Slave Name: SLAVE1
> > > Task Name: slave_tasks.eval_tasks.EvalLuxTask
> > > --------------Task Stdout---------------
> > > --------------Task Stderr---------------
> > > File "C:\AkiDTS\dexen-32-hou-0.3.3.7\dexen\system\node\slave
> > > \executor.py", line 48, in _execute
> > > inds = slave_task.__execute__(master_state, transact.get_inds())
> > > File "c:\users\chenzy~1\appdata\local\temp\dexen\nodes\t1_j9sals
> > > \slave_tasks\eval_tasks.py", line 43, in __execute__
> > > ind.eval_lux = run_houdini_eval(ind, "eval_lux.hipnc")
> > > File "c:\users\chenzy~1\appdata\local\temp\dexen\nodes\t1_j9sals
> > > \slave_tasks\eval_tasks.py", line 31, in run_houdini_eval
> > > score =
> > > score_node.geometry().attribValue(common.SCORE_ATTRIB_NAME)
> > > File "C:\Program Files\Side Effects Software\Houdini 11.0.733/
> > > houdini/python2.5libs\hou.py", line 15280, in attribValue
> > > return _hou.Geometry_attribValue(*args)

For my case, the eval_task, only fails sometimes.
I intend to debug it, but how do we know which individual IND number
from the Act ID and Transact ID?
I would want to know the individual number of the phenotype so that i
could test with its parameter genes again in Houdini.

I tried to vary the genes randomly and test it, it all seems to be
working fine in Houdini, and the evaluation is also working too.
Thus, i think i need to test with the specific parameters that causes
the failure.

I tried looking at the log file and output file, but seems that the
indivdual number is not included. How do we find out the individual
number from the above information?


Tungsing

[ckw]

the genes shld be archive in the archive just need to retrieve it from
the network, exactly how to do it I am not sure, you need to ask cihat
or look at the help for retrieving archive files

kianwee

On May 31, 2:01 pm, Zengyuan <chenzy...@hotmail.com> wrote: