| | 19 | * Small molecule cif bonds |
| | 20 | - Tristan says small molecule cif files don't bond atoms by distance for atoms that have bonds to metals. |
| | 21 | - This is because adding bonds by distance does not operate on atoms that already have 1 or more bonds. |
| | 22 | - Greg will cache the metal bonds, then add bonds by distance, then add metal bonds back. |
| | 23 | |
| | 24 | * Toolshed Editor vs Contact email addresses |
| | 25 | - Trac accounts use the Toolshed Contact email. |
| | 26 | - For the Kurwenal bundle this the contact email was set to the lab PI. Probably it should instead be set to the bundle developer's email which is currently the Toolshed editor email. |
| | 27 | - Tom will tell the Kurwenal developer if they want bugs to go to them they need to change the contact email to their email address. |
| | 28 | |
| | 29 | * Qt setCheck() with numpy.bool_ |
| | 30 | - Eric says new bug report in daily build has Qt setCheck() giving an error when passing a numpy.bool_ |
| | 31 | - This may be because of our update from numpy 1 to numpy 2. |
| | 32 | - Eric will test if ChimeraX 1.12 gives the same error. 1.12 is still using numpy 1. |
| | 33 | |
| | 34 | * Python 3.14 getrefcount() |
| | 35 | - Python 3.14 returns different values from getrefcount() due to a new optimization. |
| | 36 | - Tom will check if the getrefcount() calls in the map_data bundle that free data from the volume cache needs updating and inform Zach. |
| | 37 | |
| | 38 | * Avoid making prebuilt prereqs tar file |
| | 39 | - Zach points out that the ChimeraX build makes a prereqs prebuilt tar file for use in subsequent builds, but on Mac (and possibly Windows) there is nothing used from it since we now use Astral Python builds. |
| | 40 | - Zach asks if he should remove making the prebuilt tar ball on Mac that contains python. This saves 1 minute of build time. Yes. |
| | 41 | |
| | 42 | * SSL_CERT_FILE on Mac ChimeraX builds |
| | 43 | - ChimeraX builds set SSL_CERT_FILE to a non-existent file in the build site-packages/certifi directory. |
| | 44 | - This causes the Python 3.14 ChimeraX build to fail building pynmrstar. |
| | 45 | - Tom worked around this by setting SSL_CERT_FILE to the ChimeraX.app site-packages/certifi which does exist. |
| | 46 | - Zach will test if setting SSL_CERT_FILE is necessary and will remove it if not needed. |
| | 47 | - Zach will also test if the curl --insecure option is needed for fetching prereqs from plato. The code comment says it was needed because of the bad SSL_CERT_FILE path on Mac. |
| | 48 | |
| | 49 | * Segger tar ball in ChimeraX |
| | 50 | - The ChimeraX Segger tool is installed from a tar ball on plato as a prerequisite. |
| | 51 | - Zach asks can it be removed from plato? |
| | 52 | - Tom says the Segger tar ball is made from a github SeggerX repository and we could check that tar ball into our ChimeraX github. |
| | 53 | - Zach suggests another route would be to make the SeggerX github a subrepository of the ChimeraX repository. We don't currently use subrepositories. |
| | 54 | - We discussed whether it is feasible to get rid of all the prereqs downloaded from plato during a ChimeraX build. Unclear. |
| | 55 | |