Using another different quantification method than category makes torque fail

Context

Trying to style a Torque layer with TurboCarto using [value] fails randomly. The idea in the background was to use the tips & tricks at http://andrewxhill.com/blog/2015/04/17/torque-unknown/

Steps to Reproduce

1. Load a dataset of points and create a 1-layer map with it
2. Set the aggregation of the layer to Torque
3. Make a 1 frame, 0 time, 16px agg Torque layer in Builder, so the CartoCSS looks like the code below and the map is OK

Map {
  -torque-frame-count: 1;
  -torque-animation-duration: 0;
  -torque-time-attribute: "cartodb_id";
  -torque-aggregation-function: "count(1)";
  -torque-resolution: 16;
  -torque-data-aggregation: linear;
}
#layer {
  marker-width: 7;
  marker-fill: #FFB927;
  marker-fill-opacity: 0.9;
  marker-line-width: 0.5;
  marker-line-color: #FFF;
  marker-line-opacity: 1;
  comp-op: lighter;
}

1. Now, let’s customize the CartoCSS so the Torque becomes a bubble map based on aggregation values

Map {
  -torque-frame-count: 1;
  -torque-animation-duration: 0;
  -torque-time-attribute: "cartodb_id";
  -torque-aggregation-function: "count(1)";
  -torque-resolution: 16;
  -torque-data-aggregation: linear;
}
#layer {
  marker-width: ramp([value], range(2, 8), jenks(6));
  marker-fill: #FFB927;
  marker-fill-opacity: 0.9;
  marker-line-width: 0.5;
  marker-line-color: #FFF;
  marker-line-opacity: 1;
  comp-op: lighter;
}

1. Change the basemap

Current Result

It works OK till you changes anything else in the dashboard. V.g.: change the basemap. Then, the map is rendered as expected : But you get an error in the UI:

And no error message in Chrome console.

But if you force refresh the browser, you get the same message in the UI and the error below in the console:

In the case that your Torque layer is linked to an analysis node instead of a source node, the node stays in “running” mode forever. No matter the kind of analysis.

Expected result

Plain dashboard with no errors

Browser and version

No matter the browser

.carto file

No need of .carto file, any points dataset will reproduce this

Additional info

Same behavior in on-prem 2.0

cc @rochoa

[xavijam]

Removed the quantification option and fixed torque categories when map is reloaded.

[noguerol]

Note for our future selves: we posponed the dev of the real thing, turbocarto on aggregations, in favor of this much easier solution, but we will have to tackle it sooner or later.