Changes between Version 14 and Version 15 of NIAID2023

Timestamp:

Jul 20, 2023, 1:54:36 PM (2 years ago)

Author:

Elaine Meng

Comment:

--

NIAID2023

@@ -43 +43 @@
 == 7/20/2023 ==
 
-Phil, Bhinnata; Zach, TomG, Eric, Elaine
+Phil, Bhinnata, Victor (at end); Zach, TomG, Eric, Elaine
 
-Phil: a couple of things about using ChimeraX in the Bioviz lab.  Tried to use VR meeting with Quest 2 headsets but had problems: airlink disconnections (link cables not much better, easily jiggle loose), problems joining meeting. Later investigation found timeouts in Steam and in headset. Setting Steam timeout to longer time (in Startup/Shutdown settings) made most issues go away, but sometimes Steam forgets this and it gets reset back to 30 seconds. After resetting everything got 6 headsets working as compared to only 1 in the previous session. Our SOP from now on will be to check the timeout settings of both the headset and SteamVR beforehand.
+Phil: a couple of things about using ChimeraX in the Bioviz lab.  Tried to use VR meeting with Quest 2 headsets but had problems: airlink disconnections (link cables not much better, easily jiggle loose), problems joining meeting. Later investigation found timeouts in Steam and in headset. Setting Steam timeout to longer time (in !Startup/Shutdown settings) made most issues go away, but sometimes Steam forgets this and it gets reset back to 30 seconds. After resetting everything got 6 headsets working as compared to only 1 in the previous session. Our SOP from now on will be to check the timeout settings of both the headset and SteamVR beforehand.
 
 TomG: if you get mysterious ChimeraX errors even if you find out they are due to these non-ChimeraX timeouts, please report them so we can try to improve the error messages.
@@ -56 +56 @@
 
 Phil: Another that we ran into was in reading certain sets of DICOM files, e.g. some of the individual slice files don't have .dcm file extensions and so ChimeraX won't open them. Would be nice if we didn't have to add the filename extensions. Zach: will open a ticket. 
+
+TomG: I encourage use of the standalone headset approach, is limited in some ways, but would be more reliable for  demonstrations. Phil: I did get !LookSee going and tried the minipig data at home. TomG: the passthrough video is helpful and works with standalone. Do report any problems, as it hasn't been tested that much. Phil: as you warned, can't view huge systems with too many triangles.
+
+Victor: have multiple devices that cannot use vr meeting, cannot reach (ping) the UCSF server chimerax.meeting.net. Phil: it was working this morning, or at least from other machines.  TomG: I can't ping it from my computer here either (request timed out), will have to investigate further. I don't have much experience with AWS. Maybe there are transient outages.  Phil: I could start a meeting on my mac just now, seems fine. Victor: do I have to use some specific network settings in ChimeraX?  TomG: no specific settings are required. TomG: I can see Phil's current meeting. Victor: mine says no meeting found. 
+
+Conclusion: some problem with the specific machine, as Phil and TomG can engage with this server.
+
+TomG: you don't have to use this server, it is just a convenience to (1) create a meeting name (2) provide a hub that is not firewalled.
+
+TomG: we recently updated some packages in the daily build, causing many unforeseen problems.  May be worth trying 1.6 release instead of daily build.
 
 == 7/6/2023 ==