OMNeT++/OMNEST Bug Tracker - OMNeT++ | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0000642 | OMNeT++ | IDE / result analysis | public | 2013-03-25 11:44 | 2017-02-13 12:52 |
Reporter | tomi | ||||
Assigned To | rhornig | ||||
Priority | normal | Severity | minor | Reproducibility | unable to reproduce |
Status | resolved | Resolution | unable to reproduce | ||
Platform | OS | OS Version | |||
Product Version | 4.3rc1 | ||||
Target Version | Fixed in Version | 4.6 | |||
Summary | 0000642: Strange module names in csv files generated by scavetool | ||||
Description | Original message from the mailing list: I ran my scavetool like this scavetool s -V -p 'name(numNodes) OR name(MeanE2EDelay)' -g 'module,name' -O test2.csv C:\\omnetpp-4.2.1\\my_workspace\\MyResults\\simulations\ \DC121_250_NMScalarsOnly\\simulations\\results\\*.sca On sca files all very much like the one at the bottom of the page and the csv field headings are like this File, Run, ._numNodes, DataCentricicNet.dataCentricNetworkMan_MeanE2EDelay, DataCentricNet.dataCentricNetworkMan_MeanE2EDelay, DataCentricNet.dataCentricNetwtaCentricNetworkMan_MeanE2EDelay To begin with I only expected 2 name headings not 4. But also if you look carefully some bits of text seem to have been inserted inbetween parts of the module or scalar names I have hilighted this below with < > File, Run, ._numNodes, DataCentric<ic>Net.dataCentricNetworkMan_MeanE2EDelay, DataCentricNet.dataCentricNetworkMan_MeanE2EDelay, DataCentricNet.dataCentricNetw<taCentricNetw>orkMan_MeanE2EDelay This is surely a bug in the scavetool? Or can some one explain this output as valid? Example sca file: version 2 run DataC_Experiment_One_to_One_Binding-0-20130313-07:12:46-4544 attr configname DataC_Experiment_One_to_One_Binding attr datetime 20130313-07:12:46 attr experiment DataC_Experiment_One_to_One_Binding attr inifile DataCentric_2.ini attr iterationvars $numNodes=50 attr iterationvars2 "$numNodes=50, $repetition=0" attr measurement $numNodes=50 attr network DataCentricNet attr numNodes 50 attr processid 4544 attr repetition 0 attr replication #0 attr resultdir results attr runnumber 0 attr seedset 0 scalar . numNodes 50 scalar DataCentricNet.dataCentricNetworkMan DataArrivals 1 scalar DataCentricNet.dataCentricNetworkMan PercentageArrivals 100 scalar DataCentricNet.dataCentricNetworkMan DataFailures 0 scalar DataCentricNet.dataCentricNetworkMan PercentageFailures 0 scalar DataCentricNet.dataCentricNetworkMan MeanE2EDelay 0.382505927911 scalar DataCentricNet.dataCentricNetworkMan StdDevE2EDelay -1.#IND scalar DataCentricNet.dataCentricNetworkMan MaxE2EDelay 0.382505927911 scalar DataCentricNet.dataCentricNetworkMan MinE2EDelay 0.382505927911 scalar DataCentricNet.dataCentricNetworkMan numControlPackets 217 scalar DataCentricNet.dataCentricNetworkMan MeanBPS 71134.440947921 scalar DataCentricNet.dataCentricNetworkMan StdDevBPS 94006.576400524 scalar DataCentricNet.dataCentricNetworkMan MaxBPS 202960 scalar DataCentricNet.dataCentricNetworkMan MinBPS 1440 scalar DataCentricNet.dataCentricNetworkMan BPSCollectionCount 4 | ||||
Steps To Reproduce | |||||
Additional Information | I was unable to reproduce the bug with the included scalars. It is either occurs with larger datasets only, or the result files themselves are corrupted. | ||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2013-03-25 11:44 | tomi | New Issue | |||
2013-03-29 17:58 | tomi | Status | new => feedback | ||
2017-02-13 12:52 | rhornig | Status | feedback => resolved | ||
2017-02-13 12:52 | rhornig | Fixed in Version | => 4.6 | ||
2017-02-13 12:52 | rhornig | Resolution | open => unable to reproduce | ||
2017-02-13 12:52 | rhornig | Assigned To | => rhornig |
There are no notes attached to this issue. |