JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for BUGS Archives


BUGS Archives

BUGS Archives


BUGS@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BUGS Home

BUGS Home

BUGS  2006

BUGS 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: handling paths in scripts (summary)

From:

Andreas Krause <[log in to unmask]>

Reply-To:

Andreas Krause <[log in to unmask]>

Date:

Tue, 21 Feb 2006 11:05:16 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (98 lines)

Summary of what I received within half a day:

12 out of office replies
1 unknown recipient notification
9 suggestions to use BRUGS (which does not work in my particular situation, and I had inquired on winbugs)
4 requests to share solutions if I receive any
3 other replies, among them one suggesting to use a path that is a subdirectory of c:\program files\winbugs14 (the only suggested solution that actually implements a relative path but should be prevented unless you have admin rights on your system - but then, writing to a system directory is not a good idea)
1 email from an author of (win)bugs, Andrew Thomas, inquiring about details and generating hope in me that the desired feature might be added in some future version

It seems that many list members are actually not winbugs but BRUGS users and this might need clarification in postings.
Thanks to everyone.

  Andreas



> -----Original Message-----
> From: Andreas Krause 
> Sent: Monday, February 20, 2006 2:54 PM
> To: [log in to unmask]
> Subject: handling paths in scripts
> 
> 
> 
> I would like to discuss or learn how to "best" handle paths 
> when writing winbugs scripts. I am not happy with the current 
> status (my current status, to be precise) and I wonder if 
> there are better ways to handle path names.
> 
> Situation: Have a script file that reads a model file, a data 
> file, and an init file. The log file and the values of the 
> chain(s) shall be written out.
> All of these files reside in a single directory.
> My ideal world is that there is no absolute path name 
> involved such that directories can be transfered to other 
> paths, computers, or people easily.
> 
> The script file might look like this:
> 
> check('c:/project999/model.txt')
> data('c:/project999/data.txt')
> inits(1, 'c:/project999/inits.txt')
> [ ... ]
> coda(*, 'c:/project999/values') 
> save('c:/project999/log.odc')
> 
> In reality the directory is more similar to something like 
> c:/Documents and Settings/akrause/My 
> Documents/projects/modeling/model5678/winbugs/
> 
> Having to write a lengthy path name five times into a script 
> is not only displeasing to the eye, it is also more 
> error-prone than defining a directory at the beginning of a 
> script and then using relative paths throughout the remainder 
> of the script.
> 
> In an ideal world there would be no absolute path at all. I 
> set the startup-directory for the winBUGS shortcut to my 
> project directory, but seemingly without effect. Saving to a 
> file stored the file in the winbugs directory, c:\program 
> files\winbugs14.
> 
> Can someone point me to a solution where
> a) no absolute path is needed or
> b) something like this would work in a winbugs script:
> dir='c:/project999/'
> check(dir+'model.txt')
> data(dir+'data.txt')
> etc.
> 
> Any further insights are highly welcome.
> 
> Thanks!
> 
> 	Andreas
> 
> Note: I searched the archive, promised.
> 
> 
> Andreas Krause, PhD
> Pharsight Corporation
> Strategic Consulting Services
> Phone:	+41-61-481 39 74
> Fax: 		+41-61-481 39 78
> Cell: 	+41-76-324 75 54
> 

-------------------------------------------------------------------
This list is for discussion of modelling issues and the BUGS software.
For help with crashes and error messages, first mail [log in to unmask]

To mail the BUGS list, mail to [log in to unmask]
Before mailing, please check the archive at www.jiscmail.ac.uk/lists/bugs.html
Please do not mail attachments to the list.

To leave the BUGS list, send LEAVE BUGS to [log in to unmask]
If this fails, mail [log in to unmask], NOT the whole list

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager