ACTS (7) – How could it work – The config-containers …

[ek.skirl]

The following snippets are from the CTS’s config.txt intended as config-container draft.

…
dumps {

mydumpname1 {
​

kuid <kuid2:nnnnn:mmm>
position (x,y)
dimension (±x,±y)
stackcount n+1
stacks {
​

0 "stackname0"
1 "stackname1"
…
n "stacknameN"​

}​

}​

…
mydumpnameN {​

kuid <kuid2:nnnnn:mmm>​

position (x,y)​

dimension (±x,±y)​

…​

stacks { … }​

}​

}
…
terminals {

myterminalname1 {​

kuid <kuid2:nnnnn:mmm>
position (x,y)
cranescount m+1
cranes {
​

0 "cranename0"
1 "cranename1"
…
m "cranenameM"​

}​

}​

}
…
stacks {

mystackname1 {
​

kuid <kuid2:nnnnn:mmm>
position (x,y)
maxcount m
contcount 2
floor z
containers {
​

0 CONTID
1 CONTID​

}​

}
…
mystacknameX { … }​

}
…
cranes {

mycranename1 {
kuid <kuid2:nnnnn:mmm>
position (x,y)
dimension ((±x,±y),(±x,±y))
dumpcount d+1
dumps {
​

0 "dumpname0"
1 "dumpname1"
…
d "dumpnameD"​

}
…
mycranenameY { … }​

}

This too is uncomplete and shows for now some bits to do. One of the main tasks for config.txt-creation is to decide, which config-containers should lay in which asset’s config.txt.

Ibelief that the cranes-, dumps- and stacks-container may notnecessary written by hand to the soup. I belief that it is possibleto add them in some properties-dialog-menu and then let calculate the soupsvalues with some script-methods.

For now I don’t know enough about this all to have clear sightat the things to do. But time will show, I belief.