| | 16 | * ProofPoint email filtering |
| | 17 | - UCSF IT insists we enable URL mangling using urldefense.com for incoming emails. |
| | 18 | - Scooter thinks this is bad for the ChimeraX mailing list and Trac. |
| | 19 | - Suggests we implement ProofPoint and ask for a 1 year excemption from urldefense. |
| | 20 | - Another problem with url mangling is it breaks DKIM mail signatures. There is an option to not mangle DKIM signed emails but we don't have that option in our ProofPoint sub-console. |
| | 21 | - Might be possible to white-list sites to avoid url mangling, but Scooter did not see that option to white-list based on the "To" header, only the "From" header. |
| | 22 | |
| | 24 | |
| | 25 | * Outline for ChimeraX paper |
| | 26 | - Made outline in Google Doc, copied here |
| | 27 | |
| | 28 | {{{ |
| | 29 | Outline: |
| | 30 | 1. Introduction |
| | 31 | Example Cryo-EM workflow |
| | 32 | Get starting structures (experimental, AlphaFold, Modeller, etc.) |
| | 33 | Optionally segment the map |
| | 34 | Fit the structures into the map |
| | 35 | Build and add het groups, nucleic acid chains, etc. |
| | 36 | Refine (phenix, Starmap, ISOLDE, etc.) |
| | 37 | Validation and evaluation (visualize/VR/QScore) |
| | 38 | Iterate as necessary |
| | 39 | Other model building requirements |
| | 40 | ChimeraX model building capabilities |
| | 41 | ChimeraX extensibility (third party bundles) |
| | 42 | 2. ChimeraX role in Cryo-EM model building |
| | 43 | 3. ChimeraX role building non-Cryo-EM structures |
| | 44 | 4. ChimeraX Extensibility |
| | 45 | ChimeraX Third Party Bundles |
| | 46 | 5. Conclusion |
| | 47 | }}} |