http://forums.visokio.com/discussions/tagged/aggregation/feed.rss Mon, 30 Oct 17 16:21:42 -0400 Tagged with aggregation - Visokio Forums en-CA http://forums.visokio.com/discussion/2709/table-view-aggregated-fields-decimal-place-displays Wed, 10 Sep 2014 06:35:45 -0400 triptiagarwal 2709@/discussions In a Table view if I aggregate it to one column and for all other columns I am calculating the mean, can I restrict the result to only two decimal places? As of now it is showing mean value up to 6 decimal places.]]> http://forums.visokio.com/discussion/2687/aggregation-calculating-weighted-meanss Fri, 15 Aug 2014 08:40:24 -0400 Alexander 2687@/discussions
I am encountering a problem that I am aggregating a rather large dataset, but I am not able to choose a weight for the fields that I want to result as the average of the aggregated data.

Do you get what I mean?

The same problem is occuring as discussed in http://forums.visokio.com/discussion/2606/aggregation-why-are-some-fields-not-editables.

Please advise.

(Using custom build: Hotfix Function not supported 2.8 b 1276)]]> http://forums.visokio.com/discussion/2606/aggregation-why-are-some-fields-not-editables Fri, 20 Jun 2014 06:40:24 -0400 Mees 2606@/discussions Screenshot attached.

Why is this? And what can we do to disable this? We need to change the Aggregate setting for a field but are not able to due to this thing

Thanks
A]]> http://forums.visokio.com/discussion/2440/barline-view-1-field-2-measures-colour-by-measure Tue, 14 Jan 2014 13:36:46 -0500 ksluder 2440@/discussions
I can't get any of the 'color' options to perform the coloring the so that the mean portion and the maximum portion have different colors.

Thanks for any suggestions. I am on day one of using Visokio.]]> http://forums.visokio.com/discussion/2368/idea-field-counts-in-mergejoin-and-aggregation-blockss Mon, 07 Oct 2013 09:32:46 -0400 cgamolo 2368@/discussions
]]> http://forums.visokio.com/discussion/2349/aggregation-category-data-and-multiple-selectionss Wed, 18 Sep 2013 10:59:29 -0400 mmor 2349@/discussions I have created a file which is the result of a one-to-many merging process. The merged data looks like:
Italy,5,Rome,10
Italy,5,Milan,8
Italy,5,Naples,7
UK,6,London,15
UK,6,York,4
UK,6,Bath,3

I want to create a Table view that sums data at the "country" level.
For example, in a Map view I want to select UK and show in my table:
6 (UK value) ,22 (the sum of 15,4 and 3).

But if I select both UK and Italy, I want my table to show:
11 (6 + 5), 47 (all cities added).

At the moment, if I create my aggregate at the "country" level, in my table I have 2 entries:
5, 25
6, 22

While if I don't aggregate at the country level, my table shows:
33 (6*3 + 5*3), 47.

What am I doing wrong?
Thanks]]> http://forums.visokio.com/discussion/2295/aggregation-function-non-empty-counts Fri, 23 Aug 2013 05:36:37 -0400 Mees 2295@/discussions Is this expected behavior? Will be useful when this is possible.

Thanks, A]]> http://forums.visokio.com/discussion/2277/aggregation-all-dates-into-one-dates Thu, 08 Aug 2013 13:02:20 -0400 amitbdesai 2277@/discussions For e.g: there are 10 times this date 8/1/2013 with different value in revenue.
But i want to aggregate all this into one with aggregation of sum of revenue and only one time date i.e 8/1/2013.
How can i do this?]]> http://forums.visokio.com/discussion/2209/aggregation-version-2.7-2.8-issuess Fri, 21 Jun 2013 12:05:05 -0400 DominicChan 2209@/discussions
It appears with 2.8 having to specify aggregation by "All Records", instead of the defaulted all records aggregation with 2.7 and prior, files created with 2.7 containing aggregate blocks in DataManager without any fields specified will not always get aggregated when ran by 2.8 server.

I have been testing the 2.8 server running 2.7 files, the results are quite random....sometimes some aggregation blocks run properly and sometimes none of the aggregation blocks function.

Please can you advise if this is a bug?

Dom]]> http://forums.visokio.com/discussion/1941/formula-summing-unique-value-countss Mon, 10 Dec 2012 09:07:48 -0500 BlaaackMambaaa1985 1941@/discussions http://forums.visokio.com/discussion/1882/aggregation-dm-block-single-average-record-unweighteds Thu, 01 Nov 2012 14:11:54 -0400 ygulla 1882@/discussions
I need to aggregate all records into one "total" row. Field A needs to aggregate as an average weighted by Field B.

When I drop in an Aggregation block, don't select any splits and the choose function for Field A to be mean and the weight to be Field B. The resulting value is unexpected... the result seems to be an unweighted mean?

NB: to make it work I had to add a constant field One (equals 1 for all records) and "split" by it.

See attached file for a trivial example.

Edit: I use 2.7 b441 x64]]> http://forums.visokio.com/discussion/1830/performance-faster-aggregation-2.8- Fri, 12 Oct 2012 12:31:53 -0400 steve 1830@/discussions
If you are using multi-field aggregations in your views or your data models, these aggregations will be performed significantly faster. ]]> http://forums.visokio.com/discussion/883/table-view-improve-table-view-grouping Tue, 26 Jul 2011 03:26:56 -0400 steve 883@/discussions 1. formula calculation precedence options should mirror aggregation (formula result per field, rather than view-wide precedence setting)
2. wysiwyg, i.e. you have to show fields for them to work in formulas precedence setting (because otherwise you can't configure the mean/sum function for hidden fields)
3. you can currently only group by category fields
4. you can't show summaries in blank collapsed grouping columns
5. memory-inefficient

Ideas: improve the options so it is identical to aggregation, except the aggregation fields are in a chosen order, and you can expand/collapse them, and sort the resulting data.

Or, consider merging aggregation with grouping, by making aggregation have the collapse/expand capabilities currently only available with grouping.]]> http://forums.visokio.com/discussion/1639/datetime-formats-aggregatesplit-datetime-fields-by-quarterss Fri, 06 Jul 2012 01:04:15 -0400 naruemon 1639@/discussions http://forums.visokio.com/discussion/1252/graphline-view-y-axis-counting-values Wed, 25 Jan 2012 07:31:50 -0500 anna 1252@/discussions
I've attached the sample with the initial data in the "raw data" tab and the result I'm looking for in the "result" tab.
I would appreciate your help! Thanks - Anna]]> http://forums.visokio.com/discussion/1088/menus-formula-and-aggregationgrouping-interaction-2.7- Wed, 09 Nov 2011 06:12:14 -0500 steve 1088@/discussions
These ideas would not affect pre-configured IOK files; they would only change default settings, and hide inactive unusual choices.

1. In the function picker, only show functions which have the same resulting data type (in the same "logical value domain") as the field they are applied to.
   
   Visible choices (depending on field data type):
   
   • Sum
   • Mean
   • Median
   • Mode
   • Minimum
   • Maximum
   • Singleton value
   • First value
   • Last value
   • (Formula result)
   
   
   Power-user hidden choices:
   
   • Record count
   • Empty count
   • Non-empty count
   • Unique value count
   • Unique values list
   • Range
   • Standard deviation
   
   
   You would still be able to get at the power-user hidden choices easily but would not see these by default.
   
   This is necessary for (3), to avoid aggregation/grouping from changing the data structure and preventing formulas from working. Formulas are defined to operate over underlying raw data, and if your aggregation changes a text field into a numeric through the use of "Empty count", the formula will most likely fail.
   
   This change would occur in grouping and aggregation, but perhaps also elsewhere for consistency and to remove choices which are confusing - e.g. a value labelled "Sales volume" but showing "Range" is incorrect.
   
   
2. In the Table view, we provide a "Formula result" option for each field alongside sum/mean/etc., just like with aggregation, instead of the "calculate formulas over grouped results" precedence setting.
   
   
3. In aggregation and grouping, we make "(Formula result)" the default for any formula field. This would include the Table view grouping, in-view aggregation, and the Aggregation operation in the Data menu and in DataManager.
   
   Note: While the bar view aggregates automatically, we couldn't allow choosing "Formula result", since Omniscope couldn't tell whether to sum/mean/whatever in any fields referenced by formulas. Instead, you would use the new "Formula" measure in 2.7, which allows you to write your own field-independent formula where you are required to use SUBSET_SUM/MEAN as appropriate.
   
   

This would mean that, if you have formulas configured in the underlying data, and you are rolling up a view to show the total sales per region, your formulas would re-execute by default.

However, due to the power and complexity of formulas, we would like to get feedback from our power users as to whether this would be a net-positive change. Would it reduce the incidence of incorrect configuration, for common models? ]]> http://forums.visokio.com/discussion/1074/totalsummary-value-all Mon, 31 Oct 2011 11:22:28 -0400 hgross 1074@/discussions
Thanks!]]> http://forums.visokio.com/discussion/891/aggregation-viewing-multiple-record-detailss Tue, 26 Jul 2011 04:07:28 -0400 steve 891@/discussions http://forums.visokio.com/discussion/946/datetime-aggregate-on-date-using-histogramss Mon, 22 Aug 2011 11:21:36 -0400 adam_varney 946@/discussions
Not sure if this is a bug or me using the histogram feature incorrectly any advice on this situation would be greatly appreciated.The end result of using the aggregate function should show me only a few months and the totals for each of them as they have not been aggregated but Summed. Regards Adam]]>