Gonki
New Member
I am developing a client-server software platform that I believe one day could be used in an embedded turbulence suppression system. The system proposes database index of motion sensor readouts and rudder positions. Every time "t" there is a database query retrieving a multitude of possible plane positions at "t+n milliseconds". It is a query against a very large dataset comparable in size to a search engine query. Thus every time t there is a dataset of possible aircraft positions at, for example, t+1second, supplied with turbulence detector readings. The system chooses most stable flight track based on retrieved data rather than performing real-time calculations.
The database index would be computed in stationary environment with help of high performance supercomputers that are too large to be placed aboard an aircraft. So a plane takes up a databank of pre-computed flight patterns.
The reason I think my system can work is that I was able to code an object oriented programming language that runs inside of a database. I theorize it's possible to implement this language in a high-performance calculator rather than an OS-operated computer. Configurations of connected sensors and rudder readouts is loaded into the system via serialized strings (ex. JSON). My client-server architecture does not have "middle-tier" like most (or all?) 3-tier web application systems.
There are functioning prototypes of this system components. I'm looking to raise a discussion or receive criticism.
Gonki.
The database index would be computed in stationary environment with help of high performance supercomputers that are too large to be placed aboard an aircraft. So a plane takes up a databank of pre-computed flight patterns.
The reason I think my system can work is that I was able to code an object oriented programming language that runs inside of a database. I theorize it's possible to implement this language in a high-performance calculator rather than an OS-operated computer. Configurations of connected sensors and rudder readouts is loaded into the system via serialized strings (ex. JSON). My client-server architecture does not have "middle-tier" like most (or all?) 3-tier web application systems.
There are functioning prototypes of this system components. I'm looking to raise a discussion or receive criticism.
Gonki.