[ADMB Users] running admb from R using system()

[Rubén Roa]

I can try to duplicate it. I have been using R and ADMB executables for a while without problems but calling the executable from a batch file.
Cheers

____________________________________________________________________________________

Dr. Rubén Roa-Ureta
AZTI - Tecnalia / Marine Research Unit
Txatxarramendi Ugartea z/g
48395 Sukarrieta (Bizkaia)
SPAIN



 


________________________________

	De: users-bounces at admb-project.org [mailto:users-bounces at admb-project.org] En nombre de Ian Fiske
	Enviado el: lunes, 31 de mayo de 2010 11:52
	Para: Benedikt Gehr; users at admb-project.org
	Asunto: Re: [ADMB Users] running admb from R using system()
	
	
	Definitely sounds windowsy.  I would try a couple of things.   

	(1)  Upgrade R to the latest version.  Maybe you'll be lucky ;)
	(2)  Write a windows batch file that basically does nothing but call your model executable.  Call this batch file with system() in R.  Maybe the extra layer of indirection can prevent the crash.
	(3)  Post to R-Help because this is starting to sound like a real R problem.  Can anyone else with a windows machine duplicate this?

	Best,
	Ian
	
	
	On Mon, May 31, 2010 at 5:43 AM, Benedikt Gehr <benedikt.gehr at ieu.uzh.ch> wrote:
	

		Thanks for the fast reply. I'm using Windows XP  v. 2002 with R 2.10.1.
		When I invoke system('makeadm stocpool') R produces the 3 files model.cpp, model.htp and model.exe. When I double klick on model.exe the model is executed and all the admb output files are produced.
		However when I invoke " system('stoc.exe')" in R, R simply shuts down and the error window appears: "R for Windows GUI front-end has encountered a problem and needs to close."
		I'm not sure what you mean by "RAM filling up".
		
		I guess this is a windows thing because Dave Fournier tried to help me and run the model on linux and windows 2000 and did not get an error.
		

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.admb-project.org/pipermail/users/attachments/20100531/30ec74da/attachment.html>