Real Time Data Now / Nest Trader to Amibroker, Fcharts
- Thread starter josh1
- Start date
@Tracerbullet,
I have raised a pull request for changes in RTDMan. I know I have made invasive changes in worker.cpp but I have given lot of additional facilities. Most users are using the new version. Please consider merging.
I do not feel any necessity to go for tick data after using this version though it can be done using the same logic with some code for event handling.
I don't know whether RTD_1.40 can be converted from Autoit to AHK but atleast RTDMan should be synchronised.
I have raised a pull request for changes in RTDMan. I know I have made invasive changes in worker.cpp but I have given lot of additional facilities. Most users are using the new version. Please consider merging.
I do not feel any necessity to go for tick data after using this version though it can be done using the same logic with some code for event handling.
I don't know whether RTD_1.40 can be converted from Autoit to AHK but atleast RTDMan should be synchronised.
Actually, i see your version as the updated master version with new stuff and mine frozen with features only i need. Still need to add few things once in a while but that will also stop as Orderman/BackfillMan gets done.
Had a look but there is a *lot* of code to be reviewed before merge. Will need to check how to merge selectively in git and how to send comments to change stuff. I can just merge without looking but I prefer to review/understand code before using it, esp since trading will be profession and not hobby.
But problem is i wont use most of it so there is less motivation. Most people, probably all, will use your build - i redirect them to RTD when they ask
For example
1) 1min Bars - i instead overwrite with TICKMODE 1 backfill
2) ms ts - Dont need - and using current time instead of ltt is slightly incorrect ( but only if pc clock is wrong - can happen) . So if i want it ill prefer event based instant update.
3) B/A stuff - wont use.
4) This is picky, but i prefer certain commenting style and code organization to make it easier to read for me in future. This gets broken.
One example, no need to put name and decoration around changes, its unnecesary - can add name to copyright/file top instead and changes will be recorded by git. We used to do this during 1st year at job. After a while our mammoth javascript code had plenty of names and decoration
All of these things can be sorted out with some effort, but it doesnt serve any purpose. I want to mostly freeze it and work on other things like OrderMan and ( maybe something for logging trades in future ). Hope you dont mind, if you need anything specific in future let me know.
So, in short - you are the owner of Future of RTDMan for community through RTD. You have a lot of patience in supporting people and adding lots of features. I want to move to other stuff and keep RTDMan static as much as possible. OrderMan is a lot of code and doesnt end ...
Had a look but there is a *lot* of code to be reviewed before merge. Will need to check how to merge selectively in git and how to send comments to change stuff. I can just merge without looking but I prefer to review/understand code before using it, esp since trading will be profession and not hobby.
But problem is i wont use most of it so there is less motivation. Most people, probably all, will use your build - i redirect them to RTD when they ask
For example
1) 1min Bars - i instead overwrite with TICKMODE 1 backfill
2) ms ts - Dont need - and using current time instead of ltt is slightly incorrect ( but only if pc clock is wrong - can happen) . So if i want it ill prefer event based instant update.
3) B/A stuff - wont use.
4) This is picky, but i prefer certain commenting style and code organization to make it easier to read for me in future. This gets broken.
One example, no need to put name and decoration around changes, its unnecesary - can add name to copyright/file top instead and changes will be recorded by git. We used to do this during 1st year at job. After a while our mammoth javascript code had plenty of names and decoration
All of these things can be sorted out with some effort, but it doesnt serve any purpose. I want to mostly freeze it and work on other things like OrderMan and ( maybe something for logging trades in future ). Hope you dont mind, if you need anything specific in future let me know.
So, in short - you are the owner of Future of RTDMan for community through RTD. You have a lot of patience in supporting people and adding lots of features. I want to move to other stuff and keep RTDMan static as much as possible. OrderMan is a lot of code and doesnt end ...
That may be because you and me are not conversant with the ways of Github. If you make changes to RTDMan for Orderman then I get requests to incorporate them on urgent basis. That becomes difficult.
I don't know why Git is showing *lot* of changes. Actually there is change only in worker.cpp, worker.h and ninja.h. I have not made any changes in other files. I understand that you want to review before merging.
It is optional, you can have tick mode, 1 sec or 1 min bars.
No. Current time is not used. ms ts is appended to ltt so that all ticks are distinguished. I had done instant update to AB long back when we were using my Excel utilities. I found that it is slower than ASCII import so I abandoned that code.
It is optional
Those decorations were made to distinguish changes. I did not have Git at the time and I am not a professional programmer. Once frozen, commented code can be deleted.
I don't mind. I will have problem if you make invasive changes to RTDMan for supporting Orderman. In fact I want to have a look at Orderman since it is becoming difficult to handle SLs/Bracket orders, target in NOW. It becomes too slow sometimes and price moves away by the time we enter order.
RTDMan is doing fine job as it is. I do not see any need to to make further changes to get tick data (we are not getting all ticks from exchange).
I don't know why Git is showing *lot* of changes. Actually there is change only in worker.cpp, worker.h and ninja.h. I have not made any changes in other files. I understand that you want to review before merging.
It is optional, you can have tick mode, 1 sec or 1 min bars.
No. Current time is not used. ms ts is appended to ltt so that all ticks are distinguished. I had done instant update to AB long back when we were using my Excel utilities. I found that it is slower than ASCII import so I abandoned that code.
It is optional
4) This is picky, but i prefer certain commenting style and code organization to make it easier to read for me in future. This gets broken.
One example, no need to put name and decoration around changes, its unnecesary - can add name to copyright/file top instead and changes will be recorded by git. We used to do this during 1st year at job. After a while our mammoth javascript code had plenty of names and decoration
One example, no need to put name and decoration around changes, its unnecesary - can add name to copyright/file top instead and changes will be recorded by git. We used to do this during 1st year at job. After a while our mammoth javascript code had plenty of names and decoration
I don't mind. I will have problem if you make invasive changes to RTDMan for supporting Orderman. In fact I want to have a look at Orderman since it is becoming difficult to handle SLs/Bracket orders, target in NOW. It becomes too slow sometimes and price moves away by the time we enter order.
RTDMan is doing fine job as it is. I do not see any need to to make further changes to get tick data (we are not getting all ticks from exchange).
I think RTDMan work for orderman is done - now any tool can take latest price of all scrips from 1 csv. Even this wasn't necessary as such but is nice to have.
No plan to make invasive changes, only invasive thing i can think of is to push every tick via events (instead of OHLC delayed buffer) - but i dont need it and your ms approach will be easier workaround anyway. So maybe ill add that when orderman is done and i have nothing to do.
Orderman - after next build in a week or two (with partial targets), i will do feature freeze for a while. Need to take break from coding, will only do bug fixes. So then you can look at code and modify as needed. Will be easier to coordinate and merge that way at start.
It does not have swing support yet, ie next day wont be able to resume. I dont need it yet so pushed for later. So maybe you can start from there if you need it. We can discuss ideas on what and how to do it and pick one way. My current plan was to pick up position from Admin Positions, assuming, we can distinguish swing from intraday orders. We can save order details in ini to pick it up automatically from admin. This will probably not work for cash as they will go to holdings, will have to check.
No plan to make invasive changes, only invasive thing i can think of is to push every tick via events (instead of OHLC delayed buffer) - but i dont need it and your ms approach will be easier workaround anyway. So maybe ill add that when orderman is done and i have nothing to do.
Orderman - after next build in a week or two (with partial targets), i will do feature freeze for a while. Need to take break from coding, will only do bug fixes. So then you can look at code and modify as needed. Will be easier to coordinate and merge that way at start.
It does not have swing support yet, ie next day wont be able to resume. I dont need it yet so pushed for later. So maybe you can start from there if you need it. We can discuss ideas on what and how to do it and pick one way. My current plan was to pick up position from Admin Positions, assuming, we can distinguish swing from intraday orders. We can save order details in ini to pick it up automatically from admin. This will probably not work for cash as they will go to holdings, will have to check.
Similar threads
-
-
-
-
How to Transfer realtime data from Now/Nestrader to Amiboker ?
- Started by ghana007007
- Replies: 4
-
Free RealTime Data NOW Nest ODIN Trade Tiger Google Yahoo to AmiBroker, Fcharts MS- Started by josh1
- Replies: 2,305