[Click] nsclick dump/trace paths

[David Bath]

Yes I agree - the dump configuration should be on a per element basis... and I have to say I quite like the current $NODENAME$DUMPTARGET arrangement - it keeps the output very neat.  From my point of view, and additional DumpPath("<myunixpath>") type directive in the script would be handy, as it doesn't break any existing scripts - DumpPath("./") could be the assumed default.  I'm not sure this is particularly 'anti-unix'... just think of make files and TARGET= options to specify the base path.  

However, I also recognise my complete novice status in Click development, so I am happy to be guided by sager voices than mine.

Best Regards,
Dave

-----Original Message-----
From: Bart Braem [mailto:bart.braem at ua.ac.be] 
Sent: 28 February 2007 14:45
To: David Bath
Subject: Re: [Click] nsclick dump/trace paths

Hi David,

There are some other possibilities too, which we prefer. You should do the dump configuration in the element itself. Of course, the current way where Click prepends nodenames to the dumps should then be changed. We see a number of solutions:
- append the nodename (this breaks current scripts but it is very easy to
implement)
- search for the last / in the dump target and insert the nodename right after it
- add a keyword PATH, so the dumps get written to $PATH/$NODENAME$DUMPTARGET (not very unix, separating a path and a file)

We propose to implement the second solution, what do you think? What do the others think?

Regards,
Bart


On Wednesday 28 February 2007 11:08, David Bath wrote:
> Hey there,
>
> Thanks for the reply.  That's rather irritating to know!  However, I 
> think it would be a good idea to try and implement...
>
> I guess ideally what I'd like is just to add a new Click language 
> option which allows you to set an output path (for anything that 
> generates a log file), and then all the elements which write out just 
> append to this path...
>
> Is that something that you might be able to give me some pointers on?
>
> Best Regards,
>
> Dave
>
> -----Original Message-----
> From: Bart Braem [mailto:bart.braem at ua.ac.be]
> Sent: 28 February 2007 07:43
> To: click at amsterdam.lcs.mit.edu
> Cc: David Bath
> Subject: Re: [Click] nsclick dump/trace paths
>
> On Tuesday 27 February 2007 19:35, David Bath wrote:
> > I have a quick question about click paths when using nsclick, and 
> > operations such as toDump etc.  Is there any way to specify in the 
> > click config the basepath for these output files?  Currently they're 
> > all appearing mixed in with my tcl scripting for ns...
>
> David,
>
> That's currently not possible. We had the same problem last week. 
> There is currently no way to set a path in the ToDump element. Adding 
> it to the code should not be that hard though, if you need any help 
> there feel free to ask.
>
> Regards.
> Bart
> --
> Bart Braem
> PATS research group
> Dept. of Mathematics and Computer Sciences University of Antwerp 
> Campus Middelheim, G2.36 Middelheimlaan 1 B-2020 Antwerpen, Belgium 
> Phone: +32
> (0)3 265.35.19
> Fax: +32 (0)3 265.37.77
> Web: www.pats.ua.ac.be/bart.braem

--
Bart Braem
PATS research group
Dept. of Mathematics and Computer Sciences University of Antwerp Campus Middelheim, G3.30 Middelheimlaan 1 B-2020 Antwerpen, Belgium
Phone: +32 (0)3 265.32.91
Fax: +32 (0)3 265.37.77
Web: www.pats.ua.ac.be/bart.braem