so-rose
/
oscillode
1
0
Fork 0
Code Issues 50 Pull Requests Packages Projects Releases Wiki Activity
oscillode/blender_maxwell/requirements.txt

6 lines
71 B
Plaintext
Raw Normal View History

feat: Somewhat working addon. Solved a lot of problems related to bundled Python environment flushing for reloading. However, we have a really solid framework for computing node trees, and we can now both construct Tidy3D objects and noodle them into the "Debug Printer". Next step is rote implementation of relevant nodes, then live-visualization of the simulation setup. See #2 for progress tracking.
2024-02-06 21:44:43 +01:00
tidy3d==2.5.2
pydantic==2.6.0
refactor: Far more well-functioning baseline.
2024-02-14 12:33:40 +01:00
sympy==1.12
feat: More sockets, nodes, fixes. We're starting to have a very advanced socket-based language for defining nodes. It's very practical already. The priorities are 1. All the nodes! 2. Sockets, including default values, as needed. 3. Library constants, mediums. 4. Output socket previews w/geonodes, geonodes structures. 5. Utilities including arrays (and selected array multi-input) The code is still very spaghetti. This is very much still the "first, make it run" part of the system design.
2024-02-19 18:36:16 +01:00
scipy==1.12.0
feat: We did it, GeoNodes node w/live update! We also implemented the TriMesh node, and established a strong convention for updating nodes from sockets via. socket superclass method. `trigger_updates`. It should be triggered as the `update=` callback on **ALL PROPERTIES IN ALL SOCKETS**. This method in turn calls the nodal `update()` function, which in turn causes the node to chain-update all nodes linked to any output socket. By default, `update()` is `pass`, so performance shouldn't be a concern, but we should think about this deeper at some point. Because update-chaining is done, we're ready for preview toggles on node outputs. A lot of exciting things to do now!
2024-02-20 13:16:23 +01:00
trimesh==4.1.4