Code center > Specialization, Metabolism, Digestions and Env Grid
Genetic Metabolism
PurpleYouko:
--- Quote ---we are going to have ~40-50 enzymes right now
--- End quote ---
I have a question here.
Are you
* Specifying particular enzymes that do one job?
* Modeling multipe enzymes for each job, all with different efficiency rates?
* Modelling a bit pattern for each enzyme and allowing the program to randomly try to match it through mutation?
* Modelling mechanisms that Num and me (well Num mostly) have to figure out the best way to make a bit pattern system work with? :D PY :D
PurpleYouko:
--- Quote ---Also, I don't think the stomach should know which of the enzymes to use. If you have 10 fat digesting enzymes, each one can cleave n fat per cycle. The bot doesn't know which one does it better than others. Which one is used is random for each fat bit.
--- End quote ---
OK this is an interesting concept that I hadn't really thought of.
So are you saying that if the total bit pattern contains 50 sub patterns that are recognizable as enzymes by the program, that the bot will make all available enzymes in equal quantities?
If so then there will be a strong evolutionary drive to lose the ones that don't work too well in addition to getting better ones. It is obviously going to be more efficient to only make one good enzyme for a particular purpose (digesting fat) than to make one good one and a dozen cheesey ones that bairly work for the same purpose.
We should see robots with the bare minimum enzyme patterns with this method.
:D PY :D
Numsgil:
--- Quote ---I say we let 'em have as many as they want and if they can't afford them, tough! Evolutionary dead end!
--- End quote ---
That would be my thought. Exactly how we charge for enzymes I'm still not sure on, but if you want to be an omnivore, and digest absolutely everything possible, it should be an option. Remember that omnivores do actually exist in real life. There are situations that call for it.
Numsgil:
--- Quote ---...
We should see robots with the bare minimum enzyme patterns with this method.
--- End quote ---
That's the general idea I was after. Reward minimalist bots. The amount of reward is open to debate, but I would like to see a mechanism to prune inefficient patterns from the genome. A spring cleaning incentive.
This of course only applies to activation sites on the same enzyme. I may very well want to produce more of enzyme A than enyzme B. But activation sites on an enzyme that cleve the same materials should be equally likely to work as each other.
shvarz:
OK, I know this is open for discussion, so this is just my side of story:
1. Specifying particular enzymes that do one job?
Right now I do one enzyme - one job. The difference in efficiency will come from "3-bits on each end" idea of Num's, from enzyme complexes and from total amount of enzyme.
2. Modeling multipe enzymes for each job, all with different efficiency rates?
No. See above.
3. Modelling a bit pattern for each enzyme and allowing the program to randomly try to match it through mutation?
No. Enzyme function is hard-coded. Again, see above.
4. Modelling mechanisms that Num and me (well Num mostly) have to figure out the best way to make a bit pattern system work with?
Not sure what you mean. As far as available enzymes, I just assume we'll have some kind of modification of Num's bit system.
P.S: Jeez, I must do some work today. But all these discussions make me wanna drop everything and present the metabolism I have to all of you. But I don't want to rush it, cause if I explain it poorly, you all will hate it and all my work will go to waste :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version