Code center > Suggestions

Tieports

(1/2) > >>

Endy:
Another topic got me started thinking about these again, and ways they could be better :)  I was wondering if perhaps tielenX/tieangX could also readback the current length of that particular tie. That way the bots could know which tieport was activated and various basic information about it.

Something like:

--- Code: ---cond
*.tielen1 0 !=
start
300 .tielen1 store
stop
--- End code ---

would be really useful.

Numsgil:
I don't see why not.

I've done something similar with setaim and some other sysvars.

Keep in mind at some point the tie interfaces are going to change.  It will probably become something along the lines of:

1 settie

*.tielen

instead of

*.tielen1

Anyway, you can read more about all that here.

Endy:
Sounds good, thanks.

Just how do other programming systems or real cells work to make parallel processing units? Is there anything we could use from these in Db? Right now MB's are difficult to program at best , especially when you have to juggle multiple ties.

Numsgil:
Real organisms have every gene basically 'executed' simoltaneously, but they are limited somewhat to locality.  Certain protiens in certain physical parts of the cell.  I don't think I've managed to find any other simulator that has to address this sort of issue the way DB does.

For MBs, we really need two things in my mind:

1.  A DNA structure that encourages modularity.  That is, one gene controlling a tree of genes 'underneath' it.  I discussed this sort of thing in a recent post.

2.   Better communication between individual cells.  Real developmental biology is poorly understood I think, but generally cells are tought to differentiate based on hormone levels.  The stem cell produces two distinct hormones axially apart from each other, then divides in the same direction.  The daughter cells know what to become based on the hormone level.

Endy:
I checked on the tieports and they appear to hold their values even after the affected tie is gone, ie. 300 .tielen1 store at age 0, will affect any tie that becomes tielen1.(which means some of my bots were doing a massive amount of unnecessary storing)

Thanks for the above.

Number one isn't too hard nowadays, but number two is a bit difficult with just shots or ties. We really need some sort of particle information system (hormones basically) that isn't so processor costly.

Speaking of differentiation I made a snap tie share feeder, that actually improved in terms of overall population, when it had a non-feeding phenotype. It was very odd since I originally expected the community to do worse, and instead it did better. (these are insanely good at nrg gathering, and so should be used with caution)

Navigation

[0] Message Index

[#] Next page