Any update on 5.4... does the June time frame still look probable...? do you know if it will include the optimizer ?
thx
Size:
Color:
Yes, 5.4 will come with the optimizer.
Size:
Color:
Excellent. thx
Size:
Color:
I just got "Authentication Failed" as log in to WL5.1, was fine yesterday. Is it because 5.4 going to release next Monday 6/1 ?!!
And just curious, could you please highlight what's new, upgrade, fix in 5.4 ? Thanks, Eugene.
Size:
Color:
Nope. No connection to WLP 5.4 release somewhere in June. BTW it happened before and was pretty much a problem within the customer's computer configuration:
Fidelity login fails in WLP 5.1
Size:
Color:
I started getting this Thursday night (5/28). It crashed after authenticating. I had to upgrade to 5.3 to get around it, I'm not sure if that was the problem but I didn't have time to figure it out. I should note the PC crashed and needed a reset button press prior to the problem, so it may have been a corrupted file of some sort.
Size:
Color:
Thanks, Eugene. My "Authentication failed" has nothing to do with WLP 5.4 going to release. And 5.4 highlight is Optimizer, will release on the third week of June, from Fidel rep.
Sorry to hear that, DaveAronow. Happened to me before. thus, I back up 1.0.0 folder once a week. If you have to download 1 or 3 minutes data for >1000 symbols, uhmmmm .
Size:
Color:
any word on 5.4 release ?
Size:
Color:
Please see Robert's reply 6/25/2009 2:08 AM in
this thread.
Size:
Color:
great. thx
Size:
Color:
To clarify that, WLP 5.4 should be out the door early next week. For Developer we're officially skipping 5.3 (5.2 was a special educational release for "Pro"), and we're shooting to get WLD 5.4 (Rankings, Optimizer, and Paper Trading) out before the end of July.
Size:
Color:
I recall reading that WL 5.4 could come with a WatchListName function. Has that been incorporated and how could I access it? Thanks.
Size:
Color:
It's mentioned on the Wiki, but I don't recall seeing anything official about putting such a function in 5.4 or even 5.5 or 5.6. Eugene, can you correct that on the "Missing features" wiki article, please?
Nonetheless, you can use the Community.Component extension's
GetDataSetName method.
Size:
Color:
Thanks. I'm new at C#, so I'm probably missing something elementary. When I compile, it does not find the namespace 'Community'.
Size:
Color:
WLTrader23QUOTE:
When I compile, it does not find the namespace 'Community'.
Please download the Community.Components library from the
Extensions section.
Size:
Color:
Thanks for the pointer, Robert. It's corrected. I was confused about Fidelity adding some watchlist support, which then turned to be a different thing under the familiar name.
Size:
Color:
Perfect. Thanks.
Another Question:
I do some pre-processing of the watchlist before running the strategy. I'm having trouble accessing stock option data.
I get an error whenever it goes to SetPrimarySeries(WatchListSymbol(SymCount)) for an Option Symbol like -COTHA. How do I access the Option Price data in such a WatchList Loop?
Size:
Color:
Where is your historical option data (i.e., chart data) coming from? (You can't SetPrimarySeries if there isn't a series to set it to.)
Size:
Color:
The option is part of the DataSet. It will chart the option, so I thought it would also pick up the bar data for manipulation. A snippet of code is below. It picks up an error for any options.
CODE:
Please log in to see this code.
Size:
Color:
If you have historical bar data for options, then there's no difference in accessing it as for any other symbol. After all, Wealth-Lab doesn't know it's "option data" anyway.
For Version 5, see DataSetSymbols, SetContext, GetExternalSymbol in the QuickRef.
Size:
Color:
Thanks Cone. It's using Fidelity Investment as the provider. I'll play with it some more. Have a great weekend!
Size:
Color:
Does Fidelity provide historical stock option data?
Size:
Color:
Yes. In WL5.4 I can chart the option data, but when I try to pull it in to process it, I get an error (I understand your point that it should not know the difference). In WL4.5, I could pull it in and process it. Fidelity uses a "-" predecessor for options. Could WL 5.4 being get hung up on that?
Size:
Color:
It works in 5.4 for me. Example -
CODE:
Please log in to see this code.
Size:
Color:
Thanks. I find that works for the individual symbol, but when I put it into a DataSetLoop, it gives me a syncronization error "Cannot Synchronize, no overlapping Dates". I'm using .DJI for the first symbol and the option only has 18 bars. If I turn off GetExternalSymbol syncronization, I still get the same error. I put the entire code below. It just writes the price and volume data on a file for offline processing.
CODE:
Please log in to see this code.
Size:
Color:
Please wrap code in the CODE tags when you post it, thanks.
Size:
Color:
Sorry. Here it is again, hopefully more readable. It stops on GetExternalSymbol with the error "Cannot Xynchronize, no overlapping Dates."
CODE:
Please log in to see this code.
Size:
Color:
Neither .DJI-COTHB nor .DJI-COTHA seem like a valid symbol to me: no data available.
Size:
Color:
At Fidelity the "." prefix is for indices and "-" is for options. The "." works and delivers the expected symbol data. Unfortunately "-" does not in the dataset loop. As I mentioned, it works if done for a single symbol. I may have to do that.
Size:
Color:
First thing, the error "Cannot Xynchronize, no overlapping Dates" refers to synchronization with the primary (clicked) symbol. If you access a secondary symbol that doesn't have any dates in common with the primary symbol, then it's unlikey that there's any point to accessing that symbol in the current context.
In reality, it appears to me that the purpose of your code is to export the raw data for symbols in the WatchList. You should not be synchronizing secondary symbols for that purpose. In the v4 code that you translated, you're missing an EnableSynch(false) statement. I don't know how WSTL handles that.
Second, if you've got a problem with WSTL, then you should report that to the WSTL forum. We can't support that component problems in translated code. Consequently, my advise is to re-write the code without dependence on WSTL following the example in the QuickRef for DataSetSymbols. Keeping in mind the first thing, it will work.
Size:
Color:
Size:
Color:
Thanks guys. For some reason FileCreate/FileWrite didn't work, but as soon s I went to StreamWriter, it worked fine.
Size:
Color:
Sorry, still learning. It's 8pm and when I update a dataset from wealthlab, I'm still getting 7/2 data versus 7/6. In WL4.5, I get the 7/6 data which is updated right after close. What do I have set wrong?
Size:
Color:
Hmmm, considering that the data come from the same place and are requested the same way, it's hard to know what could be wrong other than something with the system clock (make sure the clock is accurate for the Time zone and DST setting), or potentially you just happened to hit a server that isn't working. If the problem persists another day, please call Fidelity about Fidelity data problems.
Size:
Color:
Any ETA on WLD 5.4? I am keenly awaiting it.
Size:
Color:
In a few days. We're putting on the finishing touches.
Size:
Color:
The free version for acquaintance will be?
Size:
Color:
Like always, there is a free 30-day trial of Wealth-Lab Developer.
Size:
Color:
Has installed. At start there is an error:
????????:
Stopped working
????????? ????????:
??? ??????? ????????: CLR20r3
????????? ???????? 01: wealthlabdev.exe
????????? ???????? 02: 5.1.5.10
????????? ???????? 03: 48a5e379
????????? ???????? 04: System
????????? ???????? 05: 2.0.0.0
????????? ???????? 06: 49cc5ec9
????????? ???????? 07: 5a2
????????? ???????? 08: 0
????????? ???????? 09: System.TypeInitialization
?????? ??: 6.0.6002.2.2.0.256.6
??? ?????: 1049
OS: Vista Business SP2, RAM: 4G
Size:
Color:
This is not WLD 5.4, you have installed WLD 5.1. Probably the same package you've used 2008/08/29 when taking a trial.
Size:
Color:
Has helped so:
Has deleted WLD
Has cleared the directory "C:\Program Files\MS123\Wealth-Lab Developer 5"
Has installed WLD
Most likely stirred files of an old trial.
Size:
Color:
Again, this is not WLD 5.4.
Size:
Color:
In WLP 5.4 when using code that reads and write to text files I am constantly getting errors that indicate the FileOpen, FileWrite, FileRead do not exist in the current context..In WLP 4.5 such coding works fine and when I run the translator on the 4.5 code, the code runs fine, however if I write the coding from scratch in WLP 5.4 I get the errors noted above. Could you point me to some same coding in 5.4 that read and write to text files. Thanks
sample code below
CODE:
Please log in to see this code.
Size:
Color:
Those File* commands do not exist in C# or in WealthScript for version 5. They work in the WSTL because that includes a special library to interpret those statements. (If you're familiar with the syntax of the WSTL library, just include it with a "using" statement and you should be able to work with that old WealthScript syntax.)
Please browse through the
WL5 Wiki for lots of good information when making the transition from 4x to 5x. Specifically, looking in the Knowledge Base, Data category for an ASCII example.
Size:
Color:
The tip about WL5 Wiki was right on. You wrote a beautiful example of filewriting in WLP 5.4 back on 13 Oct of 2008. I will use it as a guide. for others reference link.. http://www2.wealth-lab.com/WL5WIKI/kbSaveOpenTrades.ashx
As for being familiar with the syntax of WSTL library, I am totally unfamiliar with the syntax other than being aware of the using statements at the beginning of those scripts that have been translated.
again...thanks
Size:
Color: