Forex Software — Not all bars read? 1/3

Re: Not all bars read? 1/3

null@example.com (nquental) — Thu, 01 Aug 2013 10:44:35 +0000

Thanks!

Re: Not all bars read? 1/3

null@example.com (Popov) — Thu, 01 Aug 2013 03:33:05 +0000

FSB automatically rounding volume to the unit when importing data (csv, hst, etc)?

I'll do it.

Re: Not all bars read? 1/3

null@example.com (nquental) — Wed, 31 Jul 2013 20:49:19 +0000

Dear Popov
Do you think in a future version it would be possible to have FSB automatically rounding volume to the unit when importing data (csv, hst, etc)?
Btw, it seems that TickStory is able to export, one time frame at a time, in FSB's format. However the volume problem with the decimal point persists. I've managed to post a message in their forum as well.
Cheers
Nuno

Re: Not all bars read? 1/3

null@example.com (nquental) — Wed, 31 Jul 2013 20:31:55 +0000

Whenever I export from Tickstory I get volumes with a decimal point:
2013-06-30 20:00:00,1.30077,1.30088,1.30074,1.30087,76.8400001525879

I don't know if Birt's script is able to get rid of them, but I also don't feel like trying now... This is so much time consuming!

Re: Not all bars read? 1/3

null@example.com (Blaiserboy) — Wed, 31 Jul 2013 10:31:32 +0000

check carefully how you set up the files to export as I have had no difficulty with Tickstory and use it almost daily

Tickstory data has holes in it, I do not know why that occurs, but from time to time you will find holes, best source is Dukas or use the tick data from tick story and then use Birt's script to convert the ticks to the preferred time frames.

Re: Not all bars read? 1/3

null@example.com (nquental) — Wed, 31 Jul 2013 10:15:33 +0000

Indeed, that would be a great idea.

Re: Not all bars read? 1/3

null@example.com (Popov) — Tue, 30 Jul 2013 22:35:46 +0000

Probably they can fix TickStory to export in FSB format. In that case I can promote it in forexsb website. Unfortunately no luck to post in their forum. Some email issue.

Re: Not all bars read? 1/3

null@example.com (nquental) — Tue, 30 Jul 2013 22:18:41 +0000

I wonder where tickstory is taking these numbers from!

Re: Not all bars read? 1/3

null@example.com (Popov) — Tue, 30 Jul 2013 22:03:50 +0000

Volume must be an integer number from 1 to 10 digits. Here is the RegularExpression

VolumePattern = @"\d{1,10}";

Re: Not all bars read? 1/3

null@example.com (nquental) — Tue, 30 Jul 2013 21:10:18 +0000

footon wrote:

The last one seems dodgy - 682190.40090.

But the csv was created by FSB, not by MT4.

Re: Not all bars read? 1/3

null@example.com (footon) — Tue, 30 Jul 2013 20:40:22 +0000

The last one seems dodgy - 682190.40090.

Re: Not all bars read? 1/3

null@example.com (nquental) — Tue, 30 Jul 2013 18:57:37 +0000

I get the same error message "Could not count the data bars" in a different circumstance:
- I imported the date into MT4 without problems (through tickstory, which is dukascopy data)
- Then I tried to import the hst files, which seems to work in FSB without problems
- But then FSB cannot open the data...

When opening the csv I notice this was the format the csv "got":
2003-05-04 00:00 1.12284 1.15366 1.12018 1.14824 682190.40090

SO maybe something needs to be corrected in this case?

Cheers
Nuno

Re: Not all bars read? 1/3

null@example.com (Popov) — Wed, 23 Jan 2013 09:44:48 +0000

I tested the file from the first post F20WIG60.csv.
It was oped by FSB Pro without problems.

In F20WIG1440.csv I changed time from 18:00 to 00:00 and it was opened also.

Re: Not all bars read? 1/3

null@example.com (Kasandra) — Thu, 10 Jan 2013 17:10:57 +0000

Replacing spaces with comas and the "-" with dots (as in the attached file) also did not help.

It should not be the date format, as the deafult data downloaded witht he FSB also is in 2011-07-25 and not 2011.07.25. Also the files for differnet timeframes which read well have date in 2011-07-25 format.

However, the problem must be in the date+hour recognition, not quotations, as the same quotations copied to another timeframe uploaded without a problem (although of course gave incorrect strategy results).

Re: Not all bars read? 1/3

null@example.com (kukreknecmi) — Thu, 10 Jan 2013 14:08:05 +0000

If i know right ;
your csv is in

2011-07-25 00:00:00 27.22 27.32 27.16 27.25 23789

format

FSB to read it, it should be like in this:

2011.07.25,00:00:00, 27.22,27.32,27.16,27.25,23789

Saving it as ANSI also helps size, instead of uuencode.