I get a headache every time I try to figure out if there is anything useful in the 'concept' you're trying to write.
Where does the stream of numbers come from?
Why are you calculating them over and over again? What figure are you trying to determine?
The calculations go round and round in circles. To what end?
What's the concept? Keep generating numbers?
Then later, you introduce letters with no value assigned and you don't use them again or explain what they represented.
Where did you get that calculation to begin with - you didn't come up with yourself. You came across how to calculate resistance in circuits boards and know you want to know if that can be used in programming.
Onedream, are you going to study programming for yourself or not.
If stream$="g,y,n,K" and their ASKII's="800,96,50,12" then D_list =ASKII's thus the final sum=8.74764755 So abstractly {in a relative way},you could say 8.74764755="g,y,n,K"
What I did is replace D with R={D+(1/T)}
I create c={1/(R*3600)} I create L={A*(1/360)} I create F={1/((L*c)^.5*(2Pi))
thus (1/R1)+(1/R2)=T is ((1/R)+(1/F)=T
The code is the sum of ((1/R)+(1/A))+((1/R)+(1/A))+((1/R)+(1/A)) So abstractly {in a relative way},you could say code{8.74764755}="g,y,n,K" or "g,y,n,K" =8.74764755
now___File8.74764755.txt=__________ Code(1) ______gallery8.74764755=___________Code(2) ______Picture8.74764755.bmp=______Code(3) such that Code(3)= Sum of {Code(1)+Code(2)+Code(3)}+((Code(1)+Code(2))*-1)___{a relation }
then goto [.04533] {Code(3) is .04533} {{ another relation}}
The concept is to define the {final relation} in a relative way so memory recall is automatic and instantious.Not as an answer;,But, as a group of relations to the answer.
Thus creating relative thought from past experiences.
This was strange. While doing a search on unrelated topic(2dgrid retrieval) this here was a result. On my phone I'll make it a link when I get to my pc next. But is this what your talking about https://people.cs.pitt.edu/~chang/365/chap5.htm
I'm not sure why you are posting that. The linked article uses full sentences and makes an honest attempt to explain what is done and why. That's completely different from this thread.
Ankhd, That looks something like it,with the exception of pictures. The code created is a direct symbol created form the input,such that "by the car" is different than "the car by". This is to say,that buy compounding codes you create a specific relative code {or picture} The code{picture} path{relations} of compounding to the code is relative to the code{picture} But one has to remember,Not dealing with picture,but actual logic. The idea is that when you have a thought,and are in a relative mode {angry happy } this creates a code. This code symbol is the stat of you.Then a code what you want is created and the combining relation direct the path searched for.Thus by relation you arrive at an experienced location. The past and present information can used to learn.
Sorry guys, I'm doing the best I can. Here is one more laugh.
Seems like there is an interest.
We are talking about a pattern for dealing with large amounts of logics and relations. We need detail. We need monitoring. We need control. We need feed back. We need automatic relations. We need logic. We need the ability to create. ect.
There is no more detail than a characture at a time. ie askii D is 86 You can monitor,control and modify each at point of entry. ie see$=str$(asc(D)) or if see$=86 then see$=str$(asc(K)) of if see$="32" then print "Done"
Different detail is groups of charactures--{words} "I","was","here" or {fragments} "I was here.","for a while"
{code} is the value output of the coder, dependent on the input. in the program it is the val(RelG$)
So; { Joe was here for a while,with the car. {------code} And he left shortly,after,Judy arrived. {------code} But they left in a different car. {------code} } are three different Stream$ and three different codes. {or summed== parrell code}
while; { Joe was here for a while,with the car._ And he left shortly,after,Judy arrived._ But they left in a different car. {------code} } is one Stream$ and one code. {or seiries code}
Compairing in this case is relivent to format.{ parrell to seiries vs seiries} In parrell Compairing in this case is relivent to changing format and relation. decending codes "2,6,5,1" vs decending like codes "6 3 5 2" 2 __2 ___same 5 __5 ___same 6___6___same
note: logic of relations is a veriable. a 4 inch circle vs a 4 foot circle { invert and mulitply } fractional division ie 3/6 devided by 2/3 is 3/6 times 3/2
code 1____________________code 1 code 3____________________code 2 code 5____________________code 5 code 6____________________code 6_____________ note: 4 possable 1different and 3 sames is 3/4 alike or 1/4 differents
or "code 1 code 3 code 5 code 6" vs "code 1 code 2 code 5 code 6" {SUM vs New Code}
So we see some possible uses.
Now we need some form of relativity to give relitive codes.
A. gain is the sum active loss is the sum nonactive total is total of active and nonactive simple: loss=Totat+(gain*-1)______________gain=Total+(loss*-1) compound: loss-(Total+new)+(gain1+gain2+gain3)__ gain2=New Total+((loss+(gain1+gain3)*-1)*-1) now we control relitivity.
Ok,so we have the input control,what about output.
Look at the decoder relations. input TL$ input AL$ decoder out = DL$ I can out put whatever a group of TL$ and AL$ is changed to;
This is a continuse flyweel effect.of one or more coders back feeding.
We have detail. We have monitoring. We have control. We have feed back. We have automatic relations. We have logic. We have relativity We have the ability to create. ect.
