Conference item

ABNORMAL SALIENCY PROCESSING IN A PATIENT WITH VISUAL FORM AGNOSIA

Publication status:: Published

Actions

Email

Email this record

Send the bibliographic details of this record to your email address.

Your Email
Please enter the email address that the record information will be sent to.

-
Your message (optional)
Please add any additional information to be included within the email.
Cite

Cite this record

APA Style

Mannan, S., Rosenthal, C., Kennard, C., Graham, R., & Hicks, S. (2010). ABNORMAL SALIENCY PROCESSING IN A PATIENT WITH VISUAL FORM AGNOSIA. JOURNAL OF NEUROLOGY NEUROSURGERY AND PSYCHIATRY, 81(11), E44–E44.

MLA Style

Mannan, S., et al. “ABNORMAL SALIENCY PROCESSING IN A PATIENT WITH VISUAL FORM AGNOSIA.” JOURNAL OF NEUROLOGY NEUROSURGERY AND PSYCHIATRY, vol. 81, no. 11, 2010, pp. E44–E44.

Chicago Style

Mannan, S, C Rosenthal, C Kennard, R Graham, and S Hicks. 2010. “ABNORMAL SALIENCY PROCESSING IN A PATIENT WITH VISUAL FORM AGNOSIA.” In JOURNAL OF NEUROLOGY NEUROSURGERY AND PSYCHIATRY, 81:E44–E44.
Share
Print

Access Document

Publisher copy:: 10.1136/jnnp.2010.226340.108

Authors

+ Mannan, S More by this author

Role:: Author

+ Rosenthal, C More by this author

Role:: Author

+ Kennard, C More by this author

Institution:: University of Oxford
Division:: MPLS
Department:: Engineering Science
Sub department:: Institute of Biomedical Engineering
Role:: Author

+ Graham, R More by this author

Role:: Author

+ Hicks, S More by this author

Role:: Author

Host title:: JOURNAL OF NEUROLOGY NEUROSURGERY AND PSYCHIATRY
Volume:: 81
Issue:: 11
Pages:: E44-E44
Publication date:: 2010-11-01
DOI:: 10.1136/jnnp.2010.226340.108
ISSN:: 0022-3050

Pubs id:: pubs:119804
UUID:: uuid:5ff3c172-db7e-4c38-a096-930ea31e1bf9
Local pid:: pubs:119804
Source identifiers:: 119804
Deposit date:: 2012-12-19

Terms of use

Copyright date:: 2010

Licence:: Terms and Conditions of Use for Oxford University Research Archive

Views and Downloads

About views and downloads

If you are the owner of this record, you can report an update to it here: Report update to this record

TO TOP