Changes between Version 48 and Version 49 of NeteSOW


Ignore:
Timestamp:
Nov 19, 2020, 4:08:53 PM (5 years ago)
Author:
Tom Goddard
Comment:

ui-1 contains 46 zero bytes. Usually this is a short text file of about that length. Maybe the buffer values were somehow set to zero before being written.

Legend:

Unmodified
Added
Removed
Modified
  • NeteSOW

    v48 v49  
    235235- Phil has tried the script, seems to work well in a few tests, needs to try with more data including edge cases and wider range of sizes
    236236- The script looks for a recommended contour level for maps from EMDB, but some maps do not have this annotation
    237 - They will need Chimera 1.15 because of changes in RCSB PDB fetch
     237- NIH 3D Print Exchange will need Chimera 1.15 because of changes in RCSB PDB fetch
    238238- Add new fetches?
    239239  - Crystallography Open Database provides CIF, but ChimeraX does not read small-molecule CIF
    240   - ZINC provides formats ChimeraX reads, we will reach out to Shoichet and/or Irwin
     240  - ZINC provides formats ChimeraX reads (SDF, MOL2), we will reach out to Shoichet and/or Irwin
    241241
    242242VR Meetings:
    243243- Meghan: we will try a VR meeting with Uganda
    244 - Victor: ...or with our own low-bandwidth machine
    245 - the Meeting GUI will be very helpful
    246 - TomG will investigate lowering the bandwidth requirement by using Messagepack
     244- Victor: ...or with our own low-bandwidth test equipment
     245- the Meeting GUI is easier than using command, remembers multiple proxy servers
     246- TomG will investigate lowering the bandwidth requirement by using !MessagePack library
    247247- TomG wants to make a science-focused video also to publicize ChimeraX meeting capabilities
    248 - security issues with meeting (whether a key is required)
    249248
    250249Segmentation, Medical Imaging, HuBMAP:
    251 - re Hubmap, the contract was to investigate it rather than to finish any specific tasks
     250- re Hubmap, the contract was to investigate it rather than to implement specific visualization
    252251- Kristen: may be too early to work with Hubmap, seems in flux
    253252- Darrell: would still like to prioritize Hubmap
    254253- Darrell: then secondarily, medical imaging; make use of ITK somehow? Would be strategic move to incorporate ITK. NIH has made investments in Hubmap and ITK, so using them may help subsequent round of funding.
    255 - TomG: maybe simple ITK can help with showing segmentations
    256 - They will invite simple ITK developer(s) to our next meeting
     254- TomG: maybe work to make ChimeraX show DICOM simple ITK segmentations
     255- They will invite simple ITK developer(s) to our next meeting, Liv and Brad.