Names of the different heads?

[linas]

Gabrieliau,

I learned that the "beorn rig" should be called "the dimitry head". So ... does "robo.blend" have a name? Can we name it? How about "standard-fs-face.anim_test.blend" -- looks vaguely eva-ish, an early eva prototype? Can we give it a name other than "standard-fs-face.anim_test.blend"

When I load standard-fs-face.anim_test.blend, it crashes:

  File "/hr/./robo_blender/src/outputs/state/ParametersOut.py", line 34, in <listcomp>
    if get_coeffs(store, bpy.data.meshes[mesh].shape_keys.key_blocks)
KeyError: 'bpy_prop_collection[key]: key "Neutral.001" not found'

During handling of the above exception, another exception occurred:

 File "/hr/./robo_blender/src/outputs/__init__.py", line 83, in initialize
    store = InstanceStore(fullconfig)
  File "/hr/./robo_blender/src/outputs/__init__.py", line 78, in __init__
    traceback.print_exc()
NameError: name 'traceback' is not defined

[Gaboose]

Just fixed in feb7438b9504a9778cbe01f9cb589c3a395d15c6 and 445607984ae297e99e8ceed02276fb8bb8dbadb3.

We can change names. By analog robo.blend may be called Ean's rig :) I think the neck construction in there is Dmitry bot's. Also, I'm pretty sure "standard-fs-face.anim_test.blend" is Beorn's rig of Dmitry. The face is generic, but the shapekeys and neck closely relate to Dmitry's motors.

I might be missing something though. Which Beorn rig are you talking about?

[linas]

I asked Beorn, he said this is dmitry: http://imagebin.ca/v/1ix1BxFq8UJ6 I'm confused by standard-fs-face.anim_test.blend which looks feminine in the fish-eye lens view, but looks masculine in the orthographic view.

I'd like to rename robo.blend to ean-head.blend and standard-fs-face.anim_test.blend to proto-dmitry,blend . I'm calling it proto-dmitry, because Vytas gave me a "beorns-rig.blend" file which looks like the pastebin above --I asked beorn "who is this?" and he said "dmitry" -- Vytas gave it to me because it works with Animations, but it can't do LookAround/TrackDev

[beornleonard]

I am also confused. The model in the pic is indeed Dmitry, as is " standard-fs-face.anim_test.blend". They are the same.

The reason for the more masculine look in the orthographic view is that the square jaw line becomes more prominent when perspective is removed.

[Gaboose]

The other reason why "standard-fs-face.anim_test.blend" doesn't look like Dmitry, because the face texture and mesh is not Dmitry's. It's a generic face we used in absence of Dmitry's head scan, to get started quicker :) Although the shapekeys there do represent motors in Dmitry robot.

[linas]

OK, I just renamed standard-fs-face.anim_test.blend to dmitry-mesh.anim_test.blend.

It may be geometrically identical to the other Dmitry's floating around out there, but behaviorally, it is not. Vytas gave me a Dmitry blender file that looks completely different, and actually works in Animations mode. By contrast, standard-fs-face.anim_test.blend aka dmitry-mesh.anim_test.blend crashes on load, and neither animations, nor eye tracking work.

After today's pull, I get this:

ROBO: Loading
Traceback (most recent call last):
  File "/robo_blender/src/outputs/__init__.py", line 76, in __init__
    self._store_instance(confentry["name"], self._build_single(confentry))
  File "/robo_blender/src/outputs/__init__.py", line 56, in _build_single
    return cls._get_class(confentry["class"])(confentry)
  File "/robo_blender/src/outputs/state/ParametersOut.py", line 106, in __init__
    self.processors.append(self.build_processor(singlebind))
  File "/robo_blender/src/outputs/state/ParametersOut.py", line 82, in build_processor
    blendergetter = blendergetter_builder(bindentry)
  File "/robo_blender/src/outputs/state/ParametersOut.py", line 35, in shkey_mesh
    ][0]
  File "/robo_blender/src/outputs/state/ParametersOut.py", line 34, in <listcomp>
    if get_coeffs(store, bpy.data.meshes[mesh].shape_keys.key_blocks)
KeyError: 'bpy_prop_collection[key]: key "Neutral.001" not found'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/robo_blender/src/startup.py", line 9, in <module>
    exec(compile(open(filename).read(), filename, 'exec'))
  File "/robo_blender/src/main.py", line 114, in <module>
    robo.execute()
  File "/robo_blender/src/main.py", line 70, in execute
    Utils.read_yaml(os.path.join(self.config_dir, "outputs.yaml"))
  File "/robo_blender/src/outputs/__init__.py", line 83, in initialize
    store = InstanceStore(fullconfig)
  File "/robo_blender/src/outputs/__init__.py", line 78, in __init__
    traceback.print_exc()
NameError: name 'traceback' is not defined

Anyway, this bug was just for naming the thing correctly, instead of un-crashing it. So I'm closing this bug.

[linas]

Huh. Bizarre. I just tried again, after the file rename. This time, it works! So I am guessing that there is something in the py_cache that had cached the old py scripts. Why is python would misbehaving like this? Is this a ros or blender thing?

[linas]

Argh.

Not so fast. Ran through all 4 animations, paused, unpaused and then stopped one. The next animation change crashed blender:

# Blender 2.69 (sub 0), Revision: unknown
bpy.ops.object.editmode_toggle()  # Operator

# backtrace
blender() [0x8d026d]
/lib/x86_64-linux-gnu/libc.so.6(+0x36c30) [0x7f703a516c30]
blender(MEM_freeN+0x19c) [0x1192dac]
blender() [0xe8bf4d]
blender() [0xe8cbeb]
blender(CustomData_free+0x3f) [0xe8cf4f]
blender(DM_release+0x97) [0xe44077]
blender() [0xeab2c9]
blender() [0xe47547]
blender(BKE_object_handle_update_ex+0x603) [0xf15873]
blender() [0xf52777]
blender(BKE_scene_update_tagged+0x6b) [0xf52a0b]
blender(RNA_function_call+0x12) [0x13ba9a2]
blender() [0xc58cb8]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f70400aa458]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x42b9) [0x7f704006ade9]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x7e15) [0x7f704006e945]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x886) [0x7f7040195516]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x225b46) [0x7f7040195b46]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f70400aa458]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x16381d) [0x7f70400d381d]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f70400aa458]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0xb4b01) [0x7f7040024b01]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f70400aa458]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x42b9) [0x7f704006ade9]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x7e15) [0x7f704006e945]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x7e15) [0x7f704006e945]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x7e15) [0x7f704006e945]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x7e15) [0x7f704006e945]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalFrameEx+0x7e15) [0x7f704006e945]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyEval_EvalCodeEx+0x886) [0x7f7040195516]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(+0x225b46) [0x7f7040195b46]
/usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0(PyObject_Call+0x68) [0x7f70400aa458]
blender(bpy_app_generic_callback+0x8c) [0xc5f7bc]
blender(BLI_callback_exec+0x2d) [0x102384d]
blender(BKE_scene_update_tagged+0x17) [0xf529b7]
blender(wm_event_do_notifiers+0x481) [0x8d6f21]
blender(WM_main+0x20) [0x8d22a0]
blender(main+0xc19) [0x8bb029]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f703a501ec5]
blender() [0x8cfc84]