Code center > Specialization, Metabolism, Digestions and Env Grid
Darwinbots enzyme system
Zelos:
shvarz, as ive understand it the mebo (MEtaBOlism) system will be in 3,0. and ur system, I think ive came up whit a simulare things and said it to numsgil, not exacly the same but simular. when its about gravity, it doesnt effect the spread of something aslongest its not to heavy, and are liquid or gas. I like the idea of toxic, like a bot who uses the sulfur photosythensis, CO2 + H2S + Light, should be toxiced by oxygen. if om not misstagen the oxygen steals some electron or something like that which sabotage the entire reaction. while some using water photo uses the oxygen and arent toxiced by it :D . what I think is that we make the system you have came up whit numsgil, enzymes is a hexacode, some things are toxic to some reactions, you can have alimited amount of enzymes
Numsgil:
The Mebo system is the last bit thing I want to include in 3.0. After that is done, a few minor fixes, what PY's been working on in graphics, and we'll be done I think.
Don't worry about delaying the programming. I'm taking a break from the DB source code for a few days to learn OpenGL.
Having the individual substances have their own bit patterns is a cool idea.
I was going to do something similar to it when reactions are read it. If each reaction is an enzyme, you'll need a way of making and remaking the same unique activation site bit pattern every time the program is run.
That involves some kind of hash function.
The only drawback to what you've listed is that it increases the length of activation sites. Which means it more closely models real life, along with the real length of enzymes (very long indeed). Which means it may be harder to evolve new enzymes.
Zelos:
:( numsgil, I sugjested something simular and you didnt liked it :(
I cant wait for 3,0 :D will be so awesome
Numsgil:
Really? I must have misunderstood.
Zelos:
yeah, but there I said for the atoms, like
S=001
H=101
then H2S would have 101,101,001 (,=to show its different atoms)
buts its basacly the same, instant of have to come up whit a bit code for each new reaction (I assume it will come more) you simply add them and then the program calculate what the bit code for it is, right now you would need 6 code, H,S,Fe,O,C,N is all the atomtypes ive seen, but for like carbs, fat and so it would need a customed code, but I think you get the idea. but if we use carbs to be like glucose it would have a long code. if we dont make it possible to tell the number after the type. glucose have the formula C6H12O6, if we say H=100, C=110 and O=101, the first 1 would represent its a element. and numbers would have the usual bit number, + a 0 in the front to tell its a number, like 1=01 2=010, you get the idea, so the bit number for glucose would be (once again ,=just to show its different things), 110,0110,100,01100,101,0110 its a long code but shorter than keep making c after c codes, this is just an idea, how you numsgil fix it whit programing I have no idea. think it could be hard making it seperate numbers from elements, unless it constanty check the list. that was my idea from the begining or something like that
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version