This is so cool! I’ve been playing around for a while now with different objects and types of lighting. Now I’m getting this error when I try to post:
{"timestamp":"2022-02-23T05:57:19.930+00:00","status":500,"error":"Internal Server Error","path":"/record"}
I'm really sorry about this... I don't think I can fix it at the moment but I'll keep work on making the app more stable. And thanks a lot for trying the app!!!
Hi! Thanks for your feedback. I had not come across this, but it looks quite similar :) (at least conceptually). I don't have a video, but there is a short gif in the repository. I am planning to make a video at some point though!
Thanks! One of the creators here. Our main idea with Lavastone is that you just write “plain” c++ code that doesn’t call any special query interface. It’s transparently making your code run by performing some interactions with the database on your behalf. In this sense the query interface looks just like the standard language features of C++.
As you point out, there are definitely trade offs with choosing Lavastone instead of a SQL database. For instance you can’t easily share concurrent read/write access to the same Lavastone data with multiple processes. However, you can copy a fixed Lavastone data store (ie the underlying LevelDB store) and distribute it to multiple server nodes. That’s how we used it anyways!
Academic papers are often reviewed independently of code.
It's the academic contribution to the wider body of knowledge reviewers will focus on as the paper, not the code, will be the thing presented at conference.
Code will likely be spaghetti. Academic research is often more about "finding new stuff" than "building robust stuff".
Doesn't always make sense IMO, but that's the way of the world.
Given several logic gates, if their most recent common ancestor in the lattice is the clone of all boolean functions, then that set is universal. This provides a convenient prescription for deciding universality for a new k-input gate.
