search for: straigthforward

...red computer (a Mac pro) in our lab, that is dedicated to execute R code for large simulations (over a few days). We have a VNC option to remote control the computer, with a shared used session, but this is not really needed in most of the cases. I would like to do some ssh access. This is pretty straigthforward, and I am able to launch commands using R -e 'source("myfile.R")' & However, it could be useful to check the advancement of the computation from time to time, again via ssh. Is there any way to do this? Regards, Timothée Poisot ---------------------------------- Timothé...

...lation is not possible with my own data unfortunately, as the random effects are (likely to be) different with respect to two factors: I need to express something like "random=list(b0 = ~1, b1 = ~treatment)". When leaving away the random effects I get an error message as well, which is straigthforward from the above, because nlme<-function(..., random=fixed, ...){lots-of-code} ~~~~~~~~~~~~ and the fixed effects are expressed as (list of) formulae. I had the same problem with R-1.2.1 and nlme-3.1-9. Am I missing something? Thanks in advance ... Uli...

is there a straigthforward way to get the holidays for Toronto ? like the function for NYSE e.g. the timeDate class says that setting a finCenter will give the right holidays, but how? thank you very much. stephen

Hi, I have two DSL line from the different provider connected to my Linux Router Firewall. Server_A is behind the Linux Router Firewall. DSL0 -- | ---- LINUX_ROUTER_FW -- SERVER_A DSL1 -- I have the following IPTABLES command to make incoming access to Server A''s web service throught port 82 as below: - $IPTABLES -t nat -A PREROUTING -i eth1 -p tcp --dport 82 -j DNAT

...STN) For the moment, item 4 definitely isn't feasible; even if we get some hardware to switch over E1/T1/PRI whatever interfaves, card or interface initialisation will kill active calls. Item 2 would be plain file on-disk data; for an active/standby cluster replicating these should be pretty straigthforward using either shared storage or an apropriate filesystem/blockdevice replication system. I've personaly had good experience with drbd (block device replication over the network; only supports 2 nodes in active/standby configuration but works quite well for that.) Item 3 should also feasible; th...

...bullet point apply: we shouldn’t do it unless it gets in the way of running/debugging the program. > > I agree that these optimizations should not be done at -O0. I think not doing them is actually an improvement: you give the user what they asked, i.e. "no optimization", and an as-straigthforward-as-possible mapping from source to assembly. > >>> * FastISel doesn’t\ seem to handle functions with switch statements, so it falls back to DAGISel. DAGISel produces code that's a lot better than GlobalISel for switch statement at -O0. I'm not sure if we need to do something he...

Hi Kristof, > On Apr 6, 2017, at 6:53 AM, Kristof Beyls <kristof.beyls at arm.com> wrote: > > I've been digging a little bit deeper into the biggest performance regressions I've observed. > > What I've observed so far is: > * A lot of the biggest regressions are caused by unnecessarily moving floating point values through general purpose registers. I've

...previous bullet point apply: we shouldn’t do it unless it gets in the way of running/debugging the program. I agree that these optimizations should not be done at -O0. I think not doing them is actually an improvement: you give the user what they asked, i.e. "no optimization", and an as-straigthforward-as-possible mapping from source to assembly. * FastISel doesn’t\ seem to handle functions with switch statements, so it falls back to DAGISel. DAGISel produces code that's a lot better than GlobalISel for switch statement at -O0. I'm not sure if we need to do something here before enabling...

...we shouldn’t do it unless it gets in the way of running/debugging the > program. > > > I agree that these optimizations should not be done at -O0. I think not > doing them is actually an improvement: you give the user what they asked, > i.e. "no optimization", and an as-straigthforward-as-possible mapping from > source to assembly. > > * FastISel doesn’t\ seem to handle functions with switch statements, so it > falls back to DAGISel. DAGISel produces code that's a lot better than > GlobalISel for switch statement at -O0. I'm not sure if we need to do > s...

...do it unless it gets in the way of running/debugging the program. >>>>> >>>>> I agree that these optimizations should not be done at -O0. I think not doing them is actually an improvement: you give the user what they asked, i.e. "no optimization", and an as-straigthforward-as-possible mapping from source to assembly. >>>>> >>>>>>> * FastISel doesn’t\ seem to handle functions with switch statements, so it falls back to DAGISel. DAGISel produces code that's a lot better than GlobalISel for switch statement at -O0. I'm not su...