Home → Final Project → Overview

ME 295 - Final Project Web Site
Overview
Directory & File Organization

Your final project must be documented and presented on the Web via a set of web pages explaining your simulation and providing illustrations of your input and output along with the text of your simulation program.

The organization and content of the web pages should be as follows:

Directory    
public_html    
  project    
    index.html  

This is your Final Project Home Page. It contains:

  • a short (1 paragraph) description of your project,
  • 1-2 images depicting the important physical objects of the project,
  • your name & contact information (Including email), and
  • links to all of the other pages within your web site.

This home page is within the main project directory, so you can use the navigation & page templates discussed in the last web tutorial, but you'll have to manually change all of the links for this page only. We'll include a link here (Coming soon), to a job aid describing how you can make these changes.

    Directory File Name Description
    cv    
      cv.html Your resume goes here.
    proe    
      proe.html

This page explains the model, how you made it, and how you assembled it.
      drawing.html All ProEngineer drawing images.
      model.html

This file includes snapshots of the model, each part and the full assembly.

    labview    
      labview.html

This page begins with a description of the labview: how it runs, what everything means, etc. It will also contain front and internal panels. Click here for a job aid on how to take snapshots of labview windows via the import command.

    physics    
      physics.html This page contains a STATEMENT of the problem: a description.
      analysis.html

This page will contain all free body diagrams that you scan in, as well as equations, boundary conditions and figures. You must include a full description of how the solution was obtained.

      solution.html This page displays the function that solves the problem statement in physics.html, along with a full description of the solution algorithm.
    server    
      server.html

This page contains the server code, fully commented. But at the TOP, put the word description, and link it to another page in this directory called server_description.html, which is described below.
      server_description.html

This page contains:

  • a description of the variables and
  • a full description of structures defined within the code, along with
  • a description of how the code runs.
    viewer    
      viewer.html

This web page simply lists the inventor code, fully commented. But at the TOP of the page, just above the inventor code, include the word description. Link description to the page described below, viewer_description.html.

In addition, there should be a second link at
the BOTTOM of the viewer code to another page within this directory called images.html. This page is described underneath viewer_description.html.

      viewer_description.html

This page explains the details of the code, above and beyond the in-line comments. It should include:

  • a description of the variables,
  • a full description of structures defined within the code, and
  • a description of how the code runs.
      images.html This page should contain snapshots of the viewer code and the gview with some nodes shown. You can get these snapshots using the import command.
    network    
      network.html This page contains the network code, plus links to labview_server and viewer_server code files, and information about network connections.
      labview_server.html  
      viewer_server.html  
    personal    
      personal.html

Personal thoughts on obstacles and how they resolved and what you learned from the sequence:

  • Tom Johnstons course, through
  • C programming (ME290) through
  • this course, ME295.

Keep in mind that you should include everything you learned in class; some of you have worked with Dr. Impelluso one-on-one and discovered errors.

Others have worked with Dr. Impelluso when he inserted flags to avoid compilation of certain sections of code. A number of you have also worked with Dr. Impelluso to debug the viewer and server code.

All of this should be documented and included in this web page. It is essentially an area for you to include all comments on this and your other related computer classes.

    source  

This will contain 3 directories:
       
  • labview
  • server
  • viewer

Corresponding source code files go into each of the directories, and there is a README file in the source directory describes how the code files in each directory are to be compiled and run.

Dr Impelluso will explain how to create a tar file of the source directory so that interested visitors to your page can download, compile and run your simulation.

In order to construct your web site, you'll find a series of Job Aids that should help step you through some most of what you'll need to do in order to use Mozilla composer. You'll find separate Job Aids for

Contact Web Designer