|
|
| (184 intermediate revisions by 14 users not shown) |
| Line 1: |
Line 1: |
| This wiki houses projects, links, and other information regarding two courses. The main course pages (including readings, syllabus and so forth) are on the Courseworks site at:
| |
|
| |
|
| * [https://coursework.stanford.edu/portal/site/F09-PSYCH-204A-01 PSYCH-204A (Human Neuroimaging Methods)]
| |
| * [https://coursework.stanford.edu/portal/site/W09-PSYCH-221-01 PSYCH-221 (Applied Vision and Image Systems)].
| |
|
| |
|
| For research and software tools information please consult [http://white.stanford.edu/newlm/index.php/Main_Page VISTALAB wiki].
| | = Psych 221 Project Information= |
|
| |
|
| = Psych 204 (Human Neuroimaging Methods)=
| | * [[Project Guidelines]] describes the project write-up rubric. |
| | * [[Psych221 Project Suggestions]] for this and previous years. |
|
| |
|
| == Tutorials == | | == Project writeups == |
| | * [[Psych221-Projects-2023-Fall]] |
|
| |
|
| == Project Suggestions == | | == Past project writeups == |
|
| |
|
| Visit the [[Psych204-Projects | project suggestions page]] to see some of our ideas for you.
| | * [[Psych221-Projects-2022-Fall]] |
| | * [[Psych221-Projects-2021-Fall]] |
| | * [[Psych221-Projects-2020-Fall]] |
| | * [[Psych221-Projects-2019-Fall]] |
| | * [[Psych221-Projects-2018-Fall]] |
| | * [[Psych221-Projects-2017-Fall]] |
| | * [[Psych221-Projects-2016-Fall]] |
| | * [[Psych221-Projects-2015-Fall]] |
| | * [[Psych221-Projects-2015-Winter]] |
| | * [[Psych221-Projects-2014]] |
| | * [[Psych221-Projects-2013]] |
| | * [[Psych221-Projects-2012]] |
| | * [[Psych221-Projects-2011]] |
|
| |
|
| You are welcome to suggest a project. We encourage students who are working on neuroimaging to choose a project that advances their ongoing research.
| | (Even older project pages (from acorn)) |
|
| |
|
| The criteria for designing a good project are
| | * [http://acorn.stanford.edu/psych221/projects/2010/index.html Projects 2009-10] |
| | * [http://acorn.stanford.edu/psych221/projects/2009/index.htm Projects 2008-09] |
| | * [http://acorn.stanford.edu/psych221/projects/2008/index.htm Projects 2007-08] |
| | * [http://acorn.stanford.edu/psych221/projects/2007/index.htm Projects 2006-07] |
| | * [http://acorn.stanford.edu/psych221/projects/2006/index.htm Projects 2005-06] |
| | * [http://acorn.stanford.edu/psych221/projects/2005/index.htm Projects 2004-05] |
| | * [http://acorn.stanford.edu/psych221/projects/2003/index.htm Projects 2002-03] |
| | * [http://acorn.stanford.edu/psych221/projects/2002/index.htm Projects 2001-02] |
| | * [http://acorn.stanford.edu/psych221/projects/2000/index.html Projects 1999-00] |
| | * [http://acorn.stanford.edu/psych221/projects/1999/index.html Projects 1998-99] |
| | * [http://acorn.stanford.edu/psych221/projects/1998/index.html Projects 1997-98] |
|
| |
|
| * Choose a clear question you would like to answer or at least explore
| | = Helpful Mediawiki pages = |
| * Build on the concepts taught in the class | | * Consult [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents MediaWiki User's Guide] for information on editing the wiki and using wiki software. |
| * Follow the write-up guidelines below | | * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list] |
| * Plan for a brief (15-20 minute) project presentation in the last week of class | | * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ] |
| * You can work alone or in a small group | | * [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list] |
| | * [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language] |
| | * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki] |
| | * [https://www.mediawiki.org/wiki/Cheatsheet Mediawiki formatting cheat sheet] |
|
| |
|
| == Write-up Guidelines (Templates) ==
| |
|
| |
|
| === Goal === | | = [[Psych 284]] = |
| The purpose of the writeup is to document the question, methods, results, and conclusions of your class project.
| |
|
| |
|
| If your project involves writing source code or processing scripts, you should include the code on the wiki. Be sure to describe the purpose of your code and to edit the code for clarity. The purpose of placing the code online is to allow others to verify your methods and to learn from your ideas.
| | In Spring 2011 the course included a shared software project. There is a [[Psych 284 |Psych 284 course wiki page]] for commenting and discussing about the software project. |
|
| |
|
| You may include your in-class presentation slides as part of your writeup, but this should not be the entire writeup. We expect that much of your presentation's information will not be on your slides but rather will be in the wiki and your talk.
| | = [[Psych202-Projects-2013]] = |
|
| |
|
| === Organization === | | = Psych 204A/B = |
|
| |
|
| * Introduction - Motivate the problem. Describe what has been done in the past. What is the problem? What have people tried?
| | Some years, but not all, we perform projects in Psych 204A. |
| * Methods - Describe techniques used to measure data and/or source code algorithms.
| |
| Measure something? How? Develop code? What utilities/algorithms did you use?
| |
| * Results - Show relevant graphs and/or images. Explain them
| |
| * Conclusions - Describe what you learned. What worked? What didn't? Why? What should someone next year try?
| |
| * References _ List all references. Include links if papers where found online.
| |
| * Appendix I - Link in all source code, test images, etc, and give a description of each link. In some cases, your acquired data may be too large to store practically. In this case, use your judgement (or consult one of us) and only link the most relevant data.
| |
| * Appendix II - for groups only) - Work breakdown. Explain how the project work was divided among group members.
| |
|
| |
|
| As you make your class presentation, we will offer you feedback. Please use that feedback to clarify and improve your project write-up on the wiki. The completed wiki page should be done by XXXX
| | [[Psych204B-Projects-2010 | Psych 204B Projects 2010]] |
|
| |
|
| === Creating A Project Wiki ===
| | [[Psych204B-Projects-2012 | Psych 204B Projects 2012]] |
|
| |
|
| There should be a link in here to say (a) how to add a page for your project, (b) how to upload files and images, and (c) how to create new pages within your project.
| | [[Psych204B-Projects-2013 | Psych 204B Projects 2013]] |
|
| |
|
| Naming convention for a student's project should be YEAR-NAME-Intro, YEAR-NAME-Methods, YEAR-NAME- ....
| | = Administration = |
|
| |
|
| [[2009 Project Template]]
| | This section is for CAs. It will describe |
|
| |
|
| <ul> | | <ol> |
| <li> [[09-Winawer-Intro]] </li> | | <li> How students get their accounts and passwords - each student creates their own account. They create their own project page and work within that. </li> |
| <li> [[09-Winawer-Methods]] </li> | | <li> How we remove accounts at the end of the time - we delete them after class is over. The wiki pages stay up, though. </li> |
| <li> [[09-Winawer-Results]] </li> | | <li> Who has Bureaucrat/Sysop status on the Psych 221 mediawiki pages? Brian, Doug, Joyce </li> |
| <li> [[09-Winawer-Results-Excellent]] </li>
| | </ol> |
| <li> [[09-Winawer-Results-Problematic]] </li>
| |
| <li> [[09-Winawer-Conclusions]] </li>
| |
| <li> [[09-Winawer-Conclusions]] </li>
| |
| <li> [[09-Winawer-Conclusions]] </li>
| |
| <li> [[09-Winawer-Conclusions]] </li>
| |
| </ul> | |
|
| |
|
| == Project archives ==
| | Bureaucrat/Sysop users can manually create accounts at this page: [[Special:UserLogin]] |
| | |
| [[Psych 204 - Project Archives 2009 ]]
| |
| | |
| * [[09-Winawer]]
| |
| * [[09-Wandell]]
| |
| | |
| = Psych 221 =
| |
| | |
| == Tutorials ==
| |
| | |
| == Project Suggestions ==
| |
| | |
| === Visibility of Font Contours ===
| |
| | |
| ISET has tools for modeling scenes, cameras, displays and the retinal response patterns of the human eye. We will use these tools to predict 1) the irradiance image of a displayed character and 2) the retinal cone photoreceptor response. We will then apply basic edge detectors to the photoreceptor responses under various noise conditions, perhaps including eye movements. This will provide use with a measure of the perceived sharpness and continuity of the font on the display under specified viewing conditions.
| |
| <br> '''Project consultants:''' Joyce Farrell and Brian Wandell
| |
| | |
| === Noise in the digital camera imaging pipeline ===
| |
| | |
| Color imaging sensors used in digital cameras acquire three spatially subsampled color channels with a color filter array (CFA) mosaic. The final image is formed by demosaicking these color channels, and transforming the interpolated image to a color space suitable for display. There are multiple stages in this imaging pipeline; several of these stages are nonlinear. The effect of these imaging pipeline stages on image noise is complex. In this project we will study the propagation of noise in the imaging pipeline via simulations in ISET. Some specific questions we'd like to address are: a) the effect of the order of image processing operations on visible noise in the final image, b) the improvement offered by simultaneously performing some imaging pipeline operations (e.g., joint demosaicking and denoising).
| |
| <br> '''Project consultants:''' Manu Parmar and Steve Lansel
| |
| | |
| | |
| === Resolution in color filter array images ===
| |
| | |
| The many megapixels available on modern imaging sensors offer the opportunity to trade-off spatial resolution for other desirable measurements. For instance, a color filter array with more than 3 color filters may offer improved color reproduction and the ability to render scenes under arbitrary illuminants. It is important to understand the real resolution trade-off in such schemes. In this project we will address this issue via simulations in ISET. We will consider the effect on final image resolution of some novel image acquisition schemes (e.g., interleaved imaging) by considering the full imaging pipeline (imaging lens, pixel size, color filter efficiencies, etc.).
| |
| <br> '''Project consultants:''' Manu Parmar, Steve Lansel and Brian Wandell
| |
| | |
| | |
| === Color balancing pipeline ===
| |
| | |
| If displayed without any processing, the raw image data acquired under different illuminants will appear to have an unnatural color cast. Images taken under tungsten illumination will appear too yellow; images under fluorescent illumination generally appear too green. Color balancing algorithms are designed to correct these images, transforming the raw data such that the unwanted color cast is eliminated. These images appear more correct to human viewers because the human visual system also performs a color balancing transformation as we move between illumination conditions. Despite work at Stanford on this problem for nearly three decades, there is no integrated suite of software tools for color balancing algorithms. This could be the year that you help us fix this problem.
| |
| <br> '''Project consultants:''' Joyce Farrell, Jeff DiCarlo and Brian Wandell
| |
| | |
| | |
| === Surfaces, lights and cameras: A web database ===
| |
| There are a number of online resources for surface reflectances, illuminants, and digital camera sensors (see below). Each of the existing databases have some strengths and weaknesses. We would you to design a web-database for surfaces, illuminants and camera sensors that improves upon the current set of pages. One improvement would be to offer some functionality. For example, suppose a user has a camera with a known sensor spectral sensitivity and a known light source – could you tell the user which surface reflectance functions in the database could have generated specific RGB values? Suppose the person took a picture of a wall with a flash; could you provide an estimate of the paint reflectance function on the wall, or possibly the name of the paint? Could the site help users generate test targets that help evaluate camera accuracy in different environments, such as a chart made of natural reflectances, or paint reflectances, or automotive reflectances, etc.? The web-site should have a nice user-interface, some back-end functionality for simple computations, and a way for users to volunteer new datasets.
| |
| http://www.cs.sfu.ca/~colour/data/colour_constancy_synthetic_test_data/index.html
| |
| ftp://ftp.eos.ncsu.edu/pub/eos/pub/spectra/
| |
| http://www.cs.utah.edu/~bes/graphics/spectra/
| |
| http://www1.cs.columbia.edu/CAVE/databases/
| |
| http://www.graphics.cornell.edu/online/measurements/
| |
| <br> '''Project consultants: Joyce Farrell and Janice Chen'''
| |
| | |
| | |
| === Camera image quality judgments ===
| |
| The ISET camera simulator was designed so that engineers can simulate properties of imaging sensors and visualize and quantify image quality. This project uses ISET to determine the effect that different optical, sensor and image processing properties have upon perceived image quality. Image metrics will include sharpness, color accuracy and noise visibility. These properties will be evaluated using color test charts, including the Macbeth ColorChecker and others, 2) the ISO 12233 slanted edge metric, and 3) various measures of image SNR, such as Minimum Photometric Exposure (30). The project will include informal preference ratings in which peoples’ judgments of the simulated images are compared with these metrics.
| |
| <br> '''Project consultants:''' Joyce Farrell and Jiajing Yu
| |
| | |
| | |
| === Removing haze from aerial photographs ===
| |
| The image quality of high resolution images captured at high altitudes is degraded by atmospheric haze. This project will consider the design of new imaging systems to estimate and remove the contribution of haze at each pixel in the high resolution image. One idea is to simultaneously capture a high resolution aerial image and multiple low resolution polarized aerial images. The project team will collaborate on the design a camera rig to take the polarized and non-polarized shots. This rig will then be placed in a plane to capture the aerial images. Given the data, consider how to use these multiple images to estimate and subtract the haze signal from a non-polarized high resolution imager with little loss of sensitivity. (Previous attempts to remove atmospheric haze can be found at: Fattal , Schechner et al and Tan )
| |
| <br> '''Project consultant:''' Iain Mcclatchie [iainm@google.com]
| |
| | |
| | |
| === Displays, gamuts and gamut transformations ===
| |
| Projection displays use different rendering methods depending on the image content. Text and graphics are displayed at higher luminance levels but with smaller colorgamuts. Video images are displayed using the widest possible gamut, but this reduces the overall brightness. This project will analyze the measured color gamuts already measured for different projection displays in different rendering modes. We will investigate the relationship between color gamuts, image content and perceived image quality.
| |
| <br> '''Project consultants:''' Joyce Farrell, Louis Silverstei and Karl Lang
| |
| | |
| | |
| === Tracking individually marked ants ===
| |
| A colony of ants exhibits coordinated behavior that is based on individual based rules without central control. In addition, not all ants are the same. Some ants are lazy,others very busy, some are jacks of all trades and others are masters of one. To examine how individual variation in ants contributes to the overall organization of colony behavior we will use paint marks to individually identify and track the behavior of all ants in a colony. The project proposed for this class is to: 1. Predict the camera rgb values given the spectral sensitivity of the camera, the spectral power of the light, and the spectral reflectance of objects (paints) in the scene, to determine the most discriminable colors and color combinations that should be used for tagging the ants. 2. Develop an algorithm that identifies each individual ant based on her color code in each frame of a video sequence.
| |
| <br> '''Project consultants:''' Joyce Farrel and, Noa Pinter-Wollman (Biology Department)
| |
| | |
| == Write-up Guidelines (Templates) ==
| |
| | |
| The purpose of the writeup is to document the methods, results, and conclusions of your class project.
| |
| | |
| If your project involved writing any non-trivial source code or processing scripts, you should make this available. Be sure to describe the purpose of your code and if possible, edit the code for clarity. The purpose of placing the code online is to allow others to verify your methods and to learn from your ideas.
| |
| | |
| You may include your in-class presentation slides as part of your writeup, but this should not be the entire writeup, since much of your presentation's information is not on your slides, and will come from what you say.
| |
| | |
| Projects at the minimum should contain the following:
| |
| | |
| | |
| Introduction Motivate the problem. Describe what has been done in the past.
| |
| What is the problem? What have people tried?
| |
| Methods Describe techniques used to measure data and/or source code algorithms.
| |
| Measure something? How? Develop code? What utilities/algorithms did you use?
| |
| Results Show relevant graphs and/or images. Explain them
| |
| Conclusions Describe what you learned.
| |
| What worked? What didn't? Why? What should someone next year try?
| |
| References List all references. Include links if papers where found online.
| |
| Appendix I Link in all source code, test images, etc, and give a description of each link.
| |
| | |
| In some cases, your acquired data may be too large to store practically. In this case, use your judgement (or consult one of us) and only link the most relevant data.
| |
| Appendix II
| |
| (for groups only) Work breakdown. Explain how the project work was divided among group members.
| |
| | |
| == Project Archives ==
| |
| | |
| There is an [http://scien.stanford.edu/labsite/scien_past_projects.php archive for SCIEN-related courses] on the [http://scien.stanford.edu SCIEN] machine in [http://ee.stanford.edu Electrical Engineering]. The archive contains projects from several different classes (EE 398A/B, EE 368, EE392J) and more than a decade of projects from Psych 221 (also known as EE 362).
| |
| | |
| Links to Psych 221 projects from the last few years are listed below.
| |
| | |
| <ul>
| |
| <li> [http://scien.stanford.edu/class/psych221/projects/09/index.htm Projects 2008-09] </li>
| |
| <li> [http://scien.stanford.edu/class/psych221/projects/08/index.htm Projects 2007-08] </li>
| |
| <li> [http://scien.stanford.edu/class/psych221/projects/07/index.htm Projects 2006-07] </li>
| |
| <li> [http://scien.stanford.edu/class/psych221/projects/06/index.htm Projects 2005-06] </li>
| |
| <li> [http://scien.stanford.edu/class/psych221/projects/05/index.htm Projects 2004-05] </li>
| |
| </ul>
| |
| | |
| = Administering This Site (CAs) =
| |
| | |
| How students get their accounts and passwords - we assign them in class.
| |
| | |
| How we remove accounts at the end of the time - we delete them after class is over. The wiki pages stay up, though.
| |
| | |
| Who does the site backup? Some combination of martin, michael, bob?
| |
| | |
| Who has Bureaucrat/Sysop status on this page? Brian, Jon, Bob
| |