Spherical joint

The Metaverse on the Cloud

The real cloud operating system is to let people only need to focus on developing algorithms regardless of how many hardwares their software will be distributed on and the network bandwidth among the hardwares.  

The real metaverse is to let people only need to focus on acting in the virtual space and the operating system automatically syncs with the reality.

Robot

The humanoid robot is for the human emotion, not the best work or combat machine. The machines dispatched on the front line should be omnidirectional, and the joints should be rotated at all angles.  The machines created by the creatures with heads and tails seem not easy to get out of heads and tails: cars, ships, aircrafts............

Metaverse @ Cloud

Cloud: the union of storages, computing and communication resources of the whole world. 

Metaverse: the union of virtual realities (synchronizing or no synchronizing with realities) of the whole world.

The Real Cloud

The real Cloud should let the application softwares do not need to care about what type and how many hardwares to execute. 

In addition to the Cloud hardware scalability, the Cloud software must be scalable too to be easy to move and dynamically allocate during runtime. 

What the goal the Real Cloud system really wants is not only a traditional client-server architecture even if the services could be moved and dynamically allocated during runtime on different servers, but also a peer to peer architecture among big and small hardwares. 

Design in an editor, save to a file, and then load the file to the other simulator. That is an old generation way. 

The new generation way is: designing and simulating, all of interactions are in the same distributing virtual reality by the access permission management without any file loading and saving. 

The general purpose Cyber Physical System needs:

1 kind of thread to read the inputs from each local sensor to update the Distributing Virtual Reality 

1 kind of thread to recognize the 3D images in the Distributing Virtual Reality to be 3D objects 

1 kind of thread to offer the local user interaction with the Distributing Virtual Reality 

1 kind of thread to read the registered senses in the Distributing Virtual Reality to update each local actuator in the real world

Spherical Shell

Basically, 6 pieces of the information eye (face) masks form a spherical shell, and it becomes a head hood when 1 piece of them is opened. 

Graph machine & Replacement machine

Graph machine 是模拟人在阅读或算式的过程是先同时看到几个重要关键的字符再系结旁边的字符组成认知图而理解一段文式然后进行思考。

Replacement machine 是模拟人在阅读或算式的过程会逐步将文式片段转换成自己已理解的片段，多次返复代换到最后其实就是结果与答案了。

Graph machine & Replacement machine

Graph machine 基本是依结合优先顺序透过 comparation gate array 同时并行位移比对将 match 到多个 Sense 中取左边第一个连接到动态配置的 virtual wire 上，之后 sense 欲变更 virtual wire 的连接状态亦是相同的方式输出 senses 到 comparation gate array 上。

Replacement machine 基本透过 comparation gate array 与 replacement table 做同时并行位移比对将 match 到的片段 replace，返复进行至没有任何 match 了即为运算完成。排在 table 前面的优先 replace 即达 graph machine 中结合力较强的 operator 优先结合的效果，过程中遇到 definition keyword 就将片段加入 table 或从其刪除。

两者对括号的处理方式都是在比对到左括号时都暂不 connect 或 replace ，后面再一并进行消括号的动作，自多个左括号处同时并行向右位移比对出右括号，左右括号间仅存在一 Sense 即消掉左右括号，接着再重复前面的动作 loop 至不再比对出任何括号，若自左括号处向右位移比对到左括号则什么都不做、等待下一 loop 后面再重复进行一次。

Graph machine 是接线生的角色，接完线后 graph 自己是线路、自己在动；Replacement machine 的 senses 则完全是被动处理，纯粹是 data。

Can these two machines be combined to be one machine?

Not login to the server, login to the local sense and the system automatically synchronizes the senses @ different machines by caching each other @ the distributing virtual memory. 

How to make the access permission security in this condition? 

The key is there should be the hardware circuit for the access permission control built in the memory and storage, and then the server will be not necessary. 

Deformable wing

吾本欲照此改滚球面展开翼然多个问题：翼面要考虑滚行接触地面的应力。

立体环场空间状态扫描采主动式射频回波测距在军用上会暴露行踪、在民用上亦易造成干扰；有一种演算法可以从多角度被动式摄得的平面影像合成立体模型可是运算量极为庞大。道路上车辆颇多，有车联网共享，多角度影像是随时大量在取得，若各车备多些运算资源就可以分担中心的运算。车多时倾向多车组成的 near cloud 而疏解与中心的通讯负担，车少时附近运算资源不足而远端通讯带宽反就充足所以倾向 far cloud，如此即需要底层分布式操作系统自动调节运算分布方为完整的 Cloud。

The submarine vision

The submarine only can hear the sounds but can not see the image? No no no, the computer can synthesis the visual graphic from the sonar data and integrate the sonar data from different submarines or another units by the sound communication to be a virtual reality basically, and render with the neural database advancedly.

The software operator

Implementing the operator by the memory has more cost than the fixed hardware operator. But in order to implement the flexible bandwidth, the link cost on the switches network is much more if using the hardware operator, so the cost spent on the software operator is acceptable.

Spheron 2019

Spheron 2019

载人不载弹、载弹不载人

有人球无人球联网协作战

载人球轻武 无人球重武装

球面小孔

滚球外视解决方案同武装解决方案：分布内嵌球面，附小盖于开口，球面离地面后开启、球面触地面前关闭。球面清污泥解决方案采喷气不采喷水，喷水另有用途。

球型限定

胶囊型载具长条状有两倍道路宽度才夠空间干溼分离但就没有球型载具內球舱无论环境如何动荡都不会倾斜的优点所以浴卧同室回干设施也是重点工作项目

舱门

斜滑盖舱门不会被水压住打不开，适用浅潜载具便于失控下沈时紧急手动开门逃生，其应力仅需应付登陆时滚行不会崩开；深水压会导致斜滑盖门滑开而失抗压球构形，若要深潜则再外包一层附掀盖式拱边抗压舱门之球壳方能应付深水压，并采多块外挂动态装卸式压舱以于意外发生时渐进抛弃浮上水面方得开启舱门。

Graph ≠ Graphic

The graph IC can replace the CPU but the graphic IC can not, and the graph IC can be the base for the graphic IC.

But is it possible about Graph = Graphic?

Perhaps it could be Graph = Graphic as Computer = Network, but my brain doesn’t reach there yet. I will think about that if I have time.

Sense Graph IC

As the processors in computers were never called electronic brain, the neural networks we usually called before should not be called neural networks. They belong to the 5th generation computers; the real neural networks belong to the 6th generation computers.

No matter the 5th or 6th generation processors, the Sense graph ICs were designed to be the base to satisfy both.

Computer = Network

" Network is a computer " will be made by the Dynamically Distributing Operating System; " Computer is a network " will start with combining the router and the computer to be one.

Hardware : Software

I/O access = memory access ➡ hardware access = software access ➡ remote hardware access = remote software access ➡ hardware service = software service ➡ hardware distribution = software distribution