- Exam/Homework/Reading
Assignments:
- HW 01 Designing McCulloch neuron; Perl installation (posted 01.26.07)
- HW 02 Perceptron, hard/soft activation functions, delta rule (posted 02.26.07)
- Solution covered in class (see the lecture slides).
- Exam #1 Preparatory examples (posted 03.19.07)
- HW 03 Feedforward bipolar network design, NNOTT (posted 04.02.07)
- These are some of your solutions (names are removed). Some solutions are better than others, but it is important to note different approaches (1, 2, 3, 4, 5, 6, 7).
- HW 04 AD converter, fuzzy logic (posted 04.11.07)
- Solution pdf (some of your solutions, not necessearly awarded with full credit 1, 2, 3, 4).
- Preparatory examples for final exam (posted 04.23.07)
- Final Exam (posted 05.08.07)
- Exam solution pdf (some of your exemplary solutions 1, 2, 3)
Before you send me an email, please check
the FAQs (your answer might already be there).
Paper:
- Paper topic: Neural networks are known by their inherent ability to deal with wide range of problems, such as classification, prediction, approximation, even when the outcome is not known. ECE students may be interested in circuit implementation of certain neural architecture. Ecohydraulics students may be interested in specific modeling, classification, prediction (watershed, etc.). You may want to do a preliminary literature search first.
- Type of paper: Required paper can have more of a research (theoretical) or more of a project (applicative) flavor.
- Format: Formatting should be according to an IEEE conference guidelines. It should be composed of title, abstract, introduction, problem definition, proposed solution, experimental/testing, conclusion, and future directions.
Some examples are:
- IEEE Computer Soc. Publishing Forms page (see Formatting Instructions);
- IEEE Author Tools page with Template for IEEE Transactions with template in MS Word or pdf format and WIN and MAC Bibilography file.
- Submission: Please follow these rules when submitting your paper:
- Please compile all your results into a single file!
- In email, use the proper subject line and signature as stated in course web page.
- Include the same signature on every page of your assignment.
- Use the following convention for naming the file: " HWnn_Family_name.xxx ", nn being the homework number.
- General tip: After you choose a problem, give a problem definition on a general level first. Then decompose it to feasible components and tackle one after another. In other words, put some boundaries on a problem and keep it reasonably difficult for a given deadline.
- Teaming up: If you are a member of a team, first select a project manager for your team. He or she will be submitting paper drafts and questions for all of you. He or she will also be cc-ing to all of the members of your team. Hence, when I reply I will be replying to all. Paper title page will contain all the team members names, as well as the detailed description of division of work in team (who is doing what).
Outreach students: Outreach students are encouraged to team up with other outreach students or students taking the course live/cv. Though EO students can assume deadlines 10 days longer than the ones posted below, I would encourage to use the same final submission date. This way, your teammates can present your papers during the last session of the course.
- First draft due: February 19, 2007.
- Deliverable: brief outline, up to one page long. It should include: working title, author contact info, short abstract, and brief problem description.
- Formatting: at this point, your deliverable should look like an abstract you would submit to an IEEE conference.
- Initial proposal should be a brief description - what do you see as a problem worth solving followed by how you would approach it. I would be happy to guide you or advise you.
- I am hesitant to force you into a list of topics – I would rather see you coming up with something in the line of your current project problems, something you would be interested in working on. I will be happy to discuss topics with you - feel free to contact me anytime.
- Second draft due: March 26, 2007.
- Deliverable: final title, author contact info, short abstract, introduction, problem description, proposed steps towards solution (solution can be included, if ready).
- Formatting: you are going towards an IEEE paper, so the formatting applies accordingly.
- This will be a more elaborate paper, but not more than 5-6 pages long. It should contain detailed problem description as well as a survey of existing solutions (referenced - you may want to do a literature search first). It should contain steps towards the solution. At this point a detailed solution, experiments, etc. do not need to be done yet.
- Division of work in team: please clearly state the division of work within a team (the work performed by each team member).
- Final submission: April 23, 2007.
- Deliverables:
- Final, complete paper, up to ten pages. It should contain detailed solution and experimental work. You may include test examples (learning & test patterns), architecture description, discussion on robustness of your solution. You should also include future work directions, problems that you may want to tackle in next paper.
- Please submit copies of papers/books used in your research.
- Please name your file like this: FamilyName_Paper_xxxx.xxx and FamilyName_Presentation_xxxx.xxx
- Presentations: last week of the course (April 30, 2007).
- Each of you will present your project and we will all discuss it. You should use this discussion to finalize your project paper and hopefully publish it at some conference.
- Presentation: please limit your presentation to 10min+5min for discussion. Along with final version you should email me your slides so I can post them on our course web page. This way others will be able to read about your project and prepare questions. Please print out all project papers & presentations before coming to the final session.
- Paper topic - some ideas
- These are some of the topics of papers from previous years. These will give you some examples of what applications can be targeted.
- Pattern recognition
- Pattern Recognition and Conversion of Japanese Hiragana to Roman Characters
- Using Neural Networks to Identify Disordered Regions for Protein Alignments
- An Experiment To See If Hopfield Networks Can Be Used in Handwritten Digit OCR
- Artificial Neural Network For Automated Prediction of Popularity of Digitized Images
- Pattern Classification
Of Numericals
By
Neural Networks
- Pattern recognition using Hopfield associative memories
- Feedforward ANN for bipolar pattern recognition
- Clustering
- Good Vibrations: Investigating Neural Network Applications in
Prognostics of Jet Engine Ball Bearings
- Single Neuron Classification of Non-Linearly Separable Data
- GA
- Evolving Neural Networks Using Particle Swarms
- CBAC Optimization for Artificial Neural Network (Cluster Based Averaged Crossover to converge in Particle swarm time)
- ECE problems
- Implementing the 2-bit A/D Converter using the Counterpropagation Networks
- A Study of Advancements Made in Circuit Efficiency Using Threshold Logic
- An Artificial Neural Network Approach for Detecting High-Impedance Faults on Three Phase Four-Wire Distribution Circuits
- Neural protective relay for a circuit breaker.
- HDL modeling of neural networks
- IDS
- Artificial Neural Networks for Intrusion Detection
- CE/ME problems
- Bed Load Sediment Transport Estimation Using Artificial Neural Networks
- Use of Artificial Neural Networks (ANN) in a Stream flow Prediction
- Implementing a Neural Network System to Solve the Inverse Kinematics of a Biologically Inspired Robotic Cat Leg
- Neural Network Application In Engineering Principle
- Biodiesel Blend Level Sensing from the Ultraviolet Absorption Spectra with Application
of Neural Network
- Intelligent controllers
- Road recognition for an autonomous vehicle
- Control of Underwater Autonomous Vehicles Using
Neural Networks
Final
Information:
- Course web sites will be closed:
- Husky class site will be closed after the semester is officially
over. I will be granting temporary permissions upon the request.
|