I am using S3D regularly, and developed a USB user interface that allows me to adjust S3D parameters such as focal plane using a contour express dial.
I have stopped using scale factor by disabling the keyboard scroll, and switching to z translation.
I am finding that I need to adjust the focal plane a lot.? Usually it is between the clipping planes, but when I do z translations it normally gets between the camera and the near clipping plane, or out past the far clipping plane.
For S3D animations I can work around it. For interactive use, people are having major eye strain.
I would like to modify the chimera code to automatically adjust the focal plane as the clipping planes change.
Can you point me to the area of code where I could make the change?
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine ===========================================================================
Hi Matt,
Here’s some Python that will update the focal plane position to always lie midway between near and far clip planes.
If you zoom by moving a map or molecule closer to you (z translation) then visually the map should move from behind the screen to be in front of the screen so it looks like it is coming closer. In other words the map moves forward and the focal plane that defines the position of the screen stays fixed. That is normal Chimera behavior. The above script will defeat that. You will move the map closer to you in z, but what you will see in stereo is that the map gets bigger, but no closer. It instead feels like a magical scaling of the map, rather than getting closer to it. This isn’t natural, but I understand that because of the limited 3d depth with stereo viewing it is necessary to do something to avoid uncomfortable stereo where the models are too far in front of the screen. An optimal solution is more subtle than the above script. In fact the above script won’t prevent getting the front surface of the map too close for stereo viewing because it keeps the focal plane at the map midpoint in z. The front of the map can still get close to your eye and the stereo will not work. Basically you want to avoid having the front visible part of the models from getting too close to your eye where the stereo glasses don’t work (because the display screen is not wide enough). We have not worked on techniques to avoid stereo interactive viewing limitations. But the normal Chimera zoom uses scale factor, not z-translation, so that is the main way this problem is avoided. But you are using z-translation instead of the normal Chimera zooming and that is why you encounter this problem.
Tom
On Apr 20, 2015, at 8:59 PM, Dougherty, Matthew T wrote:
I am using S3D regularly, and developed a USB user interface that allows me to adjust S3D parameters such as focal plane using a contour express dial.
I have stopped using scale factor by disabling the keyboard scroll, and switching to z translation.
I am finding that I need to adjust the focal plane a lot. Usually it is between the clipping planes, but when I do z translations it normally gets between the camera and the near clipping plane, or out past the far clipping plane.
For S3D animations I can work around it. For interactive use, people are having major eye strain.
I would like to modify the chimera code to automatically adjust the focal plane as the clipping planes change.
Can you point me to the area of code where I could make the change?
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== _______________________________________________ Chimera-dev mailing list Chimera-dev@cgl.ucsf.edu mailto:Chimera-dev@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev
thanks.
from chimera import triggers triggers.addHandler('new frame', set_focal_plane, None)
was the part I could not figure out. Would like to find out more about this api and other registered triggers, will look at the code. Besides 'new frame', are there any other imporant ones that could make useful for interfaces?
In my user control pane extension I have a focal widget that varies between -1,0 thru 100. -1 disables the widget. 0-100 is the percentage between near & far CP. Usually if I am between the two, people's eyes don't bleed, buying me some time to adjust the percentage correctly.
As for zooming, I tell people here not to use it, stick with z-translation because it gives you a better spatial feel of the data set, XYZ are in unity. Plus zooming maxes out and people can't figure out why, they think they are dollying but are not. Unless they can write a command for z translation, they are stuck.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== ________________________________ From: Tom Goddard goddard@sonic.net Sent: Tuesday, April 21, 2015 2:57 PM To: Dougherty, Matthew T Cc: chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
Hi Matt,
Here's some Python that will update the focal plane position to always lie midway between near and far clip planes.
If you zoom by moving a map or molecule closer to you (z translation) then visually the map should move from behind the screen to be in front of the screen so it looks like it is coming closer. In other words the map moves forward and the focal plane that defines the position of the screen stays fixed. That is normal Chimera behavior. The above script will defeat that. You will move the map closer to you in z, but what you will see in stereo is that the map gets bigger, but no closer. It instead feels like a magical scaling of the map, rather than getting closer to it. This isn't natural, but I understand that because of the limited 3d depth with stereo viewing it is necessary to do something to avoid uncomfortable stereo where the models are too far in front of the screen. An optimal solution is more subtle than the above script. In fact the above script won't prevent getting the front surface of the map too close for stereo viewing because it keeps the focal plane at the map midpoint in z. The front of the map can still get close to your eye and the stereo will not work. Basically you want to avoid having the front visible part of the models from getting too close to your eye where the stereo glasses don't work (because the display screen is not wide enough). We have not worked on techniques to avoid stereo interactive viewing limitations. But the normal Chimera zoom uses scale factor, not z-translation, so that is the main way this problem is avoided. But you are using z-translation instead of the normal Chimera zooming and that is why you encounter this problem.
Tom
Hi Matt,
I think the “new frame” trigger is the main useful one. There are others that tell when molecule colors or display styles change, when atoms get deleted, or models are moved. We don’t have much programming documentation but there is an example of using triggers to see when atoms change colors.
http://www.cgl.ucsf.edu/chimera/docs/ProgrammersGuide/Examples/Main_AtomTrig...
Tom
On Apr 21, 2015, at 1:24 PM, Dougherty, Matthew T matthewd@bcm.edu wrote:
thanks.
from chimera import triggers triggers.addHandler('new frame', set_focal_plane, None)
was the part I could not figure out. Would like to find out more about this api and other registered triggers, will look at the code. Besides 'new frame', are there any other imporant ones that could make useful for interfaces?
In my user control pane extension I have a focal widget that varies between -1,0 thru 100. -1 disables the widget. 0-100 is the percentage between near & far CP. Usually if I am between the two, people's eyes don't bleed, buying me some time to adjust the percentage correctly.
As for zooming, I tell people here not to use it, stick with z-translation because it gives you a better spatial feel of the data set, XYZ are in unity. Plus zooming maxes out and people can't figure out why, they think they are dollying but are not. Unless they can write a command for z translation, they are stuck.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== From: Tom Goddard <goddard@sonic.net mailto:goddard@sonic.net> Sent: Tuesday, April 21, 2015 2:57 PM To: Dougherty, Matthew T Cc: chimera-dev@cgl.ucsf.edu mailto:chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
Hi Matt,
Here’s some Python that will update the focal plane position to always lie midway between near and far clip planes.
If you zoom by moving a map or molecule closer to you (z translation) then visually the map should move from behind the screen to be in front of the screen so it looks like it is coming closer. In other words the map moves forward and the focal plane that defines the position of the screen stays fixed. That is normal Chimera behavior. The above script will defeat that. You will move the map closer to you in z, but what you will see in stereo is that the map gets bigger, but no closer. It instead feels like a magical scaling of the map, rather than getting closer to it. This isn’t natural, but I understand that because of the limited 3d depth with stereo viewing it is necessary to do something to avoid uncomfortable stereo where the models are too far in front of the screen. An optimal solution is more subtle than the above script. In fact the above script won’t prevent getting the front surface of the map too close for stereo viewing because it keeps the focal plane at the map midpoint in z. The front of the map can still get close to your eye and the stereo will not work. Basically you want to avoid having the front visible part of the models from getting too close to your eye where the stereo glasses don’t work (because the display screen is not wide enough). We have not worked on techniques to avoid stereo interactive viewing limitations. But the normal Chimera zoom uses scale factor, not z-translation, so that is the main way this problem is avoided. But you are using z-translation instead of the normal Chimera zooming and that is why you encounter this problem.
Tom
You could also try turning on the Camera's experimental autoFocus capability:
chimera.viewer.camera.autoFocus = True
It tries to maintain the focal plane at the same relative position between the hither and yon planes. I don't recall why it is off, it must have interacted badly with some other feature. But it might work for you :-)
-- Greg
On 04/23/2015 10:57 AM, Tom Goddard wrote:
Hi Matt,
I think the “new frame” trigger is the main useful one. There are others that tell when molecule colors or display styles change, when atoms get deleted, or models are moved. We don’t have much programming documentation but there is an example of using triggers to see when atoms change colors.
http://www.cgl.ucsf.edu/chimera/docs/ProgrammersGuide/Examples/Main_AtomTrig...
Tom
On Apr 21, 2015, at 1:24 PM, Dougherty, Matthew T <matthewd@bcm.edu mailto:matthewd@bcm.edu> wrote:
thanks.
from chimera import triggers triggers.addHandler('new frame', set_focal_plane, None)
was the part I could not figure out. Would like to find out more about this api and other registered triggers, will look at the code. Besides 'new frame', are there any other imporant ones that could make useful for interfaces?
In my user control pane extension I have a focal widget that varies between -1,0 thru 100. -1 disables the widget. 0-100 is the percentage between near & far CP. Usually if I am between the two, people's eyes don't bleed, buying me some time to adjust the percentage correctly.
As for zooming, I tell people here not to use it, stick with z-translation because it gives you a better spatial feel of the data set, XYZ are in unity. Plus zooming maxes out and people can't figure out why, they think they are dollying but are not. Unless they can write a command for z translation, they are stuck.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine ===========================================================================
*From:*Tom Goddard <goddard@sonic.net mailto:goddard@sonic.net> *Sent:*Tuesday, April 21, 2015 2:57 PM *To:*Dougherty, Matthew T *Cc:*chimera-dev@cgl.ucsf.edu mailto:chimera-dev@cgl.ucsf.edu *Subject:*Re: [chimera-dev] stereo3D focal plane Hi Matt,
Here’s some Python that will update the focal plane position to always lie midway between near and far clip planes.
If you zoom by moving a map or molecule closer to you (z translation) then visually the map should move from behind the screen to be in front of the screen so it looks like it is coming closer. In other words the map moves forward and the focal plane that defines the position of the screen stays fixed. That is normal Chimera behavior. The above script will defeat that. You will move the map closer to you in z, but what you will see in stereo is that the map gets bigger, but no closer. It instead feels like a magical scaling of the map, rather than getting closer to it. This isn’t natural, but I understand that because of the limited 3d depth with stereo viewing it is necessary to do something to avoid uncomfortable stereo where the models are too far in front of the screen. An optimal solution is more subtle than the above script. In fact the above script won’t prevent getting the front surface of the map too close for stereo viewing because it keeps the focal plane at the map midpoint in z. The front of the map can still get close to your eye and the stereo will not work. Basically you want to avoid having the front visible part of the models from getting too close to your eye where the stereo glasses don’t work (because the display screen is not wide enough). We have not worked on techniques to avoid stereo interactive viewing limitations. But the normal Chimera zoom uses scale factor, not z-translation, so that is the main way this problem is avoided. But you are using z-translation instead of the normal Chimera zooming and that is why you encounter this problem.
Tom
Chimera-dev mailing list Chimera-dev@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev
Tom, you mentioned that someone tried out the zspace with chimera a few years back.
Who was that?
Was that at CGL?
Should get my quadro card next week.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== ________________________________ From: Greg Couch gregc@cgl.ucsf.edu Sent: Thursday, April 23, 2015 1:07 PM To: Dougherty, Matthew T Cc: chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
You could also try turning on the Camera's experimental autoFocus capability:
chimera.viewer.camera.autoFocus = True
It tries to maintain the focal plane at the same relative position between the hither and yon planes. I don't recall why it is off, it must have interacted badly with some other feature. But it might work for you :-)
-- Greg
On 04/23/2015 10:57 AM, Tom Goddard wrote: Hi Matt,
I think the “new frame” trigger is the main useful one. There are others that tell when molecule colors or display styles change, when atoms get deleted, or models are moved. We don’t have much programming documentation but there is an example of using triggers to see when atoms change colors.
http://www.cgl.ucsf.edu/chimera/docs/ProgrammersGuide/Examples/Main_AtomTrig...
Tom
On Apr 21, 2015, at 1:24 PM, Dougherty, Matthew T <matthewd@bcm.edumailto:matthewd@bcm.edu> wrote:
thanks.
from chimera import triggers triggers.addHandler('new frame', set_focal_plane, None)
was the part I could not figure out. Would like to find out more about this api and other registered triggers, will look at the code. Besides 'new frame', are there any other imporant ones that could make useful for interfaces?
In my user control pane extension I have a focal widget that varies between -1,0 thru 100. -1 disables the widget. 0-100 is the percentage between near & far CP. Usually if I am between the two, people's eyes don't bleed, buying me some time to adjust the percentage correctly.
As for zooming, I tell people here not to use it, stick with z-translation because it gives you a better spatial feel of the data set, XYZ are in unity. Plus zooming maxes out and people can't figure out why, they think they are dollying but are not. Unless they can write a command for z translation, they are stuck.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== ________________________________ From: Tom Goddard <goddard@sonic.netmailto:goddard@sonic.net> Sent: Tuesday, April 21, 2015 2:57 PM To: Dougherty, Matthew T Cc: chimera-dev@cgl.ucsf.edumailto:chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
Hi Matt,
Here’s some Python that will update the focal plane position to always lie midway between near and far clip planes.
If you zoom by moving a map or molecule closer to you (z translation) then visually the map should move from behind the screen to be in front of the screen so it looks like it is coming closer. In other words the map moves forward and the focal plane that defines the position of the screen stays fixed. That is normal Chimera behavior. The above script will defeat that. You will move the map closer to you in z, but what you will see in stereo is that the map gets bigger, but no closer. It instead feels like a magical scaling of the map, rather than getting closer to it. This isn’t natural, but I understand that because of the limited 3d depth with stereo viewing it is necessary to do something to avoid uncomfortable stereo where the models are too far in front of the screen. An optimal solution is more subtle than the above script. In fact the above script won’t prevent getting the front surface of the map too close for stereo viewing because it keeps the focal plane at the map midpoint in z. The front of the map can still get close to your eye and the stereo will not work. Basically you want to avoid having the front visible part of the models from getting too close to your eye where the stereo glasses don’t work (because the display screen is not wide enough). We have not worked on techniques to avoid stereo interactive viewing limitations. But the normal Chimera zoom uses scale factor, not z-translation, so that is the main way this problem is avoided. But you are using z-translation instead of the normal Chimera zooming and that is why you encounter this problem.
Tom
_______________________________________________ Chimera-dev mailing list Chimera-dev@cgl.ucsf.edumailto:Chimera-dev@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev
Hi Matt,
Peter Ullman of zSpace visited our lab and showed us the device in October of 2012. We thought it was neat but too expensive (I think it was $3000 for a display, glasses and stylus), meaning few Chimera users would buy one so we did not add support for it in Chimera. I suspect the situation is the same now. I can’t find the price online — you only see secret prices for goods that are expensive niche products. I saw an April 2013 post that said it was $4000 but they expected it to be under $1000 within 18-24 months, which would be now. Even at $1000 I would not expect more than 10 total Chimera users of the device worldwide if we supported it.
Tom
On Apr 23, 2015, at 3:00 PM, Dougherty, Matthew T wrote:
Tom, you mentioned that someone tried out the zspace with chimera a few years back.
Who was that? Was that at CGL?
Should get my quadro card next week.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== From: Greg Couch Sent: Thursday, April 23, 2015 1:07 PM To: Dougherty, Matthew T Cc: chimera-dev@cgl.ucsf.edu mailto:chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
You could also try turning on the Camera's experimental autoFocus capability:
chimera.viewer.camera.autoFocus = TrueIt tries to maintain the focal plane at the same relative position between the hither and yon planes. I don't recall why it is off, it must have interacted badly with some other feature. But it might work for you :-)
-- GregOn 04/23/2015 10:57 AM, Tom Goddard wrote:
Hi Matt,
I think the “new frame” trigger is the main useful one. There are others that tell when molecule colors or display styles change, when atoms get deleted, or models are moved. We don’t have much programming documentation but there is an example of using triggers to see when atoms change colors.
http://www.cgl.ucsf.edu/chimera/docs/ProgrammersGuide/Examples/Main_AtomTrig... http://www.cgl.ucsf.edu/chimera/docs/ProgrammersGuide/Examples/Main_AtomTrigger.html
Tom
On Apr 21, 2015, at 1:24 PM, Dougherty, Matthew T wrote:
thanks.
from chimera import triggers triggers.addHandler('new frame', set_focal_plane, None)
was the part I could not figure out. Would like to find out more about this api and other registered triggers, will look at the code. Besides 'new frame', are there any other imporant ones that could make useful for interfaces?
In my user control pane extension I have a focal widget that varies between -1,0 thru 100. -1 disables the widget. 0-100 is the percentage between near & far CP. Usually if I am between the two, people's eyes don't bleed, buying me some time to adjust the percentage correctly.
As for zooming, I tell people here not to use it, stick with z-translation because it gives you a better spatial feel of the data set, XYZ are in unity. Plus zooming maxes out and people can't figure out why, they think they are dollying but are not. Unless they can write a command for z translation, they are stuck.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== From: Tom Goddard Sent: Tuesday, April 21, 2015 2:57 PM To: Dougherty, Matthew T Cc: chimera-dev@cgl.ucsf.edu mailto:chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
Hi Matt,
Here’s some Python that will update the focal plane position to always lie midway between near and far clip planes.
If you zoom by moving a map or molecule closer to you (z translation) then visually the map should move from behind the screen to be in front of the screen so it looks like it is coming closer. In other words the map moves forward and the focal plane that defines the position of the screen stays fixed. That is normal Chimera behavior. The above script will defeat that. You will move the map closer to you in z, but what you will see in stereo is that the map gets bigger, but no closer. It instead feels like a magical scaling of the map, rather than getting closer to it. This isn’t natural, but I understand that because of the limited 3d depth with stereo viewing it is necessary to do something to avoid uncomfortable stereo where the models are too far in front of the screen. An optimal solution is more subtle than the above script. In fact the above script won’t prevent getting the front surface of the map too close for stereo viewing because it keeps the focal plane at the map midpoint in z. The front of the map can still get close to your eye and the stereo will not work. Basically you want to avoid having the front visible part of the models from getting too close to your eye where the stereo glasses don’t work (because the display screen is not wide enough). We have not worked on techniques to avoid stereo interactive viewing limitations. But the normal Chimera zoom uses scale factor, not z-translation, so that is the main way this problem is avoided. But you are using z-translation instead of the normal Chimera zooming and that is why you encounter this problem.
Tom
Chimera-dev mailing list Chimera-dev@cgl.ucsf.edu mailto:Chimera-dev@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev
Chimera-dev mailing list Chimera-dev@cgl.ucsf.edu mailto:Chimera-dev@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev
its about $3.5k, about $3k more than a s3D monitor. It is an open question for me to get it working, and it only works on windows. Compared to the $4M microscopes, nothing ventured, nothing gained...
If I can getting it working, I plan to have it in the conference room for general access.
If zspace does not go with HDMI 1.4 or 2.0, I do not see it making big penetration into the market.
head tracking is nice and pen interaction has benefits; but they may be marginal for operational work.
With all the USB-HID I am doing, a 3DTV may be the affordable ticket.
Just got the PS3 gamepad working with chimera; for $15 I can field it quickly in the lab.
This looks interesting for $950.
Stereo3D resolution is 1920x2160@60hz per eye.
Should be able to make it work with chimera out of the box.
http://www.samsung.com/us/video/tvs/UN40JU6700FXZA
[http://www.samsung.com/us/system/consumer/product/un/40/ju/un40ju6700fxza/JU...]http://www.samsung.com/us/video/tvs/UN40JU6700FXZA
40” 4K UHD SmartTV 4K UHD Curved Panel | Samsung UN40JU6700FXZA :Learn more about the new Samsung UN40JU6700FXZA 40 inch 2160 4K UHD featuring 4K UHD Read more...http://www.samsung.com/us/video/tvs/UN40JU6700FXZA
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== ________________________________ From: Tom Goddard goddard@sonic.net Sent: Thursday, April 23, 2015 6:16 PM To: Dougherty, Matthew T Cc: Greg Couch; chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
Hi Matt,
Peter Ullman of zSpace visited our lab and showed us the device in October of 2012. We thought it was neat but too expensive (I think it was $3000 for a display, glasses and stylus), meaning few Chimera users would buy one so we did not add support for it in Chimera. I suspect the situation is the same now. I can’t find the price online — you only see secret prices for goods that are expensive niche products. I saw an April 2013 post that said it was $4000 but they expected it to be under $1000 within 18-24 months, which would be now. Even at $1000 I would not expect more than 10 total Chimera users of the device worldwide if we supported it.
Tom
On Apr 23, 2015, at 3:00 PM, Dougherty, Matthew T wrote:
Tom, you mentioned that someone tried out the zspace with chimera a few years back.
Who was that? Was that at CGL?
Should get my quadro card next week.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== ________________________________ From: Greg Couch Sent: Thursday, April 23, 2015 1:07 PM To: Dougherty, Matthew T Cc: chimera-dev@cgl.ucsf.edumailto:chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
You could also try turning on the Camera's experimental autoFocus capability:
chimera.viewer.camera.autoFocus = True
It tries to maintain the focal plane at the same relative position between the hither and yon planes. I don't recall why it is off, it must have interacted badly with some other feature. But it might work for you :-)
-- Greg
On 04/23/2015 10:57 AM, Tom Goddard wrote: Hi Matt,
I think the “new frame” trigger is the main useful one. There are others that tell when molecule colors or display styles change, when atoms get deleted, or models are moved. We don’t have much programming documentation but there is an example of using triggers to see when atoms change colors.
http://www.cgl.ucsf.edu/chimera/docs/ProgrammersGuide/Examples/Main_AtomTrig...
Tom
On Apr 21, 2015, at 1:24 PM, Dougherty, Matthew T wrote:
thanks.
from chimera import triggers triggers.addHandler('new frame', set_focal_plane, None)
was the part I could not figure out. Would like to find out more about this api and other registered triggers, will look at the code. Besides 'new frame', are there any other imporant ones that could make useful for interfaces?
In my user control pane extension I have a focal widget that varies between -1,0 thru 100. -1 disables the widget. 0-100 is the percentage between near & far CP. Usually if I am between the two, people's eyes don't bleed, buying me some time to adjust the percentage correctly.
As for zooming, I tell people here not to use it, stick with z-translation because it gives you a better spatial feel of the data set, XYZ are in unity. Plus zooming maxes out and people can't figure out why, they think they are dollying but are not. Unless they can write a command for z translation, they are stuck.
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== ________________________________ From: Tom Goddard Sent: Tuesday, April 21, 2015 2:57 PM To: Dougherty, Matthew T Cc: chimera-dev@cgl.ucsf.edumailto:chimera-dev@cgl.ucsf.edu Subject: Re: [chimera-dev] stereo3D focal plane
Hi Matt,
Here’s some Python that will update the focal plane position to always lie midway between near and far clip planes.
If you zoom by moving a map or molecule closer to you (z translation) then visually the map should move from behind the screen to be in front of the screen so it looks like it is coming closer. In other words the map moves forward and the focal plane that defines the position of the screen stays fixed. That is normal Chimera behavior. The above script will defeat that. You will move the map closer to you in z, but what you will see in stereo is that the map gets bigger, but no closer. It instead feels like a magical scaling of the map, rather than getting closer to it. This isn’t natural, but I understand that because of the limited 3d depth with stereo viewing it is necessary to do something to avoid uncomfortable stereo where the models are too far in front of the screen. An optimal solution is more subtle than the above script. In fact the above script won’t prevent getting the front surface of the map too close for stereo viewing because it keeps the focal plane at the map midpoint in z. The front of the map can still get close to your eye and the stereo will not work. Basically you want to avoid having the front visible part of the models from getting too close to your eye where the stereo glasses don’t work (because the display screen is not wide enough). We have not worked on techniques to avoid stereo interactive viewing limitations. But the normal Chimera zoom uses scale factor, not z-translation, so that is the main way this problem is avoided. But you are using z-translation instead of the normal Chimera zooming and that is why you encounter this problem.
Tom
_______________________________________________ Chimera-dev mailing list Chimera-dev@cgl.ucsf.edumailto:Chimera-dev@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev
_______________________________________________ Chimera-dev mailing list Chimera-dev@cgl.ucsf.edumailto:Chimera-dev@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev
participants (3)
-
Dougherty, Matthew T -
Greg Couch -
Tom Goddard