Difference between revisions of "Publications"
(→) |
Rikesh Patel (talk | contribs) |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 7: | Line 7: | ||
After much fiddling and rewriting of code, I've managed to make the BibTex extension work on this wiki. Firstly, there are some simple changes to a BibTex code that need to be made in order to make it both work on here and if/when someone downloads the code. | After much fiddling and rewriting of code, I've managed to make the BibTex extension work on this wiki. Firstly, there are some simple changes to a BibTex code that need to be made in order to make it both work on here and if/when someone downloads the code. | ||
− | * The authors need to be separated. This is done so that external people can be main/co-authors of papers and not be linked in this wiki. I've created two new tags that only work on this wiki, and will disappear when downloaded. To add a publication, use | + | * The authors need to be separated. This is done so that external people can be main/co-authors of papers and not be linked in this wiki. I've created two new tags (preauth, postauth) that only work on this wiki, and will disappear when downloaded. You could have no linked authors by putting all authors into any of these two tags. To add a publication, use |
<code><nowiki> <bibtex> "bibtex code" </bibtex> </nowiki></code> | <code><nowiki> <bibtex> "bibtex code" </bibtex> </nowiki></code> | ||
− | * REQUIRED - All '''internal''' names in the author tag need to be | + | * REQUIRED - All '''internal''' names in the author tag need to be in normal order (i.e. first name first), preferably full (in order to be linked without redirects), and separated by 'and'. No commas should be present inside the tag! |
− | * OPTIONAL - Main '''external''' author names are to be put in | + | * OPTIONAL - Main '''external''' author names are to be put in <code>preauth = {....}</code> tag. Again separated by 'and' but do not need to be full. |
− | * OPTIONAL - Co-author '''external''' names are to be put in | + | * OPTIONAL - Co-author '''external''' names are to be put in <code>postauth = {.....}</code> tag. Again separated by 'and' but do not need to be full. |
− | Check out the | + | * OPTIONAL - A link to a pdf can be put into <code>pdf = {.....}</code> tag. Similarly, links can be put into <code>ps = {.....}</code> and <code>url = {.....}</code> for postscripts and internal/external links respectively. |
+ | |||
+ | The squiggly brackets could be quotation marks in some peoples BibTex but this doesn't matter (tested by Matt). | ||
+ | |||
+ | Check out the examples below. Personal page links will work once they are made/redirected. | ||
== == | == == | ||
Line 24: | Line 28: | ||
@ARTICLE{Summers2010, preauth = {David Summers}, author = {Matt Clark and Ian Stockford and Samuel Achamfuo-Yeboah}, postauth = {Pereira Do Carmo, J}, title = {Modulated light camera for space applications and assessment via a test bench system}, journal = {Acta Astronautica}, year = {2010}, volume = {66}, pages = {1399 - 1403}, number = {9-10}, note = {ASIC design;Imaging arrays;Innovation triangle initiatives;Large structures;Modulated laser light;Modulated light camera;Modulation schemes;Optical ranging;Phase Change;Rendezvous and docking;Roadmap;Space-borne instruments;Test benches;Test systems;University of Nottingham;}, abstract = {The modulated light camera technology, developed by the University of Nottingham, illuminates a target with modulated laser light and measures the distance to the target scene by the phase change of the return, across an imaging array. This enables the measurement of distance to different parts of the scene simultaneously, on a pixel by pixel basis. A prototype camera has been assembled under the ESA Innovation Triangle Initiative and supplied to SEA where there has been an assessment of the potential of this technology for a range of space applications, including Rover Vision, Rendezvous and Docking, and monitoring the deployment of large structures. The supplied device has been tested with appropriate modulation schemes. Finally, a roadmap has been devised to show the developments needed to take this test system forward to a fully fledged spaceborne instrument. © 2009 Elsevier Ltd. All rights reserved.}, address = {Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom}, copyright = {Compilation and indexing terms, Copyright 2010 Elsevier Inc.}, issn = {00945765}, key = {Cameras}, keywords = {Application specific integrated circuits;Electric power supplies to apparatus;Innovation;Integrated circuits;Manned space flight;Pixels;Space applications;Space rendezvous;Technological forecasting;}, language = {English}, owner = {rp}, timestamp = {2010.11.19}, url = {http://dx.doi.org/10.1016/j.actaastro.2009.10.030} | @ARTICLE{Summers2010, preauth = {David Summers}, author = {Matt Clark and Ian Stockford and Samuel Achamfuo-Yeboah}, postauth = {Pereira Do Carmo, J}, title = {Modulated light camera for space applications and assessment via a test bench system}, journal = {Acta Astronautica}, year = {2010}, volume = {66}, pages = {1399 - 1403}, number = {9-10}, note = {ASIC design;Imaging arrays;Innovation triangle initiatives;Large structures;Modulated laser light;Modulated light camera;Modulation schemes;Optical ranging;Phase Change;Rendezvous and docking;Roadmap;Space-borne instruments;Test benches;Test systems;University of Nottingham;}, abstract = {The modulated light camera technology, developed by the University of Nottingham, illuminates a target with modulated laser light and measures the distance to the target scene by the phase change of the return, across an imaging array. This enables the measurement of distance to different parts of the scene simultaneously, on a pixel by pixel basis. A prototype camera has been assembled under the ESA Innovation Triangle Initiative and supplied to SEA where there has been an assessment of the potential of this technology for a range of space applications, including Rover Vision, Rendezvous and Docking, and monitoring the deployment of large structures. The supplied device has been tested with appropriate modulation schemes. Finally, a roadmap has been devised to show the developments needed to take this test system forward to a fully fledged spaceborne instrument. © 2009 Elsevier Ltd. All rights reserved.}, address = {Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom}, copyright = {Compilation and indexing terms, Copyright 2010 Elsevier Inc.}, issn = {00945765}, key = {Cameras}, keywords = {Application specific integrated circuits;Electric power supplies to apparatus;Innovation;Integrated circuits;Manned space flight;Pixels;Space applications;Space rendezvous;Technological forecasting;}, language = {English}, owner = {rp}, timestamp = {2010.11.19}, url = {http://dx.doi.org/10.1016/j.actaastro.2009.10.030} | ||
} | } | ||
+ | </bibtex> | ||
− | @article{ | + | <bibtex> |
+ | @article{m41, | ||
title="Adaptive acoustic imaging using aberration correction in difficult materials", | title="Adaptive acoustic imaging using aberration correction in difficult materials", | ||
author="S D Sharples and M Clark and I J Collison and M G Somekh", | author="S D Sharples and M Clark and I J Collison and M G Somekh", | ||
Line 32: | Line 38: | ||
number="2", | number="2", | ||
pages="78-80", | pages="78-80", | ||
− | year="2005" | + | year="2005", |
+ | pdf=" | ||
+ | http://optics.eee.nottingham.ac.uk/optics/papers/Laser_Ultrasound/papers/2005_insight_aberration_correction.pdf | ||
+ | " | ||
} | } | ||
</bibtex> | </bibtex> | ||
Line 38: | Line 47: | ||
== == | == == | ||
− | Its a bit of a pain now, but it needs to be done in order for it work with links on here AND (when bibtex link is clicked) come out with a bibtex that can be used straight away. At some point | + | *Uploading a pdf of a paper or poster/talk (which will be called a Tech report or type 'techreport' in BibTex) use this [[Special:Upload|upload file link]]. We're trying to get a naming convention going, so the uploaded file name should be '''type_year_place_title.pdf'''. Then put the full address of the uploaded pdf in the <code>pdf = {.....}</code> tag. Here is a [[Special:ListFiles|link to uploaded files]], you want to copy/paste the link marked '(file)'. |
+ | |||
+ | *To have a link to an internal or external page, put the address in the <code>url = {.....}</code> tag. | ||
+ | |||
+ | *Preferably, we want all pdfs and links in one ''maintained'' and ''backed up'' location, and this seems to be the best place for it. | ||
+ | |||
+ | Its a bit of a pain now, but it needs to be done in order for it work with links on here AND (when bibtex link is clicked) come out with a bibtex that can be used straight away. At some point name reversing should be implemented by for now, as long as tags are put in correctly, this should work properly. |
Latest revision as of 13:04, 18 March 2011
Applied Optics: Publications
The old list of publications can be found here
After much fiddling and rewriting of code, I've managed to make the BibTex extension work on this wiki. Firstly, there are some simple changes to a BibTex code that need to be made in order to make it both work on here and if/when someone downloads the code.
- The authors need to be separated. This is done so that external people can be main/co-authors of papers and not be linked in this wiki. I've created two new tags (preauth, postauth) that only work on this wiki, and will disappear when downloaded. You could have no linked authors by putting all authors into any of these two tags. To add a publication, use
<bibtex> "bibtex code" </bibtex>
- REQUIRED - All internal names in the author tag need to be in normal order (i.e. first name first), preferably full (in order to be linked without redirects), and separated by 'and'. No commas should be present inside the tag!
- OPTIONAL - Main external author names are to be put in
preauth = {....}
tag. Again separated by 'and' but do not need to be full.
- OPTIONAL - Co-author external names are to be put in
postauth = {.....}
tag. Again separated by 'and' but do not need to be full.
- OPTIONAL - A link to a pdf can be put into
pdf = {.....}
tag. Similarly, links can be put intops = {.....}
andurl = {.....}
for postscripts and internal/external links respectively.
The squiggly brackets could be quotation marks in some peoples BibTex but this doesn't matter (tested by Matt).
Check out the examples below. Personal page links will work once they are made/redirected.
Matt Clark, Ian Stockford, Samuel Achamfuo-Yeboah - Modulated light camera for space applications and assessment via a test bench system
- Acta Astronautica 66(9-10):1399 - 1403, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom,2010
- http://dx.doi.org/10.1016/j.actaastro.2009.10.030
BibtexAuthor : Matt Clark, Ian Stockford, Samuel Achamfuo-Yeboah
Title : Modulated light camera for space applications and assessment via a test bench system
In : Acta Astronautica -
Address : Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom
Date : 2010
S D Sharples, M Clark, I J Collison, M G Somekh - Adaptive acoustic imaging using aberration correction in difficult materials
- Insight 47(2):78-80,2005
- BibtexAuthor : S D Sharples, M Clark, I J Collison, M G Somekh
Title : Adaptive acoustic imaging using aberration correction in difficult materials
In : Insight -
Address :
Date : 2005
- Uploading a pdf of a paper or poster/talk (which will be called a Tech report or type 'techreport' in BibTex) use this upload file link. We're trying to get a naming convention going, so the uploaded file name should be type_year_place_title.pdf. Then put the full address of the uploaded pdf in the
pdf = {.....}
tag. Here is a link to uploaded files, you want to copy/paste the link marked '(file)'.
- To have a link to an internal or external page, put the address in the
url = {.....}
tag.
- Preferably, we want all pdfs and links in one maintained and backed up location, and this seems to be the best place for it.
Its a bit of a pain now, but it needs to be done in order for it work with links on here AND (when bibtex link is clicked) come out with a bibtex that can be used straight away. At some point name reversing should be implemented by for now, as long as tags are put in correctly, this should work properly.