parameter-passing

I am wondering how I might be able to run 500 parallel jobs in R using the Rscript function. I currently have an R file that has the header on top: args <- commandArgs(TRUE) B <- as.numeric(args[1]) Num.Cores <- as.numeric(args[2]) Outside of the R file, I wish to pass which of the 500 jobs are to be run, which is specified by B . Also, I would like to control the number of cores/CPUs available to each job, Num.Cores . I am wondering if there is software or guides that can allow this. I currently have a CentOS 7/Linux server and I know one way is to install Slurm. However, it is quite a hassle

Setting Public Property Values on the Command Line of an msi follows the pattern MyInstaller.msi PUBLICPROPERTY="someValue" This works on "Command Prompt" aka cmd.exe and powershell. But MyInstaller.msi PUBLICPROPERTY="" does not work like expected in powershell. I expected that it sets PUBLICPROPERTY to null but it sets PUBLICPROPERTY to the value "CURRENTDIRECTORY="C:\temp\msi\"" (it does work like expected with cmd.exe). Why do powershell and cmd.exe behaviour different, and how can it be fixed? PowerShell, on Windows of necessity, performs re-quoting of your arguments behind the scenes.

I'm trying to pass a list to a function in Lisp, and change the contents of that list within the function without affecting the original list. I've read that Lisp is pass-by-value, and it's true, but there is something else going on that I don't quite understand. For example, this code works as expected: (defun test () (setf original '(a b c)) (modify original) (print original)) (defun modify (n) (setf n '(x y z)) n) If you call (test), it prints (a b c) even though (modify) returns (x y z). However, it doesn't work that way if you try to change just part of the list. I assume this has

I'm developping a REST API and I need to tranport cryptograms to authenticate the message for each request in a applicative process (MAC encryption from secret keys). I was thinking about putting them in the message header to avoid adding non-data information in the message body which contains the posted/retrieved object (XML or JSON). Is it a best practise ? Can I add as many parameters I want in the header ? I've read that I must prefix them with "x-". The behavior of this parameter is exactly the same than Path or Query params ? I'm using Jersey. Thank you for you help. Yes I believe it is

I have a URL : foo.php?name=adam&lName=scott , and in foo.php I have a form which gives me values of rectangleLength & rectangleBreadth with a submit button. When I click this submit button with form action as $_SERVER['REQUEST_URI'] , I get this result URL: foo.php?rectangleLength=10&rectangleBreadth=5 (these values have been filled in by the user). Notice that I am losing my previous values name & lName from the URL. How can I keep them? Also, keep in mind that I have to come back to foo.php and if the user wants to submit the form again then the length and breadth values should change. You

I'm wondering the opinion of what is the best way to pass a lot of values between MULTIPLE pages. I was thinking of either saving the values to a database, using context.Items[], or Session[]. I'm not sure about what is the best method. I'm passing probably around 40 variables.This will be during a checkout process so they should be persisted through the users lifecycle. The user does not change the values after they are entered the first time. The values would be like Billing Address, First and Last name etc Session is probably the most efficient. However, if the session times out or is lost

Consider these classes: #include <iostream> #include <string> class A { std::string test; public: A (std::string t) : test(std::move(t)) {} A (const A & other) { *this = other; } A (A && other) { *this = std::move(other); } A & operator = (const A & other) { std::cerr<<"copying A"<<std::endl; test = other.test; return *this; } A & operator = (A && other) { std::cerr<<"move A"<<std::endl; test = other.test; return *this; } }; class B { A a; public: B (A && a) : a(std::move(a)) {} B (A const & a) : a(a) {} }; When creating a B , I always have an optimal forward path for A , one move for rvalues