Reality - Version 0.1

So far we have discussed some Common Physics, the Propagation of Affect, Ambient Affectance and touched on the Forming of Particles.

With the rules of engagement and the starting of two Emulators we are ready to get started on plugging in the rules of engagement and get some particles.

First I am going to be messing around with scatter and setting up an ambient density field.
With scatter I am going to simulate it to begin with and then emulate it.
With ambient density I am going to try a couple of different things.

We should be able to derive quite a lot from my experiments.

I need more to think about.

AO - The Emulator

Some Skeleton Code
[list] a > The Black Box
b > The Importance Of Design
c > The Code
d > Improvements
[/list:u]

What is our skeleton code? The skeleton code is the backbone of the emulator, it is a specification that has been witnessed in this thread a few times already.
We turn the spec into code - we are still doing it.

The black box is a complex system or device whose internal workings are hidden or not readily understood. We make derivations through a black box called an emulator with the intention of readily understanding the workings of an emulated universe and in turn our own universe.

The important of design can not be underestimated, for instance we need a random number generator that is actually random - randomness does involve clusters and sparsity as well as a continuum to place clusters and sparsity on - we use milliseconds to initiate the continuum because not one millisecond is ever the same id est milliseconds are forever - once the initiation is complete we get some sparse information and clustered information and if this is not apparent then our randomness is no good but if it is apparent then we are good to go. The emulated universe is good to go after this and what was once unknown becomes known as we make discoveries.

Good design also allows us the ability of having tools by which to help us make predictions - these tools become a part of the emulated universe and are designed around things we have discovered in the emulated universe. No different to the physical universe.

The code is separated in to two realms - the driver which is the conceptual - the physical which causes what you see on the screen using conceptual laws. They are connected in the sense that they are a part of the one program - and separate in the sense that one is derived from metaphysics and the other is to be derived from to back up this metaphysics - this becomes a circular dependency.

Improvements are made across the board when something does not prove physical reality and in turn conceptual reality.

You can call me crazy but sometimes I do have to argue the very things that I myself do.

I am basing the random distribution on three basic principles.

Calculations In The Code are made on interactions that happen after the initial state. Some thought, has to be put into the interactions that take place, to make sure they can be physically true. Interactions In The Code are self driven after the initial state - that is no further input is required by the initiator.

Analytically there will be numbers to look for and these numbers will result in more mathematics. Interpreting results will come down to looking for these numbers and using tools available to verify the numbers - the numbers are representative of the universe, if they are not then they are not good numbers. The numbers should at times have patterns associated with them or they are not representative of anything.

The more consistency found in the operation of the emulator and physical reality the more that the emulator can be applied to answering questions one might ask.

Static ambient density:

Where {a,b,c} is the center point of the cube. $$Ab = \frac{1 }{(1 + 4\pi((x-a)^2 + (y-b)^2 + (z-c)^2))}$$

More info

I wonder whether this is the only way to achieve this - whatever way is used would still be representative of this.

Ambient density has come from the distribution of fuzzballs. Where else would it come from?

The ambient doesn’t “come from” the “fuzzballs”. The ambient IS the fuzzballs.

The only way to achieve what?

If the whole universe is made of affectance then the ambient density is also fuzz - different fuzzing leads to different affects.

Fuzzballs are conveniently chosen portions of affectance - Ambient density has become differential from the balls not come from the balls.

Ambient density is just an unwanted artifact that is necessary to make contrast.

I appreciate you questioning everything phyllo. I wish there was a thumbs up smiley.

The only way to achieve what?

Oh there is a thumbs up, cool. Achieve static ambient density given the emulator is fundamentally working off discrete principles. Surely there is a way to get closer to the machine is what I am wondering - the end result would be that math.

I’m still lost as to what you are thinking. That formula is for the light scatter simulation. The formula yields a static ambient field density representative of an amassed monoparticle in the center of the cube with no other affectance present. A group of afflates are then to be introduced propagating from one side. As each afflate traverses the mass field, it’s trajectory will be altered.

I knew you would be still lost after I made the post and read it - I am thinking on the fly to see how much of this is internalized hence why I was appreciative of phyllo’s questions. I understand what the formula is for - I was wondering how I could translate it beyond regular code, closer to the machine - assembly code mixed with binary operations.

You are saying to create an amassed monoparticle, in the center of the cube - I am saying the same except I will have other affectance present. Point the afflates at it, as they approach there is going to be “force” between them and the monoparticle, and each other - I imagine some repulsive force is present and momentum to give the slingshot.

Speed versus density? Perhaps.

The repulsion is an illusion.

I am further stating to create an affectance field, such that it is static with more mass in the center.

“Unwanted artifact”?

The density will produce the specific pattern of motion that you see in the cube. Without it, the motion would be random.

Why on earth would you write assembly code unless you need it to speed up calculations?

There are no forces. Yes, “speed vs Density”, but then also angular trajectory vs gradient.

But one step at a time.

The Ab is the point-by-point ambient density as a result of an amassed affectance. So the speed of each afflate is determined by it relative position to that mass and the combination of its own density and that of the ambient at each point it traverses.

Bad choice of words on my part regarding artifact. You are correct in that a specific pattern of motion is dependent on a specific density.

Of course the density has to evolve into that specific density configuration first.

That is fair James.

Back to the field emulation…

Again, this is a time when you have some freedom to pick and choose which way you would like to setup the field. You have specific afflate characteristics defined as if they were marbles (not yet “fuzzy”), yet the field has no such hard objects within. So if asked what the field density is as some point, {d,e,f}, precisely how are you going to use the local afflates to determine (to declare) the precise density … at any point chosen?