comp.lang.idl-pvwave archive: archive » Acknowledging IDL help/code from this group in academic publications

Home » Public Forums » archive » Acknowledging IDL help/code from this group in academic publications

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Acknowledging IDL help/code from this group in academic publications [message #74410]

Tue, 18 January 2011 08:30

Robin Wilson
Messages: 40
Registered: August 2010

Member

Hi all,

Firstly, I want to say thank you to the members of this group for the
help they have given me with IDL over the last few years. I'd just like
to check what the procedure is for acknowledging this help (particularly
if the help comes in the form of code samples, or even fully written
routines) in academic publications.

I obviously don't want to 'rip anyone off' or be accused of stealing
work from other people, so what do people suggest for attribution?
Should I add something to the acknowledgments in the paper saying thanks
to the members of the IDL newsgroup for their help, or does there need
to be something more than this?

Obviously when I have used code provided from IDL routine libraries on
the internet I have kept the code headers complete, so it is obvious who
the original author was. However, if people just read my paper they
won't be aware that these people contributed code. Is this a problem?

I'm hoping for a little bit of a discussion on this, so that I (and
others who use advice and code from these groups) can do the right thing.

Cheers,

Robin

Report message to a moderator

[Message index]

		Acknowledging IDL help/code from this group in academic publications By: Robin Wilson on Tue, 18 January 2011 08:30
		Re: Acknowledging IDL help/code from this group in academic publications By: Jeremy Bailin on Wed, 19 January 2011 03:56

Previous Topic:	FINDFILE problems IDL 8 LINUX
Next Topic:	Re: Book Review: Object-Oriented Programming with IDL

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Nov 29 14:03:15 PST 2025

Total time taken to generate the page: 0.56252 seconds