With or without an As Timeseries widget, the transformation to timeseries should behave the same way

[biolab]

With or without an As Timeseries widget, the transformation to timeseries should behave the same way

[irgolic]

I see. Plugging in what I did probably isn't too meaningful anyway, more than anything else, I was just confused as to why it was acting differently. It'd be nice if it sorted without As Timeseries too.

[ajdapretnar]

@irgolic Perhaps rename the issue?

[irgolic]

Related: NaNs should be ignored when Data is converted to Timeseries, and in As Timeseries, a warning should be thrown instead of an error upon NaNs.

Ideally, a warning should be shown in any Timeseries widget if there's NaN values present in the time variable. What's the easiest way of implementing this across the add-on, without duplicating Warning code in each widget?

[kernc]

Time series widgets should infer that 'As Timeseries' was supposed to be added in between,

This is the case.

and try to use the first datetime feature as the sequential attribute

This is the case.

or instance ordering if there's no datetime feature.

And this is not (yet).

IIRC, the widget is there exactly to make the choice of the temporal attribute convenient and explicit.

[ajdapretnar]

I think it is necessary if there is more than one time variable or there is an non-explicit continuous variable with 'pseudotime'.

[irgolic]

Ah, I should've opened with the use case.

My dataset contains a couple of different sources merged together, so the timestamps are a bit jumbled. It seems the time delta isn't detected properly if I plug Data directly into a timeseries widget, but it works fine if I run it through As Timeseries.

[kernc]

Yeah, in addition, the widget sorts:

orange3-timeseries/orangecontrib/timeseries/widgets/owtabletotimeseries.py

Lines 114 to 116 in 49d8648

	ordered = np.argsort(values)
	if (ordered != np.arange(len(ordered))).any():
	data = data[ordered]

[ajdapretnar]

Fixed via #95.