Need Help With Calculating Quark/Day || 500TAC Bounty! :D

[Bombadil]

Hey guys!

I've been busy with writing a profit-switcher for ccminer/cudaminer, in C#, will be opensourced, and I've just finished the part where I could read from different web API's for info like difficulty, blockreward and exchange prices.
I set up a test with the hashrates of a GTX750TI as used hashrates, and it calculates it nicely for most algo's. Scrypt(-n), keccak and X11 are the same on other profit calculators like coinwarz.
But Quark (like classic Quark and Securecoin) end up way too low. My own experience already showed me that Quark is a lot more profitable, and so says Coinwarz. Hell, even Securecoin is on top on Coinwarz, but at the bottom on my list: http://pastebin.com/RMBUFNZN
Code used:

Code:

public double CalcBtcPerDay(double hashRateKh)
        {
            CoinsPerDay = BlockReward/(Difficulty*(Math.Pow(2,32))/(hashRateKh*1000)/3600/24);
            return BtcPerDay = CoinsPerDay*BestExchange.BtcPrice;
        }

Anyone care to take a look at this and tell me what I'm doing wrong? I'm mining ATM at a SRC pool, and after half an hour I'm already having as much unconfirmed coins as my calc said I would have over a day
500TAC (Talkcoin, 0.015BTC) bounty for the one who solves this riddle ^^"

[leicas]

Might be a problem of conversion between khash and Mhash, seems like you've got a 1 000 factor missing.

[Bombadil]

Might be a problem of conversion between khash and Mhash, seems like you've got a 1 000 factor missing.

Nah, it seems correct for other algo's. Here's a new (trimmed) list also showing the coins per day: http://pastebin.com/S3H5vq1m
Here is a CoinWarz with all the hashrates for 750ti already filled in: http://bit.ly/UoDd2N
So it's like quark has some mystery to it's diff calc I'd like to know that one.

Edit: Found it!

500TAC has been sent

[Lizzardis]

Any ETA on this switcher? That would be incredible!

[waldistons]

just a friendly advice if You haven't done it already: If You use HttpWebRequest or something like that, then set proxy to null as it will _REALLY_ speed up web request! (C# web interfaces use IE settings and setting proxy to null will save some time while doing request) I've experimented a lot with this, was trying to make web crawler a while ago

Code:

HttpWebRequest request = (HttpWebRequest)WebRequest.Create(prefix + host + ":" + port);
request.Proxy = null;

Hope this helps