I would like to come back to an old suggestion:
I just finished coding fibonacci clusters based on daily swing highs and lows, and as with daily, weekly and monthly pivots I had the problem that I needed to define a session time for each market and instrument (which can be done within the indicator, if necessary).
The logic behind this is
Current PC time -> Convert to Universal Time -> Convert to local time of exchange by adding x hours-> Modify for summertime via algorithm, if applicable -> This is the market time which is checked against preset session start and end.
As .Net 2.0 can only perform the first conversion, the second and third conversion had to be coded. As far as I know, .Net 3.5 should do this via the library.
If you switch NT to higher version of .Net, it would definitely be very useful to define session times at an instrument level. All that would be needed for this property of an instrument would be
- time zone of exchange
- session start time in local time of exchange
- session end time in local time of exchange
Session times could be preset for the entire market (exchange or part of exchange like CBOT Agricultural) with customization possible for users.
The session as a property of a chart is not as useful, because each time you change an instrument for 3 connected charts, you would have to change the session times manually, which is not feasible.... Also testing of intraday strategies would very much rely on sessions defined for instruments.
This feature is already implemented for QuoteTracker - although it is a pretty simple piece of software compared to NT.
I think it should be fairly easy to implement, as it just needs some extension of the instrument data base.
I just finished coding fibonacci clusters based on daily swing highs and lows, and as with daily, weekly and monthly pivots I had the problem that I needed to define a session time for each market and instrument (which can be done within the indicator, if necessary).
The logic behind this is
Current PC time -> Convert to Universal Time -> Convert to local time of exchange by adding x hours-> Modify for summertime via algorithm, if applicable -> This is the market time which is checked against preset session start and end.
As .Net 2.0 can only perform the first conversion, the second and third conversion had to be coded. As far as I know, .Net 3.5 should do this via the library.
If you switch NT to higher version of .Net, it would definitely be very useful to define session times at an instrument level. All that would be needed for this property of an instrument would be
- time zone of exchange
- session start time in local time of exchange
- session end time in local time of exchange
Session times could be preset for the entire market (exchange or part of exchange like CBOT Agricultural) with customization possible for users.
The session as a property of a chart is not as useful, because each time you change an instrument for 3 connected charts, you would have to change the session times manually, which is not feasible.... Also testing of intraday strategies would very much rely on sessions defined for instruments.
This feature is already implemented for QuoteTracker - although it is a pretty simple piece of software compared to NT.
I think it should be fairly easy to implement, as it just needs some extension of the instrument data base.
Comment