[BonnMotion] Fw: kind request: DisasterArea configuration

Matthias.Schwamborn at dlr.de Matthias.Schwamborn at dlr.de
Thu Oct 10 11:30:36 CEST 2019


Dear Noah,

 

please study the DA model’s documentation again, i.e.:

 

-        Section 6.4 of doc/README.pdf

-        the example scenario in doc/da_example/sample.pl

-        the DA model publication

 

The errors should give you an idea of what went wrong. For example, the first error

"Please specify a casualties clearing station for patients waiting for treatment area! aborting..."

tells you to specify a casualties clearing station (CCS) in your scenario specification. A CCS is of type ‘2’ (cf. README).

 

Best regards,

Matthias

 

 

 

Begin forwarded message:

From: "Okuonghae, Noah (2015)" <Noah.Okuonghae.2015 at live.rhul.ac.uk>
Date: 25. September 2019 at 13:51:30 CEST
To: "bonnmotion at list.serv.Uni-Osnabrueck.de" <bonnmotion at list.serv.Uni-Osnabrueck.de>
Subject: [BonnMotion] Fw: kind request: DisasterArea configuration
Reply-To: BonnMotion mobility generator mailing list <bonnmotion at list.serv.Uni-Osnabrueck.de>

 

Hello All,

 

    I am writing to say that my problem below still exists and would kindly appreciate any comment or direction as to how or who could be of help. I have been on it for more than six months now and my time is running out. 

 

Thank you ever so much for your anticipated response.

 

 

Kind regards,

 

 

Noah

 


  _____  


From: Okuonghae, Noah (2015)
Sent: Monday, September 9, 2019 6:30 AM
To: bonnmotion at list.serv.Uni-Osnabrueck.de <bonnmotion at list.serv.Uni-Osnabrueck.de>
Subject: kind request: DisasterArea configuration 

 

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"

_______________________________________________
BonnMotion mailing list
BonnMotion at list.serv.Uni-Osnabrueck.de
https://list.serv.uni-osnabrueck.de/mailman/listinfo/bonnmotion

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.serv.uni-osnabrueck.de/pipermail/bonnmotion/attachments/20191010/219cb5a6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7842 bytes
Desc: not available
URL: <http://list.serv.uni-osnabrueck.de/pipermail/bonnmotion/attachments/20191010/219cb5a6/attachment-0001.p7s>


More information about the BonnMotion mailing list