Multi-country support and weekday functions now formally launched

Dear all,

The features that were available on the beta server are now officially launched.

Please see this post for more info.

We’re now focusing on adding European data.

Thank you

Thanks!

The new 3M, 1Y, 3Y, mini-“performance charts” look great in the screener. Do you have any idea when the European data will be available? With the market crashing there’s no rush though :slight_smile:

Just to make sure the changes are working as expected, I created a simple screen with one rule:

close(90)>close_d(90)

In theory, there should be no cases, correct?

In practice, that is not the case.

What am I missing?

Thank you.

Hugh

Hugh -

Why would there be no such cases “in theory”? The inequality you wrote simply means that the closing price of a stock ninety bars ago was higher than its closing price ninety weekdays ago.

Hi Yuval,

Because somehow I thought the only changes made would involve ind and sector time series?

I really missed this one, I think.

Hugh

Hi Yuval,

Or to put it another way, in order to reproduce previoius results, the only factors I would have to change would involve ind or sector time series.

Thanks.

Hugh

Hugh,

I think you accidentally posted your last response on this thread on my thread.

Cheers,

Daniel

There is no way to precisely reproduce previous results because the industry/sector time series is now based on weekdays, not on bars, and you can’t change that. Close(120,#industry) is actually Close_D(120,#industry) in terms of functionality.

In order to get results that MAKE SENSE, you should use weekdays (_D) for functions that include industry/sector time series. So Close(0)/Close(10) > Close(0,#industry)/Close(10,#industry) should be rewritten as Close_D(0)/Close_D(10) . . . Alternatively, you could use Close_W(0)/Close_W(2) > Close_W(0,#industry)/Close_W(2,#industry).

Close_D(120) will give you the price exactly 24 weeks ago. Close(120) will give you the price a little more than 24 weeks ago since there were some holidays in the last 24 weeks.

I hope this makes sense now, and I apologize for the confusion this has caused.

Thank you, Yuval, and am copying another post that was apparently misplaced.

Because of changed results, I suspect that revisions are more widespread than at least I know what to do about.

Please see immediately below.

Thanks.

Hugh

*The following post set my expectation for what we should be seeing now and which does not seem to be the case at all:

*For users that want functions to operate on ‘bars’ (trading days)

You don’t need to do anything (almost). This is for users that want to design strategies in single country universes where all stocks in the universe stop trading on the same days. All technical functions operate on bars by default. So for example Close(10) is the close 10 trading days ago (typically 2 week span unless there was a holiday)

There’s only one case where you need to intervene: if you use sector and industry series. We chose to create industry and sector time series for the entire North America which meant that the time series had to be based on weekdays and include holidays.

This can cause problems in your strategy if, for example, you like looking for stocks that have outperformed the industry. For that filter to work the period has to be in the same units. You will need to rewrite your formulas using weekday functions. For example if you are looking for stocks that have outperformed the industry like this:

Close(0)/Close(10) > Close(0,#industry)/Close(20,#industry)

You should rewrite it using weekday functions since the industry series includes holidays:

Close_D(0)/Close_D(10) > Close_D(0,#industry)/Close_D(20,#industry)

*I am confused, for example, by what dailyavgtot(30) now represents. Is it the average daily dollar volume for the last 30 bars? Is it the average daily volume for weekdays during the last 30 calendar days with double values given for days before holidays?

Thank you!

Hugh

AvgDailyTot(30) means exactly what it used to mean. The 30 means 30 bars, not 30 weekdays. This is true for ALL functions. If a number used to mean bars, it still means bars. The only exception is if the parameter is #sector, #subsector, #industry, or #subindustry. Only in those cases does the number mean weekdays.