[BonnMotion] kind request: DisasterArea configuration

[Okuonghae, Noah (2015)]

Thanks everyone,
       for all your support as I navigate through learning  to use Bonnmotion.

I am still having difficulties configuring the DisasterArea mobility despite having read through the documentation. I would be most grateful and welcome your insight on how to fix the errors below. Thank you ever so much in advance.

Kind regards,
Noah

Ques 1 (Three errors),

   I would like to configure the disaster are mobility for 10 nodes, 20 nodes, 30 nodes ...60 nodes respectively but can not get past the errors below, especially trying to configure -b cordinates, what am I not doing right? Can any kindly advice?


Error 1:

configuration:
"./bm -f emer101a DisasterArea -n 10 -x 1000 -y 1000 -p 20 -a 4 -g 140 -r 3 -e 4 -q 2.5 -d 300 -i 3000 -j 0 -b 20,190,20,174,56,150,56,174,38,174,56,182,1,2,1 -b 75,200,75,170,225,200,225,170,75,182,140,170,0,2,1 -b 160,15,160,55,200,15,200,55,270,0,130,0,160,25,200,25,4,3,2 -b 40,10,65,10,65,35,40,35,50,10,50,11,3,3,0 -o 230,200,230,140,270,200,270,140"

Results:

Picked up _JAVA_OPTIONS: -Xmx8G
BonnMotion 3.0.1

OS: Linux 4.4.0-146-generic
Java: Oracle Corporation 11.0.3


Starting DisasterArea ...
avgMobileNodesPerGroup will not be considered in this model, because the group sizes depend on the areas
In this model you can't specify maxspeed using area dependend speed
#Obstacle[Type:0] = 1
FINISHED: compute visibility graphs type: 0
#Obstacle[Type:1] = 1
FINISHED: compute visibility graphs type: 1
#Obstacle[Type:2] = 1
FINISHED: compute visibility graphs type: 2
#Obstacle[Type:3] = 1
FINISHED: compute visibility graphs type: 3
#Obstacle[Type:4] = 1
FINISHED: compute visibility graphs type: 4
Area: 0(Type: 1) -->1 * 1 + 1 * (2-1) = 2
"Please specify a casualties clearing station for patients waiting for treatment area! aborting..."

Error 2:

./bm -f emer101a DisasterArea -n 10 -x 1000 -y 1000 -p 20 -a 4 -g 140 -r 3 -e 4 -q 2.5 -d 300 -i 3000 -j 0 -b 20,190,20,174,56,150,56,174,38,174,56,182,1,2,3 -b 75,200,75,170,225,200,225,170,75,182,140,170,0,3,1 -b 160,15,160,55,200,15,200,55,270,0,130,0,160,25,200,25,4,3,2 -b 40,10,65,10,65,35,40,35,50,10,50,11,3,2,0 -o 230,200,230,140,270,200,270,140
Picked up _JAVA_OPTIONS: -Xmx8G
BonnMotion 3.0.1

OS: Linux 4.4.0-146-generic
Java: Oracle Corporation 11.0.3


Starting DisasterArea ...
avgMobileNodesPerGroup will not be considered in this model, because the group sizes depend on the areas
"In this model you can't specify maxspeed using area dependend speed
"There can't be more transport groups than total groups, here: transport groups 3 total 2"

Error 3:

  ./bm -f emer101a DisasterArea -n 10 -x 1000 -y 1000 -p 20 -a 4 -g 140 -r 3 -e 4 -q 2.5 -d 300 -i 3000 -j 0 -b 20,190,20,174,56,150,56,174,38,174,56,182,1,2,1 -b 160,15,160,55,200,15,200,55,270,0,130,0,160,25,4,2 -b 40,10,65,10,65,35,40,35,50,10,50,11,3,4,0 -b 133,25,180,25,180,75,133,75,133,50,180,50,1,3,3 -o 230,200,230,140,270,200,270,140
Picked up _JAVA_OPTIONS: -Xmx8G
BonnMotion 3.0.1

OS: Linux 4.4.0-146-generic
Java: Oracle Corporation 11.0.3


Starting DisasterArea ...
avgMobileNodesPerGroup will not be considered in this model, because the group sizes depend on the areas
In this model you can't specify maxspeed using area dependend speed
"Areas' y-coordinates should be in scenario range and not too near to border
Area-Type: 25.0 maxdist 3.0 Params 0.0"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.serv.uni-osnabrueck.de/pipermail/bonnmotion/attachments/20190909/9c391d5b/attachment-0001.html>