Was working fine for an hour and now this message....every time.

Dec 21, 2015 at 4:52 AM
Edited Dec 21, 2015 at 4:55 AM

Not sure what happened....I was just working data...and then this started happening. Help?? ONLY happens when looking for "network top items"...in graph metrics. thanks.

Details:
[IndexOutOfRangeException]: Index was outside the bounds of the array.


at Smrf.NodeXL.ExcelTemplate.TwitterSearchNetworkTopItemsCalculator2.FilterAndReformatWordMetrics(Int32& iTableIndex, GraphMetricColumn[] oWordMetricColumns, List1 oAllGroupEdgeInfos, List1 oGraphMetricColumns)

at Smrf.NodeXL.ExcelTemplate.TwitterSearchNetworkTopItemsCalculator2.TryAddColumnsForWordsAndWordPairs(Int32& iTableIndex, IGraph oGraph, List1 oAllGroupEdgeInfos, CalculateGraphMetricsContext oCalculateGraphMetricsContext, List1 oGraphMetricColumns)

at Smrf.NodeXL.ExcelTemplate.TwitterSearchNetworkTopItemsCalculator2.TryCalculateTopItemAndGroupMetrics(IGraph oGraph, CalculateGraphMetricsContext oCalculateGraphMetricsContext, List1 oGraphMetricColumns)

at Smrf.NodeXL.ExcelTemplate.TwitterSearchNetworkTopItemsCalculator2.TryCalculateGraphMetricsInternal(IGraph oGraph, CalculateGraphMetricsContext oCalculateGraphMetricsContext, List
1 oGraphMetricColumns)

at Smrf.NodeXL.ExcelTemplate.TopItemsCalculatorBase2.TryCalculateGraphMetrics(IGraph graph, CalculateGraphMetricsContext calculateGraphMetricsContext, GraphMetricColumn[]& graphMetricColumns)

at Smrf.NodeXL.ExcelTemplate.GraphMetricCalculationManager.CalculateGraphMetricsAsyncInternal(CalculateGraphMetricsAsyncArgs oCalculateGraphMetricsAsyncArgs, BackgroundWorker oBackgroundWorker, DoWorkEventArgs oDoWorkEventArgs)

at Smrf.NodeXL.ExcelTemplate.GraphMetricCalculationManager.BackgroundWorker_DoWork(Object sender, DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)

at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

OK

Coordinator
Dec 22, 2015 at 6:22 PM
Hello,

can you try with another dataset and see if the same thing happens? If it is possible, can you share the dataset that generates this error so we can try and debug? My e-mail address is arberceni@smrfoundation.org

Regards,
Arber