Hi Marek,
I would just have some patience for now and just figure that everyone is working hard behind the scenes to solve this. I would give it a month and then reassess things. You were the first to purchase Titan's, even BEFORE the code developers got their hands on them so you ultimately took a large risk with that. No different from buying an iPhone 4 on release day for example and then having to wait for Apple to release a firmware update to solve the signal dropout problem. It is the same thing here. So I would suggest waiting to see if a fix is possible and if not then discuss with NVIDIA what the options are.
My advise for anyone buying a GTX GPU machine right now is to go for the tried and tested 680 or wait a few weeks for us to verify the 780s and then if they are good go with them. Stay clear of the Titan's until we have found a fix.
All the best
Ross
On Jun 19, 2013, at 10:55, "Marek Maly" <marek.maly.ujep.cz> wrote:
> OK, so maybe more appropriate would be call it "cuFFT/Titan" specific
> or "CUDA/Titan" specific which I am using as well.
>
> The problem which I wanted to point on is that you can perhaps
> hardly find some another software (if possible some some standard
> GPU testing software) where this tricky errs could be detected which
> might complicate eventual RMAing here.
>
> Moreover it seems that the standard RMA process where one just exchange
> bad piece for a good one does not solve the problem.
>
> Only solution is here at the given moment to get the money back or to
> exchange Titan for GTX 780 even with financial loss.
>
> OK, maybe it is too early to be so pessimistic so for the moment let's
> hope that NVIDIA will
> fix this issue soon and that Scott will not find another couple of
> different Amber/Titan
> related problems ...
>
> Best,
>
> M.
>
>
>
>
> Dne Wed, 19 Jun 2013 19:50:35 +0200 Daniel Roe <daniel.r.roe.gmail.com>
> napsal/-a:
>
>> Hi,
>>
>> On Wed, Jun 19, 2013 at 11:17 AM, Marek Maly <marek.maly.ujep.cz> wrote:
>>> It's just a pity that the issues are here perhaps only Amber specific
>>
>> I don't think this is an Amber-specific problem; rather, it is because
>> the Amber GPU code is fully deterministic that allows the problem to
>> be found (Scott correct me if I'm wrong).
>>
>> -Dan
>>
>
>
> --
> Tato zpráva byla vytvořena převratným poštovním klientem Opery:
> http://www.opera.com/mail/
>
> _______________________________________________
> AMBER mailing list
> AMBER.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Wed Jun 19 2013 - 19:30:03 PDT
