Commit Graph

77 Commits (2f42c9d91b3b01189acf5064765062fa7d85e2a0)

Author SHA1 Message Date
Sofus Albert Høgsbro Rose a282d1e7ef
fix: @base event callbacks now use @events 2024-04-02 20:49:57 +02:00
Sofus Albert Høgsbro Rose 01cfc61094
feat: Fixes for cloud tasks, lint run 2024-04-02 20:39:55 +02:00
Sofus Albert Høgsbro Rose 505a12fa25
fix: Bugs related to geonodes, end-of-chain unit conversion 2024-04-02 16:40:02 +02:00
Sofus Albert Høgsbro Rose e080d16893
feat: Proper visualization pathways 2024-04-01 19:28:24 +02:00
Sofus Albert Høgsbro Rose 221d5378e4
feat: ManagedObj Semantics 2024-04-01 16:48:56 +02:00
Sofus Albert Høgsbro Rose a4e764ba21
docs: Updated TODO 2024-03-22 13:51:58 +01:00
Sofus Albert Høgsbro Rose 74e79649fb
feat: Re-Implemented Unit System Node (+ other fixes) 2024-03-22 10:12:14 +01:00
Sofus Albert Høgsbro Rose f54a9031e8
doc: Updated line about instability 2024-03-21 18:54:53 +01:00
Sofus Albert Høgsbro Rose 6f665b891d
feat: Working logging, before- and after-deps.
We have a far more sane approach to nodeps now, which
allows us to essentially have two loggers - one that is
very useful, pretty, and clear, but requires a 'rich'
dependency, and one that is simple.
In this spirit, we factored out services/ too.

We can also set the initial console log level now when
packing the .zip.

There's still work to do with the actual flow for deps
installing / uninstalling.
But it should be far more robust now.

Finally, we have a barebones working `quartodoc`-based docs site.
It's super clever; see <https://github.com/machow/quartodoc>.
As it's "just" a quarto project with some python autodiscovery,
fleshing it out with ex. math, images, diagrams, and so forth
should be exceptionally easy.

As we develop, various linter-guided fixes are being realized.
This will be a long process, best done as we spiff everything up
in preparation for general release.
2024-03-21 18:45:38 +01:00
Sofus Albert Høgsbro Rose 0fbf201d08
chore: Ran code formatter over all files 2024-03-20 12:56:50 +01:00
Sofus Albert Høgsbro Rose be4eec2242
feat: Completely revamped dependency system. 2024-03-20 12:55:40 +01:00
Sofus Albert Høgsbro Rose 59a236f33a
packaging: Initialize virtual 'rye' project. 2024-03-14 13:37:30 +01:00
Sofus Albert Høgsbro Rose e6e7b88959 docs: Added README.md and LICENSE 2024-03-14 12:33:49 +01:00
Sofus Albert Høgsbro Rose 5be3e20e99 feat: Demo-grade simulation feedback loop. 2024-03-13 19:10:54 +01:00
Sofus Albert Høgsbro Rose a19403acf7 feat: Continue to add features.
See README.md.
2024-03-12 09:01:50 +01:00
Sofus Albert Høgsbro Rose 6912344aaf refactor: Continuing large-scale alterations.
The big news is that GeoNodes Structure is now implemented,
under the new and vastly more robust chaining system.

Upload to Tidy3D cloud is tested. Next is Monitors!
2024-03-11 16:35:41 +01:00
Sofus Albert Høgsbro Rose 4c207b96e0 refactor: Massive architectural changes.
See README.md for new, semi-finalized TODO list.
2024-03-10 11:56:37 +01:00
Sofus Albert Høgsbro Rose 28e6760dfb feat: Various features (some very prototype).
It's very prototype-y. Cleanup pending.
2024-02-26 16:16:06 +01:00
Sofus Albert Høgsbro Rose 0f1465768b 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
Sofus Albert Høgsbro Rose a06d87acc7 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
Sofus Albert Høgsbro Rose bf100843cd feat: Added accel socket, fixed default units. 2024-02-19 16:03:32 +01:00
Sofus Albert Høgsbro Rose 43414f469a feat: Custom units, def. all SocketType units. 2024-02-19 15:58:39 +01:00
Sofus Albert Høgsbro Rose 2e7d50d345 feat: Registered all nodes.
Also added several features including dynamic sockets
in nodes, abstracted units for sockets, and more.
2024-02-19 14:28:35 +01:00
Sofus Albert Høgsbro Rose 00b89dcd04 docs: Revised the node/socket plan. 2024-02-16 13:17:09 +01:00
Sofus Albert Høgsbro Rose 29c098a0c1 refactor: Far more well-functioning baseline. 2024-02-14 12:33:40 +01:00
Sofus Albert Høgsbro Rose bda734b56a refactor: Big categories, structure change.
We're back down to a single working node, but this was a very practical
refactor.
In general, very good progress towards making #2 easy to fulfill in
its entirety.

Bugs remain:

- Category discovery has big code smells and needs smoothing. Blender
  complains especially about wanting `_MT_` prefix/suffix on node
category submenu types. There's also a piece of registration logic in
category.py (big no no).
- I'd love to pass a `ruff`/`mypy` run before doubling down on node
  creation, especially to help manage the complex pieces of MP logic.
- Still needs socket-bound unit-awareness feat. sympy units, before
  doubling down on a data flow convention.
- Dependency management should also be smoothed out wrt. the user
  experience, with cached directories exposed in addon preferences.
2024-02-10 17:59:16 +01:00
Sofus Albert Høgsbro Rose 63270857ae 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