7 | | * Funding |
8 | | * CZI Essential Software proposal, due May 19 |
| 7 | * Nail down firm ChimeraX 1.2 release date |
| 8 | * Needs to occur prior to submission of R01 RPPR annual report on 5/17, otherwise it looks bad |
| 9 | * (4 releases described in last year's report, but only 2 so far this funding year) |
| 10 | * Funding Update: |
| 11 | * DoD ACSR cryoEM proposal due to Stanford C&G by May 7th - TEF |
| 12 | * CZI Essential Software proposal, due May 19 - Scooter |
| 13 | - avoid any changes to license at this point; tell CZI our license is "other" |
10 | | - draft research plan Google Doc started |
11 | | * NTT Data - [https://docs.google.com/document/d/17qUf02UIClFEmNinBcHIdM920V1ffDemtzmSoePYa7A/edit?usp=sharing task order] |
| 15 | - draft research plan is in Google Docs |
| 16 | - Specific Aims to be enumerated after Research Plan is more developed |
| 17 | - discuss status and writing assignments - All |
| 18 | * NTT Data - [https://docs.google.com/documen/d/17qUf02UIClFEmNinBcHIdM920V1ffDemtzmSoePYa7A/edit?usp=sharing task order] |
| 19 | - does the contract need to be modified given the Adams R24 OS that was submitted to NIH? |
| 20 | * Adelson grant status report - Scooter |
13 | | * ChimeraX release progress, late April release date. |
14 | | * SPOKE |
15 | | * Action items |
| 22 | * Status of job listing |
| 23 | * How to get the word out: Twitter, Chimera/X mailing lists, registered Chimera users list, other? |
| 24 | * Do we want a more detailed document for use in targeted advertising instead of the restrictive one required by UCSF HR? |
| 25 | * Someone needs to take the lead on widely posting this job opening - Eric/Elaine? |
| 26 | * Should Greg increase his level of effort for the RBVI? |
| 27 | - Pro: plenty of ChimeraX work to do |
| 28 | - Con: may burn intra-departmental bridges with other PIs and eliminate future support opportunities if funding pressures occurs in the future (i.e., fewer eggs in the basket) |
| 29 | * SPOKE: |
| 30 | * Status report |
| 31 | * Do we need to re-consider our level of involvement in this project? |
| 32 | - what are the scientific benefits? |
| 33 | - what level of funding do we receive? |
| 34 | - what is the level of enthusiasm of RBVI staff? |
| 35 | - does this project leverage our expertise? |
| 36 | * Review Action Items list below |
21 | | * Create tutorial for putting model on web page, TomG |
22 | | * ~~Summarize Phenix R24 ChimeraX aims to avoid conflict with R01 proposal, TomG |
23 | | * Buy Mac Mini with Apple Silicon and KVM switch, TomF |
24 | | * Figure out what additional plato directories need backup. Scooter |
25 | | * Try to setup 2-factor authentication for vpn, Scooter |
26 | | * ~~Test new vpn~~ on linux and document. Scooter |
| 43 | * Create tutorial for putting model on web page - TomG |
| 44 | * ~~Summarize Phenix R24 ChimeraX aims to avoid conflict with R01 proposal - TomG |
| 45 | * Buy ~~Mac Mini with Apple Silicon and~~ KVM switch for TomG - TomF |
| 46 | * Figure out what additional plato directories need backup - Scooter |
| 47 | * Set up 2-factor authentication for hal2 vpn - Scooter |
| 48 | * Document new vpn setup on Linux - Scooter |