search for: ll4

...e example (see below). Why the negative sigma? John > y <- rt(100, df=1)> m1<-fitDist(y, type="realline")Warning messages:1: In MLE(ll3, start = list(eta.mu = eta.mu, eta.sigma = eta.sigma, : possible convergence problem: optim gave code=1 false convergence (8)2: In MLE(ll4, start = list(eta.mu = eta.mu, eta.sigma = eta.sigma, : possible convergence problem: optim gave code=1 false convergence (8)3: In MLE(ll4, start = list(eta.mu = eta.mu, eta.sigma = eta.sigma, : possible convergence problem: optim gave code=1 false convergence (8)4: In MLE(ll4, start = list(e...

Hi, I am trying to use drc package to calculate IC50 value. The ED50 calculated in some models (LL4 for example) as a response half-way between the upper and lower limit, which is the definition of the relative IC50 value. Does that mean the ED50 in drc package is IC50? How the ED function in drc package distinguish to estimate ED or IC values? Thanks a lot [[alternative HTML version deleted]...

Hello everyone, I'm using the LLVM for a JIT-Client under Windows 64bit. I tried various stuff with it and noticed, that object files or libraries which are generated by the Visual Studio Compiler 2015 or 2017 will break the jitted code, when they are added to the process. I opened a bug for this a while ago (https://bugs.llvm.org/show_bug.cgi?id=39447) - sadly this bug will become a stopper

...e instruction that compiler often generates code based of __ImageBase. I show you a short snippet of the assembly output. mov eax, DWORD PTR ?myInt@@3HA ; myInt lea rdi, OFFSET FLAT:__ImageBase xor ebx, ebx Then these offset is used to jump to some labels like "$LL4 at execute:". When the object file gets added to the jitting process this offset generation seems to be broken. Executing the code coming from the object file will lead to a crash. The crash address will always be exactly the address I used to overload __ImageBase with. So it seems that t...

...generates code based of __ImageBase. I show > you a short snippet of the assembly output. > mov eax, DWORD PTR ?myInt@@3HA ; myInt > lea rdi,* OFFSET FLAT*:__ImageBase > xor ebx, ebx > > > > Then these offset is used to jump to some labels like "$LL4 at execute:". > > When the object file gets added to the jitting process this offset > generation seems to be broken. Executing the code coming from the object > file will lead to a crash. The crash address will always be exactly the > address I used to overload __ImageBase with...

...a switch case instruction that compiler often generates code based of __ImageBase. I show you a short snippet of the assembly output. mov eax, DWORD PTR ?myInt@@3HA ; myInt lea rdi, OFFSET FLAT:__ImageBase xor ebx, ebx Then these offset is used to jump to some labels like "$LL4 at execute:". When the object file gets added to the jitting process this offset generation seems to be broken. Executing the code coming from the object file will lead to a crash. The crash address will always be exactly the address I used to overload __ImageBase with. So it seems that th...