ggarciabas / flynetwork

Código doutorado
0 stars 0 forks source link

ns3::UavEnergySource::CalculateRemainingEnergy #25

Open ggarciabas opened 5 years ago

ggarciabas commented 5 years ago

UavEnergySource:UpdateEnergySourceHover [119] rem: 276.113J cons: 0.0925926J @87.9716 UavDeviceEnergyModel:HoverConsumption diff: 0.5 energy: 0.000308642 @87.9938 UavEnergySource:UpdateEnergySourceHover [121] rem: 284.618J cons: 0.0925926J @87.9938 UavDeviceEnergyModel:HoverConsumption diff: 0.5 energy: 0.000308642 @88.1179 UavEnergySource:UpdateEnergySourceHover [118] rem: 270.838J cons: 0.0925926J @88.1179 UavDeviceEnergyModel:HoverConsumption diff: 0.5 energy: 0.000308642 @88.3662 UavEnergySource:UpdateEnergySourceHover [120] rem: 281.238J cons: 0.0925926J @88.3662 UavDeviceEnergyModel:HoverConsumption diff: 0.5 energy: 0.000308642 @88.4716 UavEnergySource:UpdateEnergySourceHover [119] rem: 274.4J cons: 0.0925926J @88.4716 UavDeviceEnergyModel:HoverConsumption diff: 0.5 energy: 0.000308642 @88.4938 UavEnergySource:UpdateEnergySourceHover [121] rem: 282.878J cons: 0.0925926J @88.4938 UavDeviceEnergyModel:HoverConsumption diff: 0.5 energy: 0.000308642 @88.6179 UavEnergySource:UpdateEnergySourceHover [118] rem: 269.102J cons: 0.0925926J @88.6179 UavDeviceEnergyModel:HoverConsumption diff: 0.5 energy: 0.000308642 @88.8662 UavEnergySource:UpdateEnergySourceHover [120] rem: 279.525J cons: 0.0925926J @88.8662 assert failed. cond="m_remainingEnergyJ >= energyToDecreaseJ", file=../scratch/flynetwork/uav-energy-source.cc, line=354 terminate called without an active exception

Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: Arquivo ou diretório inexistente. (gdb) bt

0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50

1 0x00007ffff3be5535 in __GI_abort () at abort.c:79

2 0x00007ffff4001957 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6

--Type for more, q to quit, c to continue without paging--

3 0x00007ffff4007aa6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6

4 0x00007ffff4007ae1 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6

5 0x0000555555635be9 in ns3::UavEnergySource::CalculateRemainingEnergy (this=0x555555c65d90) at ../scratch/flynetwork/uav-energy-source.cc:354

--Type for more, q to quit, c to continue without paging--

6 0x0000555555631dc1 in ns3::UavEnergySource::UpdateEnergySource (this=0x555555c65d90) at ../scratch/flynetwork/uav-energy-source.cc:178

7 0x00007ffff77cad05 in ns3::WifiRadioEnergyModel::ChangeState (this=0x555555b6cca0, newState=3) at ../src/wifi/model/wifi-radio-energy-model.cc:404

8 0x00007ffff77d3c42 in ns3::MemPtrCallbackImpl<ns3::WifiRadioEnergyModel, void (ns3::DeviceEnergyModel::)(int), void, int, ns3::empty, ns3::empty, ns3::empty, ns3::empty, ns3::empty, ns3::empty, ns3::--Type for more, q to quit, c to continue without paging--

empty, ns3::empty>::operator() (this=0x555555c18330, a1=3) at ./ns3/callback.h:612

9 0x00005555555f128b in ns3::Callback<void, int, ns3::empty, ns3::empty, ns3::empty, ns3::empty, ns3::empty, ns3::empty, ns3::empty, ns3::empty>::operator() (this=0x555555a7fe38, a1=3)

at ./ns3/callback.h:1291

--Type for more, q to quit, c to continue without paging--

10 0x00007ffff77ccbec in ns3::WifiRadioEnergyModelPhyListener::NotifyRxStart (this=0x555555a7fe30, duration=...) at ../src/wifi/model/wifi-radio-energy-model.cc:595

11 0x00007ffff75da19b in ns3::WifiPhyStateHelper::NotifyRxStart (this=0x555555aa6b90, duration=...) at ../src/wifi/model/wifi-phy-state-helper.cc:243

12 0x00007ffff75dc99b in ns3::WifiPhyStateHelper::SwitchToRx (this=0x555555aa6b90, rxDuration=...) at ../src/wifi/model/wifi-phy-state-helper.cc:419

--Type for more, q to quit, c to continue without paging--

13 0x00007ffff75bf8e2 in ns3::WifiPhy::StartRx (this=0x555555990680, packet=..., txVector=..., mpdutype=ns3::NORMAL_MPDU, rxPowerW=3.5648693920587127e-13, rxDuration=..., event=...)

at ../src/wifi/model/wifi-phy.cc:3687

14 0x00007ffff75b5a9e in ns3::WifiPhy::StartReceivePreambleAndHeader (this=0x555555990680, packet=..., rxPowerW=3.5648693920587127e-13, rxDuration=...) at ../src/wifi/model/wifi-phy.cc:2483

--Type for more, q to quit, c to continue without paging--

15 0x00007ffff7604e27 in ns3::YansWifiChannel::Receive (phy=..., packet=..., rxPowerDbm=-94.479563769894682, duration=...) at ../src/wifi/model/yans-wifi-channel.cc:128

16 0x00007ffff7606a0e in ns3::MakeEvent<ns3::Ptr, ns3::Ptr, double, ns3::Time, ns3::Ptr, ns3::Ptr, double, ns3::Time>(void (*)(ns3::Ptr, ns3::Ptr, double, ns3::Time), ns3::Ptr, ns3::Ptr, double, ns3::Time)::EventFunctionImpl4::Notify() (this=0x555556adc550) at ./ns3/make-event.h:716

--Type for more, q to quit, c to continue without paging--

17 0x00007ffff4228971 in ns3::EventImpl::Invoke (this=0x555556adc550) at ../src/core/model/event-impl.cc:51

18 0x00007ffff422dff0 in ns3::DefaultSimulatorImpl::ProcessOneEvent (this=0x55555574ed10) at ../src/core/model/default-simulator-impl.cc:149

19 0x00007ffff422e3f5 in ns3::DefaultSimulatorImpl::Run (this=0x55555574ed10) at ../src/core/model/default-simulator-impl.cc:202

--Type for more, q to quit, c to continue without paging--

20 0x00007ffff4229ba9 in ns3::Simulator::Run () at ../src/core/model/simulator.cc:230

21 0x0000555555651522 in ns3::UavNetwork::Run (this=0x555555752620) at ../scratch/flynetwork/uav-network.cc:328

22 0x00005555555c9123 in main (argc=7, argv=0x7fffffffdbd8) at ../scratch/flynetwork/main.cc:103

(gdb)

ggarciabas commented 5 years ago

teste_1_custo_1_log.txt

ggarciabas commented 5 years ago

Problema ao desligar wifi e problema ao não desligar! Uav tem sua bateria esgotada quando nao desliga o wifi antes de chegar ao seu posicionamento final (central) para que possa ser removido do cenario. Mas, se colocar uma flag para que não ocorra consumo do wifi no source quando estiver em depletion ira prejudicar dados de rede quando forem considerados, pois havera comunicacao, havera troca de dados, mas incoerente com o que realmente se deseja.

O que fazer?

Como os pacotes são enviados para o servidor, poderia ser realizado um filtro ao se analizar as informacoes de rede. Mas isto somente quando o servidor tiver recebido a informacao do UAV sobre depletion. Podendo obter o IP do pacote recebido e comparar com o IP do UAV.