-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
port state resampling to frontend #352
Comments
@wodeni Can you point me to where the first frame should be evaluated in the frontend, and where the initial state is decoded in the web runtime? I looked at |
penrose/react-renderer/src/Canvas.tsx Line 45 in 8385530
If you look at |
… but resample still doesn't work for the same reason; fix frontend -> backend JSON (translation conversion); add @keenancrane's hyperbolic `tangentTo` constraint
@wodeni Fixed this for now (see commit I just pushed). Thanks for the pointer! A related issue is that energy-aware resampling in the backend won't work for the same reason—the backend needs to evaluate the energy in order to pick the lowest-energy sample, which then runs into the missing function name issue. I know you had it on your roadmap to move shape definitions and sampling into the frontend. Can you let me know if you plan to get to it anytime soon (say, in the next two weeks)? Otherwise, I can do a quick fix in the meantime:
|
Resolved as Haskell is deprecated ✨ |
This first evaluation in the Haskell backend means that the Style functions in the web runtime have to have the same names and types as those in the Haskell backend. It can be removed.
repro bug: on branch
baa
(or any one that branches offweb-runtime
), run commandrunpenrose baa/baa.sub baa/baa.sty baa/baa.dsl
, which gives the following error with call stack:Suggested fix from @wodeni:
compileTrio
. The place to change isgenOptProblemAndState
. Just get rid of the line that callsevalShapes
and initialize the list of shapes as an empty list. Do remember to eval the first frame when you get to the frontendThe text was updated successfully, but these errors were encountered: