Vectornaut
  • Joined on 2019-09-28
Vectornaut pushed to engine-integration at StudioInfinity/dyna3 2024-11-11 07:56:30 +00:00
abb9d35335 Correct align environment in notes
Vectornaut pushed to engine-integration at StudioInfinity/dyna3 2024-11-11 07:50:14 +00:00
a170492e3d Add engine conventions to inversive coordinates notes
b8ca1139d5 Explain what the Element::index field holds
ced001bbfe Alias the types of element and constraint keys
ed1890bffc Improve naming of constraint subjects
da008fd090 Write out representation in Element structure
Compare 6 commits »
Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 05:49:13 +00:00
Integrate engine into application prototype

Definitely at some point we are going to need to separate the src directory into parts for the Assembly/Engine [...]

Yeah, I think we'll probably want separate modules for "front of house"…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 05:39:58 +00:00
Integrate engine into application prototype

Yes, this is one of the recommended ways to organize tests in Rust!

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 05:37:26 +00:00
Integrate engine into application prototype

Are the _1 and _2 suffixes the number of arguments?

Yes—log_0 through [log_7](https://docs.rs/web-sys/latest/web_sys/conso

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 05:33:20 +00:00
Integrate engine into application prototype

I think it's too early to design a formal logging system. I've been adding and removing log messages pretty freely as I test new features and track down bugs. I just started a [wiki page](wiki/Logg…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 05:08:27 +00:00
Integrate engine into application prototype

The PR update will add a comment that explains the index field's meaning, as described in this comment, and reminds us to…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 04:53:35 +00:00
Integrate engine into application prototype

When an assembly with n elements is sent to the engine, each element gets an index from 1 to n, which tells you which column of the configuration matrix it goes in. The index is assigned and…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 04:17:13 +00:00
Integrate engine into application prototype

I assume the two usizes are some sort of references to elements. If a primitive type is being used with semantic baggage, typedef it or something like that so that you can write e.g.,

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 03:58:27 +00:00
Integrate engine into application prototype

This seems to assume that there will be two elements constrained.

Right now, there's only one kind of element (a sphere) and one kind of constraint (fixing the generalized angle between two…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 03:45:31 +00:00
Integrate engine into application prototype

Name choice? These are the two elements constrained by the constraint? We should prefer an entire word or short phrase that makes it clear. constrains would work for me, as would appliesTo.…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 03:29:35 +00:00
Integrate engine into application prototype

Same comments go for rep here as in Constraint. Maybe it's "representative"?

It's for "representation"—a vector representation of the element, acted on by a linear representation of the 3d…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 02:13:05 +00:00
Integrate engine into application prototype

If you go into engine-proto/gram-test, launch Julia, and then include("irisawa-hexlet.jl"), you should see that it prints basically the same loss history until the last few steps, when the…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 01:52:32 +00:00
Integrate engine into application prototype

OK, went through the code. Since this prototype seems like it has a chance to become the start of the actual code, I don't think it's too early to start trying to use some hygienic naming and…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 01:47:07 +00:00
Integrate engine into application prototype

Are they theoretically identical, with differences only occurring for numerical reasons?

Yes. In both cases, we're trying to solve a problem like

$$\left[\begin{matrix} a & b \ c & d…

Vectornaut commented on pull request StudioInfinity/dyna3#15 2024-11-11 00:50:16 +00:00
Integrate engine into application prototype

Please fix the warning

Done—by compiling engine::point only in test mode, where it's already in use. I'll update the PR once I do the other requested changes.

if there is a compiler…

Vectornaut created pull request StudioInfinity/dyna3#16 2024-11-07 23:01:49 +00:00
Clean up the outline view
Vectornaut created branch outline-cleanup in StudioInfinity/dyna3 2024-11-07 22:34:37 +00:00
Vectornaut pushed to outline-cleanup at StudioInfinity/dyna3 2024-11-07 22:34:37 +00:00
fc39f2a5f3 Switch font to Fira Sans
6e42681b71 Stop Assembly::realize from reacting to itself
327a1267d5 Test representation validity in realization effect
e12f4332fe Use tabular numbers for element vectors
5ce5f855d5 Make element vectors reactive
Compare 10 commits »
Vectornaut created pull request StudioInfinity/dyna3#15 2024-10-30 20:01:48 +00:00
Integrate engine into application prototype