home Forums # Technical Support Console.cpp issues Reply To: Console.cpp issues

#6176
Unknown
Member

Dear Juan,

First of all, thanks very much for your prompt reply.

However, after removing the main.cpp under the src file, the problem still remains the same.

I have no idea why it would execute the Fuzzylite code because the pathToCastaliaBin is supposed to link /home/utar/Desktop/Castalia/CastaliaBin which is to execute the omnetpp.tmp file.

The full content of omnetpp.tmp is shown as follows:

[General]
repeat = 1
SN.field_x = 100
SN.field_y = 100
SN.node[*].Application.collectTraceInfo = true
SN.node[*].Application.constantDataPayload = 2000
SN.node[*].Application.packet_rate = 1
SN.node[*].Application.rng-0 = 3
SN.node[*].ApplicationName = “ThroughputTest”
SN.node[*].Communication.MAC.backoffType = 2
SN.node[*].Communication.MAC.collectTraceInfo = true
SN.node[*].Communication.MAC.dutyCycle = 1.0
SN.node[*].Communication.MAC.randomTxOffset = 0
SN.node[*].Communication.MAC.rng-0 = 4
SN.node[*].Communication.MAC.rng-1 = 5
SN.node[*].Communication.MACProtocolName = “TunableMAC”
SN.node[*].Communication.Radio.RadioParametersFile = “../Parameters/Radio/CC2420.txt”
SN.node[*].Communication.Radio.collectTraceInfo = true
SN.node[*].Communication.Radio.rng-0 = 2
SN.node[*].Communication.Routing.collectTraceInfo = true
SN.node[*].Communication.Routing.netBufferSize = 1000
SN.node[*].Communication.Routing.percentage = 0.05
SN.node[*].Communication.Routing.powersConfig = xmldoc(“powersConfig.xml”)
SN.node[*].Communication.Routing.roundLength = 20s
SN.node[*].Communication.Routing.slotLength = 0.2
SN.node[*].Communication.RoutingProtocolName = “LeachRouting”
SN.node[*].MobilityManager.rng-0 = 0
SN.node[*].ResourceManager.collectTraceInfo = false
SN.node[*].ResourceManager.rng-0 = 6
SN.node[*].SensorManager.collectTraceInfo = false
SN.node[*].SensorManager.rng-0 = 7
SN.node[*].SensorManager.rng-1 = 8
SN.node[0].Communication.Routing.isSink = true
SN.node[0].xCoor = 0.0
SN.node[0].yCoor = 0.0
SN.node[10].xCoor = 0.0
SN.node[10].yCoor = 90.0
SN.node[1].xCoor = 50.0
SN.node[1].yCoor = 0.0
SN.node[2].xCoor = 60.0
SN.node[2].yCoor = 0.0
SN.node[3].xCoor = 70.0
SN.node[3].yCoor = 0.0
SN.node[4].xCoor = 80.0
SN.node[4].yCoor = 0.0
SN.node[5].xCoor = 90.0
SN.node[5].yCoor = 0.0
SN.node[6].xCoor = 0.0
SN.node[6].yCoor = 50.0
SN.node[7].xCoor = 0.0
SN.node[7].yCoor = 60.0
SN.node[8].xCoor = 0.0
SN.node[8].yCoor = 70.0
SN.node[9].xCoor = 0.0
SN.node[9].yCoor = 80.0
SN.numNodes = 11
SN.physicalProcess[*].rng-0 = 10
SN.wirelessChannel.bidirectionalSigma = 0
SN.wirelessChannel.collectTraceInfo = true
SN.wirelessChannel.onlyStaticNodes = true
SN.wirelessChannel.pathLossExponent = 2.0
SN.wirelessChannel.rng-0 = 1
SN.wirelessChannel.rng-2 = 9
SN.wirelessChannel.sigma = 0
cmdenv-event-banners = false
cmdenv-express-mode = true
cmdenv-interactive = false
cmdenv-module-messages = true
cmdenv-performance-display = false
ned-path = ../../src
network = SN
num-rngs = 11
output-scalar-file = Castalia-statistics.sca
output-vector-file = Castalia-statistics.vec
seed-set = ${repetition}
sim-time-limit = 2000s

As you can see, I suspect if it is the problem of ned-path = ../../src. However, provided that pathToCastaliaBin does not relate anything to fuzzylite, I think my concern here is redundant. Any idea how it relates to Fuzzylite ? In other words, anything I can do to track how it runs into fuzzylite?