CompVision

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

<p> The vision group webpage is managed with a SVN repository, so changes should not be made to the webpage directly. </p> <h2>Checking out the repo</h2> <div class="level2"> <p> To get a copy of the repository, simply run the command: </p> <pre class="file"> svn co https://svn.ics.uci.edu/titans/visionweb/ </pre><p> </p> <p> You'll then be prompted for a password against your current username. If this is not the same as your ICS username, then simply push enter and you'll get a prompt for a username. Enter in your ICS username then password and you'll begin getting a copying the repo. </p> </div> <h2>Updating content</h2> <div class="level2"> <p> Now that you have a copy of the repository, you should take a look at the README file located in “public_html/scripts/” to make sure your system has the prerequisite applications and libraries, before trying to make changes to the website. The webpage is semi-static in that the contents are served from static pages, but the pages themselves were dynamically generated by python scripts and xml files. Documented below are the most common changes you'd likely want to make to the webpage. </p> </div> <h4>Adding People</h4> <div class="level4"> <p> To add a person to the webpage, you'll need to do two things: (1) add a profile photo and (2) add an entry to the person database. </p> <p> (1) Before adding the photo, it should be cropped/resized to 200×250 for optimal display and named using the convention: firstname_lastname.jpg. To add the photo, copy the file to “public_html/images/mugshots/” (2) To add an entry to the person database, you'll want to edit peoplelist.xml located in “public_html/scripts/”. At the top of the file, you'll find a template that's commented out, which you can copy and add the new person with. The fields are hopefully self-explanatory, if not see other people entries as examples. </p> </div> <h4>Adding Projects</h4> <div class="level4"> <p> To add a new project to the webpage, you'll want to edit projectlist.xml located in “public_html/scripts/”. </p> </div> <h4>Adding Papers</h4> <div class="level4"> <p> The naming convention for papers is to use the first author's last name appended with the first letter of the other authors (e.g., FowlkesMM for Fowlkes, Martin, and Malik) followed by the venue of publication and the publication year. All together it'll be like “FowlkesMM_CVPR_2003”. Henceforth, we'll use “name” to denote this notation. </p> <p> To add a new paper to the webpage, you'll want to create a directory inside “public_html/papers/” following the naming convention. Inside you'll add four files: abstract.html, icon.jpg, “name”.bibtex, and “name”.pdf. </p> <p> abstract.html should contain only text or HTML code that is intended to go inside the &lt;body>&lt;/body> of a HTML file. icon.jpg is a small picture related to the paper. “name”.bibtex is the bibtex file for the paper. “name”.pdf is the pdf of the paper. </p> </div> <h2>Regenerate the static pages</h2> <div class="level2"> <p> When you're done making changes, you can regenerate all static pages by running the following command: </p> <pre class="code">python gen.py all </pre><p> </p> <p> If you see errors when running the script, feel free to try to fix them yourself or bug Bailey. </p> </div> <h2>Commit your changes</h2> <div class="level2"> <p> When you are satisfied that everything looks good, check your updates back in to svn. You should go back to the top folder "public_html" to see all changes, then “svn add” any new files or directories you have added or changed to the tree. </p> </div> <h2>Updating the live site</h2> <div class="level2"> <p> Finally, pull the updates from svn to the hosted directory. </p> <pre class="code">gsu vision cd /extra/vision0 svn export --force https://svn.ics.uci.edu/titans/visionweb/public_html/ find public_html/ -type f -print -exec chmod a+r {} \; find public_html/ -type d -print -exec chmod a+rx {} \; chmod 644 .htaccess </pre><p> </p> <p> The final step will eventually be automated but for now just email Charless :) </p> </div>