Code center > Specialization, Metabolism, Digestions and Env Grid

General approach to metabolism

<< < (8/9) > >>

shvarz:
Nums, your system is actually more complicated than mine.  If that's good or bad I don't know.  From what I hear from PY he wants it more starightforward.  Carefull adjusting of amounts of enzymes, having multiple routes and so on - I dropped all that.  It will be very easy to do stuff.  

You want to make fat, just say

fat
make

You want to convert glucose to fat, say

glucose
break
fat
make

The intermediates can be addressed directly from DNA to optimize things, but they don't have to.

Crap, I'm late.  Talk to you all later...

PurpleYouko:
Yep I like the simpler approach but with the option to get more complicated if you reeeeeeeaaaaaaallllly want to.

 :D  PY  :D

Botsareus:
Num , we already desided on the "make...breack" system as the final virsion , sorry it happend without you.

Numsgil:
Okay, but when you say break carb, how does the program know which route to take?  That is, imagine you have:

carbs -> A + nrg -> B + nrg -> 20nrg
and
carbs -> 10 nrg

How does the program know which one to use?  Which is default?  That's what I was getting at.

Basically I guess I'm saying:

MinNRG favor
glucose make

That is, I'm talking about a subset of what schvarz has.

shvarz:

--- Quote ---carbs -> A + nrg -> B + nrg -> 20nrg
and
carbs -> 10 nrg
--- End quote ---


So far I was able to avoid scenarios like this.  If need arises, then we can come up with algorithms, including (but not limited to) arbitrarily assigning which path is chosen.  

I am off work in 30-40 minutes.  I'll be home in an hour or so.  So expect a post with first version of metabolism in a couple of hours.

Navigation

[0] Message Index

[#] Next page

[*] Previous page