<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ArashLari</id>
		<title>LMU BioDB 2017 - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://xmlpipedb.lmucs.io/biodb/fall2017/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ArashLari"/>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php/Special:Contributions/ArashLari"/>
		<updated>2026-06-21T20:03:08Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.29.0</generator>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=5776</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=5776"/>
				<updated>2017-12-15T06:44:30Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Week 14 Team Progress Reflections */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Deliverables Page==&lt;br /&gt;
&lt;br /&gt;
[[Page Desiigner Deliverables Page]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Pagedesignprototype.zip]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:BiodbPageDesignFinalPresentation_.pptx]] &lt;br /&gt;
&lt;br /&gt;
==Page Layout==&lt;br /&gt;
*&amp;lt;code&amp;gt;Below are a series of rough ideas we will use to create the layout of the page&amp;lt;/code&amp;gt;&lt;br /&gt;
[[File:ACT1screenshot.png|500px]]&lt;br /&gt;
*We will be using a layout similar to the ACT1 gene page.&lt;br /&gt;
[[File:Sketchofpagedesign.png]]&lt;br /&gt;
*This is a rough sketch of what the page will look like.&lt;br /&gt;
*The section labeled &amp;#039;&amp;#039;&amp;#039;description&amp;#039;&amp;#039;&amp;#039; on the sketch will include the following:&lt;br /&gt;
**Gene ID from each database&lt;br /&gt;
**Description/Function (ensembl)&lt;br /&gt;
*Within the dropdown menus we will be incorporating the following:&lt;br /&gt;
**DNA Sequence (ensembl)&lt;br /&gt;
**Protein Sequence (UniProt)&lt;br /&gt;
**Locus tag (NCBI)&lt;br /&gt;
**Also Known As (NCBI)&lt;br /&gt;
**Consensus Sequence (JASPAR)&lt;br /&gt;
**Regulation (SGD)&lt;br /&gt;
**Interaction (SGD)&lt;br /&gt;
**Similar Proteins (UniProt)&lt;br /&gt;
**Gene Ontology (SGD)&lt;br /&gt;
**JASPAR&lt;br /&gt;
***Matrix ID &lt;br /&gt;
***Class Heat shock factors&lt;br /&gt;
***Family HSF factors&lt;br /&gt;
***Sequence Logo &lt;br /&gt;
***Frequency Matrix&lt;br /&gt;
*A zip file containing the html file of prototype page can be downloaded by clicking the &amp;lt;code&amp;gt;pagedesignprototype.zip&amp;lt;/code&amp;gt; link below.&lt;br /&gt;
[[File:Pagedesignprototype.zip]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Journal Club Presentations==&lt;br /&gt;
===Powerpoint Slides and Respective Articles===&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
*Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12] | Arash Lari Week 12]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
Because Arash and I presented last week, we didn&amp;#039;t have a heavy work load this week. Arash explained a lot of technical things to me, and we completed the first coding milestones and talked about design possibilities. I officially have a GitHub (nicolekal). I also downloaded the software I needed but didn&amp;#039;t have onto my laptop. A full update can be found on: [[Nicolekalcic Week 12] | Nicole Kalcic Week 12]. [[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 23:45, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 14]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week I worked on implementing our designs for the web page. Nicole and Hayden helped come up with some design ideas. We ended up deciding that ACT1 was a very well designed page and that it would be best to follow the format of that page. There&amp;#039;s only a few things left to do but our portion of the project is nearly complete, the generic version of every gene&amp;#039;s page needs just a few finishing touches. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 18:19, 4 December 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I finished the Week 10 assignment, using YEASTRACT and GRNsight. I specifically chose one profile from the STEM results to use in YEASTRACT to find transcription factors that regulate a cluster of genes. First I uploaded the genes from profile #22 into YEASTRACT to find 20 significant transcription factors that regulate them. Then, I used Excel to get rid of the transcription factors that were not related to other transcription factors. Once I had those, I imported them into GRNsight to create a map of the transcription factors and their relations to each other. I took a screenshot of this map and uploaded it to my [[mbalducc Week 14| Week 14]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:14, 4 December 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I served as a &amp;quot;floater&amp;quot;. I worked with Nicole and Arash in order to come up with how the page design prototype would look. We decided to use the ACT1 design along with Nicole&amp;#039;s sketch in order to find a balance between aesthetic and function. The design we used is downloadable from this page and my [[hhinsch Week 14]] page. My [[hhinsch Week 14]] page has some more information regarding why we chose our current prototype design. I also spoke with Mary to make sure she knew I was there to help with her deliverables if needed. I also spent time with the other QA&amp;#039;s this week in order to familiarize myself with the deliverables of the other groups. This was necessary for me to make sure we added everything to the page that is required. I uploaded images to my [hhinsch Week 14]] page as well as this page in order to further clarify our thought process behind the page prototype. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 20:16, 4 December 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think we all got a better grasp of the assignment and time management for the assignment. We have a clear idea where we&amp;#039;re headed.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* I wish we had more time to dedicate to this class, as often our schedules don&amp;#039;t line up. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*We&amp;#039;ll try to be more proactive about all our tasks so they don&amp;#039;t pile up. I&amp;#039;m planning on starting some work during the thanksgiving break to lighten the load afterwards.&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*Arash and I communicated via text and had a better idea of what we needed to do earlier on in the week, which made it easier to progress and do quality, time efficient work. &lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*We weren&amp;#039;t all able to meet in person. I don&amp;#039;t know if this was a huge issue this week, but scheduling conflicts might become more of a problem in December. &lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try to make plans with the group on Tuesday. I am assuming everyone is going out of town for Thanksgiving, but perhaps we can make certain dates within the week to have things done by so the rest of the group can look over the work.&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*This week we were a little more prepared to work together and complete the deliverables. As time goes by the end goal is becoming more apparent.&lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*I spent a lot of time reading the article multiple times and it is still a bit confusing to me. A lot of the vocabulary wasn&amp;#039;t even found in the dictionaries we provided and a lot of the information needed a lot of background knowledge to comprehend.&lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try and do the bulk of the assignment earlier in the week rather than on the weekend, so I may have more time to understand the material.[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 21:09, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 14]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* Our design idea turned out pretty nicely, and was not that difficult to implement.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Coming up with what the final aesthetics will look like.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* We will discuss the matter in class with the professors and our fellow students to see what works best for everyone.&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
#What worked?&lt;br /&gt;
#*Using YEASTRACT, Excel, and GRNsight to create a map of significant transcription factors in the profile I chose.&lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*I have not fixed Weeks 8 and 10 as much as I would have wanted to.&lt;br /&gt;
#What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Take more time, make sure I do things right the first time so I don&amp;#039;t have to back and fix them later.&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We did a pretty good job getting everything done we needed to get done this week in a timely fashion while dealing with adversity.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* We still need to complete the prototype and add the other groups&amp;#039; deliverables to our page.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* We just simply need to take a final assessment of the deliverables as well as gather feedback from the entire class regarding the final layout of the page.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We completed the basic structure of the page, and everyone was able to finish their work in time despite my absence on Thursday. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* We haven&amp;#039;t finalized anything yet, or implemented any information into the page. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* We will talk with everyone in class, including the Dahlquist and Dionisio in order to make final decisions moving into Week 15. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 15]] Team Progress Reflections===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week I worked on adding the finishing touches to our info.html file in order to make the information easier to digest and nicer to look at. I also worked on my parts of the group presentation and report, which basically entailed me writing out, in detail, everything I did for the GRNsight project. I also wrote an individual statement of work that I emailed to the professors.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 22:44, 14 December 2017 (PST)&lt;br /&gt;
[[ArashLari_Week_15|ArashLari Week 15]]&lt;br /&gt;
====Hayden====&lt;br /&gt;
====Mary====&lt;br /&gt;
====Nicole====&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=5775</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=5775"/>
				<updated>2017-12-15T06:41:54Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Week 14 Team Progress Reflections */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Deliverables Page==&lt;br /&gt;
&lt;br /&gt;
[[Page Desiigner Deliverables Page]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Pagedesignprototype.zip]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:BiodbPageDesignFinalPresentation_.pptx]] &lt;br /&gt;
&lt;br /&gt;
==Page Layout==&lt;br /&gt;
*&amp;lt;code&amp;gt;Below are a series of rough ideas we will use to create the layout of the page&amp;lt;/code&amp;gt;&lt;br /&gt;
[[File:ACT1screenshot.png|500px]]&lt;br /&gt;
*We will be using a layout similar to the ACT1 gene page.&lt;br /&gt;
[[File:Sketchofpagedesign.png]]&lt;br /&gt;
*This is a rough sketch of what the page will look like.&lt;br /&gt;
*The section labeled &amp;#039;&amp;#039;&amp;#039;description&amp;#039;&amp;#039;&amp;#039; on the sketch will include the following:&lt;br /&gt;
**Gene ID from each database&lt;br /&gt;
**Description/Function (ensembl)&lt;br /&gt;
*Within the dropdown menus we will be incorporating the following:&lt;br /&gt;
**DNA Sequence (ensembl)&lt;br /&gt;
**Protein Sequence (UniProt)&lt;br /&gt;
**Locus tag (NCBI)&lt;br /&gt;
**Also Known As (NCBI)&lt;br /&gt;
**Consensus Sequence (JASPAR)&lt;br /&gt;
**Regulation (SGD)&lt;br /&gt;
**Interaction (SGD)&lt;br /&gt;
**Similar Proteins (UniProt)&lt;br /&gt;
**Gene Ontology (SGD)&lt;br /&gt;
**JASPAR&lt;br /&gt;
***Matrix ID &lt;br /&gt;
***Class Heat shock factors&lt;br /&gt;
***Family HSF factors&lt;br /&gt;
***Sequence Logo &lt;br /&gt;
***Frequency Matrix&lt;br /&gt;
*A zip file containing the html file of prototype page can be downloaded by clicking the &amp;lt;code&amp;gt;pagedesignprototype.zip&amp;lt;/code&amp;gt; link below.&lt;br /&gt;
[[File:Pagedesignprototype.zip]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Journal Club Presentations==&lt;br /&gt;
===Powerpoint Slides and Respective Articles===&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
*Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12] | Arash Lari Week 12]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
Because Arash and I presented last week, we didn&amp;#039;t have a heavy work load this week. Arash explained a lot of technical things to me, and we completed the first coding milestones and talked about design possibilities. I officially have a GitHub (nicolekal). I also downloaded the software I needed but didn&amp;#039;t have onto my laptop. A full update can be found on: [[Nicolekalcic Week 12] | Nicole Kalcic Week 12]. [[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 23:45, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 14]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week I worked on implementing our designs for the web page. Nicole and Hayden helped come up with some design ideas. We ended up deciding that ACT1 was a very well designed page and that it would be best to follow the format of that page. There&amp;#039;s only a few things left to do but our portion of the project is nearly complete, the generic version of every gene&amp;#039;s page needs just a few finishing touches. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 18:19, 4 December 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I finished the Week 10 assignment, using YEASTRACT and GRNsight. I specifically chose one profile from the STEM results to use in YEASTRACT to find transcription factors that regulate a cluster of genes. First I uploaded the genes from profile #22 into YEASTRACT to find 20 significant transcription factors that regulate them. Then, I used Excel to get rid of the transcription factors that were not related to other transcription factors. Once I had those, I imported them into GRNsight to create a map of the transcription factors and their relations to each other. I took a screenshot of this map and uploaded it to my [[mbalducc Week 14| Week 14]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:14, 4 December 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I served as a &amp;quot;floater&amp;quot;. I worked with Nicole and Arash in order to come up with how the page design prototype would look. We decided to use the ACT1 design along with Nicole&amp;#039;s sketch in order to find a balance between aesthetic and function. The design we used is downloadable from this page and my [[hhinsch Week 14]] page. My [[hhinsch Week 14]] page has some more information regarding why we chose our current prototype design. I also spoke with Mary to make sure she knew I was there to help with her deliverables if needed. I also spent time with the other QA&amp;#039;s this week in order to familiarize myself with the deliverables of the other groups. This was necessary for me to make sure we added everything to the page that is required. I uploaded images to my [hhinsch Week 14]] page as well as this page in order to further clarify our thought process behind the page prototype. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 20:16, 4 December 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think we all got a better grasp of the assignment and time management for the assignment. We have a clear idea where we&amp;#039;re headed.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* I wish we had more time to dedicate to this class, as often our schedules don&amp;#039;t line up. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*We&amp;#039;ll try to be more proactive about all our tasks so they don&amp;#039;t pile up. I&amp;#039;m planning on starting some work during the thanksgiving break to lighten the load afterwards.&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*Arash and I communicated via text and had a better idea of what we needed to do earlier on in the week, which made it easier to progress and do quality, time efficient work. &lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*We weren&amp;#039;t all able to meet in person. I don&amp;#039;t know if this was a huge issue this week, but scheduling conflicts might become more of a problem in December. &lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try to make plans with the group on Tuesday. I am assuming everyone is going out of town for Thanksgiving, but perhaps we can make certain dates within the week to have things done by so the rest of the group can look over the work.&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*This week we were a little more prepared to work together and complete the deliverables. As time goes by the end goal is becoming more apparent.&lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*I spent a lot of time reading the article multiple times and it is still a bit confusing to me. A lot of the vocabulary wasn&amp;#039;t even found in the dictionaries we provided and a lot of the information needed a lot of background knowledge to comprehend.&lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try and do the bulk of the assignment earlier in the week rather than on the weekend, so I may have more time to understand the material.[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 21:09, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 14]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* Our design idea turned out pretty nicely, and was not that difficult to implement.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Coming up with what the final aesthetics will look like.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* We will discuss the matter in class with the professors and our fellow students to see what works best for everyone.&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
#What worked?&lt;br /&gt;
#*Using YEASTRACT, Excel, and GRNsight to create a map of significant transcription factors in the profile I chose.&lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*I have not fixed Weeks 8 and 10 as much as I would have wanted to.&lt;br /&gt;
#What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Take more time, make sure I do things right the first time so I don&amp;#039;t have to back and fix them later.&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We did a pretty good job getting everything done we needed to get done this week in a timely fashion while dealing with adversity.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* We still need to complete the prototype and add the other groups&amp;#039; deliverables to our page.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* We just simply need to take a final assessment of the deliverables as well as gather feedback from the entire class regarding the final layout of the page.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We completed the basic structure of the page, and everyone was able to finish their work in time despite my absence on Thursday. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* We haven&amp;#039;t finalized anything yet, or implemented any information into the page. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* We will talk with everyone in class, including the Dahlquist and Dionisio in order to make final decisions moving into Week 15. &lt;br /&gt;
{{Pagedesiigner}}&lt;br /&gt;
&lt;br /&gt;
===[[Week 15] Team Progress Reflections===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week I worked on adding the finishing touches to our info.html file in order to make the information easier to digest and nicer to look at. I also worked on my parts of the group presentation and report, which basically entailed me writing out, in detail, everything I did for the GRNsight project. I also wrote an individual statement of work that I emailed to the professors.&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Class_Journal_Week_15&amp;diff=5774</id>
		<title>Class Journal Week 15</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Class_Journal_Week_15&amp;diff=5774"/>
				<updated>2017-12-15T06:38:53Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: Created page with &amp;quot;= Electronic Lab Notebook =  * This week was the week where we finalized our contributions * I finished the styling of the page, and detailed out the process in our group repo...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Lab Notebook =&lt;br /&gt;
&lt;br /&gt;
* This week was the week where we finalized our contributions&lt;br /&gt;
* I finished the styling of the page, and detailed out the process in our group report and our group presentation&lt;br /&gt;
* Our group made &amp;amp; gave our presentation&lt;br /&gt;
* Our group also worked on the report&lt;br /&gt;
** We kept in pretty regular contact to ensure we all did our parts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements and References = &lt;br /&gt;
* I worked with Nicole, Hayden, and Mary for our Page Desiigner Deliverables.&lt;br /&gt;
* While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
&lt;br /&gt;
=Journal Entry=&lt;br /&gt;
{{Template:ArashLari}}&lt;br /&gt;
*Group Projects: https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Page_Desiigner&lt;br /&gt;
*Team Name: Page Desiigner&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 22:38, 14 December 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=5354</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=5354"/>
				<updated>2017-12-05T02:21:45Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Team Progress Reflections */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
&lt;br /&gt;
==Page Layout==&lt;br /&gt;
*&amp;lt;code&amp;gt;Below are a series of rough ideas we will use to create the layout of the page&amp;lt;/code&amp;gt;&lt;br /&gt;
[[File:ACT1screenshot.png|500px]]&lt;br /&gt;
*We will be using a layout similar to the ACT1 gene page.&lt;br /&gt;
[[File:Sketchofpagedesign.png]]&lt;br /&gt;
*This is a rough sketch of what the page will look like.&lt;br /&gt;
*The section labeled &amp;#039;&amp;#039;&amp;#039;description&amp;#039;&amp;#039;&amp;#039; on the sketch will include the following:&lt;br /&gt;
**Gene ID from each database&lt;br /&gt;
**Description/Function (ensembl)&lt;br /&gt;
*Within the dropdown menus we will be incorporating the following:&lt;br /&gt;
**DNA Sequence (ensembl)&lt;br /&gt;
**Protein Sequence (UniProt)&lt;br /&gt;
**Locus tag (NCBI)&lt;br /&gt;
**Also Known As (NCBI)&lt;br /&gt;
**Consensus Sequence (JASPAR)&lt;br /&gt;
**Regulation (SGD)&lt;br /&gt;
**Interaction (SGD)&lt;br /&gt;
**Similar Proteins (UniProt)&lt;br /&gt;
**Gene Ontology (SGD)&lt;br /&gt;
**JASPAR&lt;br /&gt;
***Matrix ID &lt;br /&gt;
***Class Heat shock factors&lt;br /&gt;
***Family HSF factors&lt;br /&gt;
***Sequence Logo &lt;br /&gt;
***Frequency Matrix&lt;br /&gt;
&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Journal Club Presentations==&lt;br /&gt;
===Powerpoint Slides and Respective Articles===&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
*Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12] | Arash Lari Week 12]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
Because Arash and I presented last week, we didn&amp;#039;t have a heavy work load this week. Arash explained a lot of technical things to me, and we completed the first coding milestones and talked about design possibilities. I officially have a GitHub (nicolekal). I also downloaded the software I needed but didn&amp;#039;t have onto my laptop. A full update can be found on: [[Nicolekalcic Week 12] | Nicole Kalcic Week 12]. [[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 23:45, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 14]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week I worked on implementing our designs for the web page. Nicole and Hayden helped come up with some design ideas. We ended up deciding that ACT1 was a very well designed page and that it would be best to follow the format of that page. There&amp;#039;s only a few things left to do but our portion of the project is nearly complete, the generic version of every gene&amp;#039;s page needs just a few finishing touches. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 18:19, 4 December 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think we all got a better grasp of the assignment and time management for the assignment. We have a clear idea where we&amp;#039;re headed.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* I wish we had more time to dedicate to this class, as often our schedules don&amp;#039;t line up. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*We&amp;#039;ll try to be more proactive about all our tasks so they don&amp;#039;t pile up. I&amp;#039;m planning on starting some work during the thanksgiving break to lighten the load afterwards.&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*Arash and I communicated via text and had a better idea of what we needed to do earlier on in the week, which made it easier to progress and do quality, time efficient work. &lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*We weren&amp;#039;t all able to meet in person. I don&amp;#039;t know if this was a huge issue this week, but scheduling conflicts might become more of a problem in December. &lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try to make plans with the group on Tuesday. I am assuming everyone is going out of town for Thanksgiving, but perhaps we can make certain dates within the week to have things done by so the rest of the group can look over the work.&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*This week we were a little more prepared to work together and complete the deliverables. As time goes by the end goal is becoming more apparent.&lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*I spent a lot of time reading the article multiple times and it is still a bit confusing to me. A lot of the vocabulary wasn&amp;#039;t even found in the dictionaries we provided and a lot of the information needed a lot of background knowledge to comprehend.&lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try and do the bulk of the assignment earlier in the week rather than on the weekend, so I may have more time to understand the material.[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 21:09, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 14]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* Our design idea turned out pretty nicely, and was not that difficult to implement.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Coming up with what the final aesthetics will look like.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* We will discuss the matter in class with the professors and our fellow students to see what works best for everyone.&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=5353</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=5353"/>
				<updated>2017-12-05T02:19:34Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Executive Summaries */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
&lt;br /&gt;
==Page Layout==&lt;br /&gt;
*&amp;lt;code&amp;gt;Below are a series of rough ideas we will use to create the layout of the page&amp;lt;/code&amp;gt;&lt;br /&gt;
[[File:ACT1screenshot.png|500px]]&lt;br /&gt;
*We will be using a layout similar to the ACT1 gene page.&lt;br /&gt;
[[File:Sketchofpagedesign.png]]&lt;br /&gt;
*This is a rough sketch of what the page will look like.&lt;br /&gt;
*The section labeled &amp;#039;&amp;#039;&amp;#039;description&amp;#039;&amp;#039;&amp;#039; on the sketch will include the following:&lt;br /&gt;
**Gene ID from each database&lt;br /&gt;
**Description/Function (ensembl)&lt;br /&gt;
*Within the dropdown menus we will be incorporating the following:&lt;br /&gt;
**DNA Sequence (ensembl)&lt;br /&gt;
**Protein Sequence (UniProt)&lt;br /&gt;
**Locus tag (NCBI)&lt;br /&gt;
**Also Known As (NCBI)&lt;br /&gt;
**Consensus Sequence (JASPAR)&lt;br /&gt;
**Regulation (SGD)&lt;br /&gt;
**Interaction (SGD)&lt;br /&gt;
**Similar Proteins (UniProt)&lt;br /&gt;
**Gene Ontology (SGD)&lt;br /&gt;
**JASPAR&lt;br /&gt;
***Matrix ID &lt;br /&gt;
***Class Heat shock factors&lt;br /&gt;
***Family HSF factors&lt;br /&gt;
***Sequence Logo &lt;br /&gt;
***Frequency Matrix&lt;br /&gt;
&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Journal Club Presentations==&lt;br /&gt;
===Powerpoint Slides and Respective Articles===&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
*Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12] | Arash Lari Week 12]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
Because Arash and I presented last week, we didn&amp;#039;t have a heavy work load this week. Arash explained a lot of technical things to me, and we completed the first coding milestones and talked about design possibilities. I officially have a GitHub (nicolekal). I also downloaded the software I needed but didn&amp;#039;t have onto my laptop. A full update can be found on: [[Nicolekalcic Week 12] | Nicole Kalcic Week 12]. [[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 23:45, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 14]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week I worked on implementing our designs for the web page. Nicole and Hayden helped come up with some design ideas. We ended up deciding that ACT1 was a very well designed page and that it would be best to follow the format of that page. There&amp;#039;s only a few things left to do but our portion of the project is nearly complete, the generic version of every gene&amp;#039;s page needs just a few finishing touches. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 18:19, 4 December 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think we all got a better grasp of the assignment and time management for the assignment. We have a clear idea where we&amp;#039;re headed.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* I wish we had more time to dedicate to this class, as often our schedules don&amp;#039;t line up. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*We&amp;#039;ll try to be more proactive about all our tasks so they don&amp;#039;t pile up. I&amp;#039;m planning on starting some work during the thanksgiving break to lighten the load afterwards.&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*Arash and I communicated via text and had a better idea of what we needed to do earlier on in the week, which made it easier to progress and do quality, time efficient work. &lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*We weren&amp;#039;t all able to meet in person. I don&amp;#039;t know if this was a huge issue this week, but scheduling conflicts might become more of a problem in December. &lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try to make plans with the group on Tuesday. I am assuming everyone is going out of town for Thanksgiving, but perhaps we can make certain dates within the week to have things done by so the rest of the group can look over the work.&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*This week we were a little more prepared to work together and complete the deliverables. As time goes by the end goal is becoming more apparent.&lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*I spent a lot of time reading the article multiple times and it is still a bit confusing to me. A lot of the vocabulary wasn&amp;#039;t even found in the dictionaries we provided and a lot of the information needed a lot of background knowledge to comprehend.&lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try and do the bulk of the assignment earlier in the week rather than on the weekend, so I may have more time to understand the material.[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 21:09, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_14&amp;diff=5351</id>
		<title>ArashLari Week 14</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_14&amp;diff=5351"/>
				<updated>2017-12-05T02:15:26Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Acknowledgements and References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Lab Notebook =&lt;br /&gt;
&lt;br /&gt;
* This week we began moving towards the final design for the gene page for GRNSight.&lt;br /&gt;
* With some discussion and guidance from professors Dahlquist and Dionisio we came up with enough material for the integration team to not get slowed down&lt;br /&gt;
* Nicole drafted a rough design of what our page should look like, based off of the reception of ACT1, the rest of the team agreed with her design&lt;br /&gt;
* I implemented the card elements in the same style as the ACT 1 page&lt;br /&gt;
** We need to figure out a way to make the links to the gene ID&amp;#039;s generic so they can easily be retrieved and updated for every gene&lt;br /&gt;
** Would also be ideal to make the formatting of the content in each card clear&lt;br /&gt;
* The only thing left to do is finalize design choices and make everything ready for the integration team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements and References = &lt;br /&gt;
* I worked with Nicole, Hayden, and Mary to discuss what the page will look like and how we should implement everything&lt;br /&gt;
* While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_14&amp;diff=5350</id>
		<title>ArashLari Week 14</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_14&amp;diff=5350"/>
				<updated>2017-12-05T02:14:55Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: Created page with &amp;quot;= Electronic Lab Notebook =  * This week we began moving towards the final design for the gene page for GRNSight. * With some discussion and guidance from professors Dahlquist...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Lab Notebook =&lt;br /&gt;
&lt;br /&gt;
* This week we began moving towards the final design for the gene page for GRNSight.&lt;br /&gt;
* With some discussion and guidance from professors Dahlquist and Dionisio we came up with enough material for the integration team to not get slowed down&lt;br /&gt;
* Nicole drafted a rough design of what our page should look like, based off of the reception of ACT1, the rest of the team agreed with her design&lt;br /&gt;
* I implemented the card elements in the same style as the ACT 1 page&lt;br /&gt;
** We need to figure out a way to make the links to the gene ID&amp;#039;s generic so they can easily be retrieved and updated for every gene&lt;br /&gt;
** Would also be ideal to make the formatting of the content in each card clear&lt;br /&gt;
* The only thing left to do is finalize design choices and make everything ready for the integration team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements and References = &lt;br /&gt;
* I worked with Nicole, Hayden, and Mary to discuss what the page will look like and how we should implement everything&lt;br /&gt;
* While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4944</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4944"/>
				<updated>2017-11-21T05:02:14Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Page Desiigner Uploaded Files */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
&lt;br /&gt;
===Citations===&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Journal Club Presentations==&lt;br /&gt;
===Powerpoint Slides and Respective Articles===&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
*&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
*Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12] | Arash Lari Week 12]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
*This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think we all got a better grasp of the assignment and time management for the assignment. We have a clear idea where we&amp;#039;re headed.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* I wish we had more time to dedicate to this class, as often our schedules don&amp;#039;t line up. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*We&amp;#039;ll try to be more proactive about all our tasks so they don&amp;#039;t pile up. I&amp;#039;m planning on starting some work during the thanksgiving break to lighten the load afterwards.&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*This week we were a little more prepared to work together and complete the deliverables. As time goes by the end goal is becoming more apparent.&lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*I spent a lot of time reading the article multiple times and it is still a bit confusing to me. A lot of the vocabulary wasn&amp;#039;t even found in the dictionaries we provided and a lot of the information needed a lot of background knowledge to comprehend.&lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try and do the bulk of the assignment earlier in the week rather than on the weekend, so I may have more time to understand the material.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4938</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4938"/>
				<updated>2017-11-21T04:48:48Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Week 12 Team Progress Reflections */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
===Journal Club Presentations===&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12] | Arash Lari Week 12]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
*This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think we all got a better grasp of the assignment and time management for the assignment. We have a clear idea where we&amp;#039;re headed.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* I wish we had more time to dedicate to this class, as often our schedules don&amp;#039;t line up. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*We&amp;#039;ll try to be more proactive about all our tasks so they don&amp;#039;t pile up. I&amp;#039;m planning on starting some work during the thanksgiving break to lighten the load afterwards.&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
#What Worked?&lt;br /&gt;
#*This week we were a little more prepared to work together and complete the deliverables. As time goes by the end goal is becoming more apparent.&lt;br /&gt;
#What didn&amp;#039;t work?&lt;br /&gt;
#*I spent a lot of time reading the article multiple times and it is still a bit confusing to me. A lot of the vocabulary wasn&amp;#039;t even found in the dictionaries we provided and a lot of the information needed a lot of background knowledge to comprehend.&lt;br /&gt;
#What will I do next week to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Next week I will try and do the bulk of the assignment earlier in the week rather than on the weekend, so I may have more time to understand the material.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4936</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4936"/>
				<updated>2017-11-21T04:44:22Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Arash */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
===Journal Club Presentations===&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12] | Arash Lari Week 12]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
*This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4935</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4935"/>
				<updated>2017-11-21T04:44:11Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Arash */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
===Journal Club Presentations===&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12]]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
*This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4933</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4933"/>
				<updated>2017-11-21T04:43:32Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Arash */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
===Journal Club Presentations===&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12] | Arash Lari Week 12]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
*This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4932</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4932"/>
				<updated>2017-11-21T04:43:04Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Week 12 Executive Summaries */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
==Team Schedule==&lt;br /&gt;
[[Page Desiigner Schedule]]&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
===Journal Club Presentations===&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week was rather light compared to the previous week. We mostly set up the files on our personal computers, which was convenient because as a computer science major I already had most of the necessary files. Nicole and I talked about some preliminary designs and set up a rough schedule that we&amp;#039;ll make concrete after the break. This can be found on my week 12 page [[ArashLari Week 12]]. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:43, 20 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
*This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_12&amp;diff=4923</id>
		<title>ArashLari Week 12</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_12&amp;diff=4923"/>
				<updated>2017-11-21T04:23:42Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: Created page with &amp;quot;==Electronic Notebook== For this week&amp;#039;s assignment  Nicole Kalcic and I worked on the Coder Milestones 0-4. We set up all the necessary files on our...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Electronic Notebook==&lt;br /&gt;
For this week&amp;#039;s assignment  [[User:Nicolekalcic|Nicole Kalcic]] and I worked on the [[Coder]] Milestones 0-4. We set up all the necessary files on our computers as according to milestones 0-3, then Nicole and I communicated briefly over some ideas for the website design. We plan to do some preliminary work over the thanksgiving break. [[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:23, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===Milestone 0===&lt;br /&gt;
#Our [[Week 11]] journal club presentation. The powerpoint can be found here:&lt;br /&gt;
#*[[File: Data Driven Design.zip | Arash and Nicole&amp;#039;s presentaton]&lt;br /&gt;
&lt;br /&gt;
===Milestone 1===&lt;br /&gt;
#This portion required our individual computers had the correct software to complete the project.&lt;br /&gt;
# As a computer science student I already had the following files, but we also installed them on Nicole&amp;#039;s computer.&lt;br /&gt;
* Node.js 8.4.0 &lt;br /&gt;
* Code-savvy editor (Atom)&lt;br /&gt;
* Web browser with developer tools (Chrome)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;git&amp;#039;&amp;#039;&amp;#039; version control software&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;curl&amp;#039;&amp;#039;&amp;#039; command&lt;br /&gt;
&lt;br /&gt;
===Milestone 2===&lt;br /&gt;
#This portion required us to fork the open source [https://github.com/dondi/GRNsight GRNsight project]. &lt;br /&gt;
#*This is found in the top right corner of the GRNsight GitHub project page.&lt;br /&gt;
#I was added to the branch by Blair, and our fork is called page-design.&lt;br /&gt;
#The fork is currently under my GitHub account: arashlari.&lt;br /&gt;
&lt;br /&gt;
===Milestone 3===&lt;br /&gt;
#For this part of the assignment, we needed to download the project code from GitHub.&lt;br /&gt;
#We followed these instructions: [https://github.com/dondi/GRNsight/wiki/Running-the-Applications instructions in the GRNsight wiki]&lt;br /&gt;
# We performed &amp;quot;git clone&amp;quot; to acquire the files, &amp;quot;cd&amp;quot; into the appropriate folder on our personal computers, and &amp;quot;git checkout&amp;quot; to the branch we were assigned to.&lt;br /&gt;
# I personally used GitKraken as I am more comfortable with it, it&amp;#039;s simply a Git tool that has a GUI which I find enjoyable.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Milestone 4===&lt;br /&gt;
#We looked at what the most liked pages were and why, and began sketching out some ideas as for layouts and color schemes.&lt;br /&gt;
#Nicole being the one with the artistic background was focused on the aesthetic elements, while I focused on how I would use bootstrap to implement everything while still relaying the relevant technical information to Nicole.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgments==&lt;br /&gt;
#For this weeks assignment, my group didn&amp;#039;t meet in person all together as it was not necessary but we all kept each other updated through text messaging.&lt;br /&gt;
#Nicole and I discussed design ideas over the phone.&lt;br /&gt;
#&amp;#039;&amp;#039;&amp;#039;While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
==References==&lt;br /&gt;
LMU BioDB 2017. (2017). Week 12. Retrieved November 15, 2017, from https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_12&lt;br /&gt;
{{Template:ArashLari}}&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:23, 20 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Template:ArashLari&amp;diff=4919</id>
		<title>Template:ArashLari</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Template:ArashLari&amp;diff=4919"/>
				<updated>2017-11-21T04:12:27Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[User:ArashLari|Arash Lari]]&lt;br /&gt;
&lt;br /&gt;
[[Main_Page| BIOL/CMSI 367-01: Biological Databases Fall 2017]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
*[[Week_1|Week 1]]&lt;br /&gt;
*[[Week_2|Week 2]]&lt;br /&gt;
*[[Week_3|Week 3]]&lt;br /&gt;
*[[Week_4|Week 4]]&lt;br /&gt;
*[[Week_5|Week 5]]&lt;br /&gt;
*[[Week_6|Week 6]]&lt;br /&gt;
*[[Week_7|Week 7]]&lt;br /&gt;
*[[Week_8|Week 8]]&lt;br /&gt;
*[[Week_9|Week 9]]&lt;br /&gt;
*[[Week_10|Week 10]]&lt;br /&gt;
*[[Week_11|Week 11]]&lt;br /&gt;
*[[Week_12|Week 12]]&lt;br /&gt;
*[[Week_13|Week 13]]&lt;br /&gt;
*[[Week_14|Week 14]]&lt;br /&gt;
*[[Week_15|Week 15]]&lt;br /&gt;
*[[Week_16|Week 16]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Journal Entries&amp;#039;&amp;#039;&amp;#039;:&lt;br /&gt;
*[[ArashLari_Week_2|ArashLari Week 2]]&lt;br /&gt;
*[[ArashLari_Week_3|ArashLari Week 3]]&lt;br /&gt;
*[[ArashLari_Week_4|ArashLari Week 4]]&lt;br /&gt;
*[[ArashLari_Week_5|ArashLari Week 5]]&lt;br /&gt;
*[[ArashLari_Week_6|ArashLari Week 6]]&lt;br /&gt;
*[[ArashLari_Week_7|ArashLari Week 7]]&lt;br /&gt;
*[[ArashLari_Week_8|ArashLari Week 8]]&lt;br /&gt;
*[[ArashLari_Week_9|ArashLari Week 9]]&lt;br /&gt;
*[[ArashLari_Week_10|ArashLari Week 10]]&lt;br /&gt;
*[[ArashLari_Week_11|ArashLari Week 11]]&lt;br /&gt;
*[[ArashLari_Week_12|ArashLari Week 12]]&lt;br /&gt;
*[[ArashLari_Week_13|ArashLari Week 13]]&lt;br /&gt;
*[[ArashLari_Week_14|ArashLari Week 14]]&lt;br /&gt;
*[[ArashLari_Week_15|ArashLari Week 15]]&lt;br /&gt;
*[[ArashLari_Week_16|ArashLari Week 16]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Shared Journals&amp;#039;&amp;#039;&amp;#039;:&lt;br /&gt;
*[[Class_Journal_Week_1|ArashLari Week 1 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_2|ArashLari Week 2 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_3|ArashLari Week 3 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_4|ArashLari Week 4 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_5|ArashLari Week 5 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_6|ArashLari Week 6 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_7|ArashLari Week 7 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_8|ArashLari Week 8 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_9|ArashLari Week 9 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_10|ArashLari Week 10 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_11|ArashLari Week 11 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_12|ArashLari Week 12 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_13|ArashLari Week 13 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_14|ArashLari Week 14 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_15|ArashLari Week 15 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_16|ArashLari Week 16 Journal]]&lt;br /&gt;
*[[Page Desiigner]]&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Template:Pagedesiigner&amp;diff=4918</id>
		<title>Template:Pagedesiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Template:Pagedesiigner&amp;diff=4918"/>
				<updated>2017-11-21T04:10:32Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Uploaded Files */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width: 100%; text-align: center&amp;quot;&lt;br /&gt;
! colspan=&amp;quot;8&amp;quot;|GRNsight Gene Page Project Links&lt;br /&gt;
|-&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot;|[[GRNsight Gene Page Project|Overview]]&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot;| [[GRNsight Gene Page Project Deliverables|Deliverables]]&lt;br /&gt;
| rowspan=&amp;quot;2&amp;quot;|[https://peerj.com/about/author-instructions/#reference-format Reference Format]&lt;br /&gt;
! Guilds&lt;br /&gt;
| [[Project Manager]]&lt;br /&gt;
| [[Quality Assurance]]&lt;br /&gt;
| [[Data Analysis]]&lt;br /&gt;
| [[Coder]]&lt;br /&gt;
|-&lt;br /&gt;
! Teams&lt;br /&gt;
| [[Page Desiigner]]&lt;br /&gt;
| [[Lights, Camera, InterACTION!]]&lt;br /&gt;
| [[White Chicks]]&lt;br /&gt;
| [[JASPAR the Friendly Ghost]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Page Desiigner Schedule===&lt;br /&gt;
*[[Page Desiigner Schedule]]&lt;br /&gt;
===Uploaded Files===&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
&lt;br /&gt;
===Individual Contributer Pages===&lt;br /&gt;
[[User:ArashLari|Arash Lari]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[User:Nicolekalcic|Nicole Kalcic]]&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4917</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4917"/>
				<updated>2017-11-21T04:09:35Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Week 11 Executive Summaries */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Page Desiigner]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Page Desiigner Uploaded Files==&lt;br /&gt;
===Journal Club Presentations===&lt;br /&gt;
[[Media:MaryHaydenWeek12JournalClubPresentation.pptx ‎]]&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*Publisher: American Society for Microbiology. This is a scientific society.&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*Publisher: Elsevier. This is a for-profit publisher&lt;br /&gt;
*Availability:  Online and in print&lt;br /&gt;
*Did LMU pay a fee for this article: No&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
&lt;br /&gt;
==Executive Summaries==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks. All of this information could be found on my Week 11 page: [[ArashLari_Week_11|ArashLari Week 11]].&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
====Mary====&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
====Hayden====&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Executive Summaries===&lt;br /&gt;
====Arash====&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
This week I read an article about an experiment done on wine and lab strains of yeast in different temperatures. The experimenters used DNA microarrays to determine which genes were affected by the change in temperatures and which were different based on the different strains of yeast. While reading the article, I can across words I had never seen before, so I also found and recorded the definitions of these words. I then made an outline of the article, to use as a basis for my presentation with our project manager, [[user:hhinsch| Hayden]]. All of this is on my [[mbalducc Week 12| Week 12]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 19:51, 19 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
*This week I worked with Mary specifically in order to complete our journal club presentation. As a group we worked together to make corrections to the [[Page Desiigner]] group page in order to complete the deliverables for this week. Mary and I created a schedule for our group along with helpful links. As a class we decided we will be using WhatsApp to communicate. I spent most of this week outlining the article (it was a pretty difficult read) and defining terms on my [[hhinsch Week 12]] page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 17:42, 20 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Team Progress Reflections==&lt;br /&gt;
&lt;br /&gt;
===[[Week 11]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
====Hayden====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
 	&lt;br /&gt;
# What worked?&lt;br /&gt;
#*We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
	&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We were unable to schedule time to meet and work effectively. &lt;br /&gt;
 	&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===[[Week 12]] Team Progress Reflections===&lt;br /&gt;
&lt;br /&gt;
====Arash====&lt;br /&gt;
&lt;br /&gt;
====Mary====&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think that this week I felt more comfortable with the project as a whole. I also liked presenting after the other guilds because I got to see their presentations to get a better idea of what we should include in ours.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*I wish that I had more time to read the article and make the presentation. I felt that I didn&amp;#039;t understand the article completely, and had to read it a few times to be happy with the way that I understood it and formed my outline of it. Because of this, I couldn&amp;#039;t spend as much time as I would&amp;#039;ve wanted on making the presentation.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I will try to spend more time on the entire project, instead of just one part.&lt;br /&gt;
&lt;br /&gt;
====Nicole====&lt;br /&gt;
&lt;br /&gt;
====Hayden====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Template:ArashLari&amp;diff=4916</id>
		<title>Template:ArashLari</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Template:ArashLari&amp;diff=4916"/>
				<updated>2017-11-21T04:08:46Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[User:ArashLari|Arash Lari]]&lt;br /&gt;
&lt;br /&gt;
[[Main_Page| BIOL/CMSI 367-01: Biological Databases Fall 2017]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
*[[Week_1|Week 1]]&lt;br /&gt;
*[[Week_2|Week 2]]&lt;br /&gt;
*[[Week_3|Week 3]]&lt;br /&gt;
*[[Week_4|Week 4]]&lt;br /&gt;
*[[Week_5|Week 5]]&lt;br /&gt;
*[[Week_6|Week 6]]&lt;br /&gt;
*[[Week_7|Week 7]]&lt;br /&gt;
*[[Week_8|Week 8]]&lt;br /&gt;
*[[Week_9|Week 9]]&lt;br /&gt;
*[[Week_10|Week 10]]&lt;br /&gt;
*[[Week_11|Week 11]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Journal Entries&amp;#039;&amp;#039;&amp;#039;:&lt;br /&gt;
*[[ArashLari_Week_2|ArashLari Week 2]]&lt;br /&gt;
*[[ArashLari_Week_3|ArashLari Week 3]]&lt;br /&gt;
*[[ArashLari_Week_4|ArashLari Week 4]]&lt;br /&gt;
*[[ArashLari_Week_5|ArashLari Week 5]]&lt;br /&gt;
*[[ArashLari_Week_6|ArashLari Week 6]]&lt;br /&gt;
*[[ArashLari_Week_7|ArashLari Week 7]]&lt;br /&gt;
*[[ArashLari_Week_8|ArashLari Week 8]]&lt;br /&gt;
*[[ArashLari_Week_9|ArashLari Week 9]]&lt;br /&gt;
*[[ArashLari_Week_10|ArashLari Week 10]]&lt;br /&gt;
*[[ArashLari_Week_11|ArashLari Week 11]]&lt;br /&gt;
*[[ArashLari_Week_12|ArashLari Week 12]]&lt;br /&gt;
*[[ArashLari_Week_13|ArashLari Week 13]]&lt;br /&gt;
*[[ArashLari_Week_14|ArashLari Week 14]]&lt;br /&gt;
*[[ArashLari_Week_15|ArashLari Week 15]]&lt;br /&gt;
*[[ArashLari_Week_16|ArashLari Week 16]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Shared Journals&amp;#039;&amp;#039;&amp;#039;:&lt;br /&gt;
*[[Class_Journal_Week_1|ArashLari Week 1 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_2|ArashLari Week 2 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_3|ArashLari Week 3 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_4|ArashLari Week 4 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_5|ArashLari Week 5 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_6|ArashLari Week 6 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_7|ArashLari Week 7 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_8|ArashLari Week 8 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_9|ArashLari Week 9 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_10|ArashLari Week 10 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_11|ArashLari Week 11 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_12|ArashLari Week 12 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_13|ArashLari Week 13 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_14|ArashLari Week 14 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_15|ArashLari Week 15 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_16|ArashLari Week 16 Journal]]&lt;br /&gt;
*[[Page Desiigner]]&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4562</id>
		<title>Page Desiigner</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Page_Desiigner&amp;diff=4562"/>
				<updated>2017-11-14T10:09:13Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Assignment]]&lt;br /&gt;
[[Category:Group Projects]]&lt;br /&gt;
&lt;br /&gt;
==Page Design Team Members==&lt;br /&gt;
Coder: [[User:ArashLari|Arash Lari]]&amp;lt;!--Replicated from home page--&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Project Manager/ Quality Assurance: [[User:hhinsch|Hayden Hinsch]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Data Analyst: [[User:Mbalducc|Mary Balducci]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Designer: [[User:Nicolekalcic|Nicole Kalcic]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[[Week 11]] Executive Summaries==&lt;br /&gt;
===Arash===&lt;br /&gt;
This week, I worked on researching the given article and the development terms within it as well as prepare a presentation on the article. I also began thinking of some page layout ideas with Nicole to prepare to implement in the coming weeks.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 02:09, 14 November 2017 (PST)&lt;br /&gt;
===Mary===&lt;br /&gt;
This week, I worked on creating an annotated bibliography. The articles I found were primary sources about experiments done involving cold shock on yeast, and the use of microarrays to show results. I used multiple databases to find these articles, and while doing so I learned what key words got me the results closest to what I wanted. While writing the annotated bibliography, I also learned more about the articles, such as when they were written, who published them, what kind of publisher they are, and other information. All of this is recorded in my [[mbalducc Week 11| Week 11]] page.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 23:03, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===Nicole===&lt;br /&gt;
This past week, I read the article &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039; by L.A. Liikkanen. This allowed me to complete my individual journal: an informative outline of the article and list of ten definitions. Arash and I worked together to complete a 15 minute presentation that we are going to give on Tuesday. The presentation gives an overview of our individual journals and what we each learned. You can access more information on what I did this week here: [[Nicolekalcic Week 11]].&lt;br /&gt;
[[User:Nicolekalcic|Nicolekalcic]] ([[User talk:Nicolekalcic|talk]]) 01:27, 14 November 2017 (PST)&lt;br /&gt;
===Hayden===&lt;br /&gt;
This week I created part of the annotated bibliography we will be using for our final project. I conducted searched for &amp;quot;yeast cold shock microarray&amp;quot; articles and found which two articles I was going to use for the bibliography. The majority of the time this week was spent on finding the information needed for the annotated bibliography which can be found below on this page. More detailed information can be found on my [[hhinsch Week 11]] page. This week I became proficient in finding reliable article to use for our final project. This week we also created the group&amp;#039;s template and wiki page. [[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:43, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==[[Week 11]] Team Progress Reflection==&lt;br /&gt;
===Nicole===&lt;br /&gt;
# What worked?&lt;br /&gt;
#* We all work well in our positions. Arash and I worked together recently, so it was easy to coordinate what we are going to do as coder and designer. Everyone was open to opinions on the page and team name. Also, everyone communicated what they were having trouble finishing. &lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#* Like Mary said, we weren&amp;#039;t able to meet in person. We planned out our meetup during class, but Friday ended up being a busy day for everyone. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#* Next week I will make sure to check in more with my partners. Even if we don&amp;#039;t meet up, it is important to make sure everyone is caught up on the assignment and their individual parts. &lt;br /&gt;
===Mary===&lt;br /&gt;
# What worked?&lt;br /&gt;
#*I think as a team, we did a good job communicating and figuring out what needed to be done, and who would do each part.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
#*We did not meet up outside of class. We had planned to, but we all ended up having conflicts so we couldn&amp;#039;t meet.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
#*I think this can be fixed just by making sure we all communicate in other ways, which is what we did. Through text messages we were able to talk about the assignment and help each other.&lt;br /&gt;
===Hayden===&lt;br /&gt;
# What worked?&lt;br /&gt;
*We are all doing well communicating and completing our deliverables as individuals and as a group.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
*Everything worked well in regards to the group, but I did have some trouble finding all the information needed to create an annotated bibliography for the articles I used. Google Scholar gave me way too many results, and PubMed did not have a lot of articles that were either free or LMU had paid for.&lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
*I will continue to ask questions in class. I also feel more confident about finding useful articles after the completion of this assignment, so it shouldn&amp;#039;t be a problem.&lt;br /&gt;
[[User:Hhinsch|Hhinsch]] ([[User talk:Hhinsch|talk]]) 22:44, 13 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
===Arash===&lt;br /&gt;
# What worked?&lt;br /&gt;
We were good at maintaining our own individual tasks and keeping each other updated via text message.&lt;br /&gt;
# What didn&amp;#039;t work?&lt;br /&gt;
We were unable to schedule time to meet and work effectively. &lt;br /&gt;
# What will I do next to fix what didn&amp;#039;t work?&lt;br /&gt;
Hopefully we will have lighter course loads and more free time for the next assignment, but besides that we will begin working sooner and try to work in person more than digitally.&lt;br /&gt;
==Annotated Bibliography==&lt;br /&gt;
===Mary&amp;#039;s contribution:===&lt;br /&gt;
Pizzaro, Jewett, Nielson, Agosin. (2008) Growth Temperature Exerts Differential Physiological and Transcriptional Responses in Laboratory and Wine Strains of Saccharomyces Cerevisiae. &amp;quot;Applied and Environmental Microbiology&amp;quot;, 74, 6358-6368, doi:10.1128/AEM.00602-08&lt;br /&gt;
*PubMed Abstract: https://www.ncbi.nlm.nih.gov/pubmed/18723660&lt;br /&gt;
*PubMed Central: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*HTML format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/&lt;br /&gt;
*PDF format: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2570279/pdf/0602-08.pdf&lt;br /&gt;
*Copyright: 2008 American Society for Microbiology. It is open access.&lt;br /&gt;
*The publisher is American Society for Microbiology.&lt;br /&gt;
**This is a scientific society.&lt;br /&gt;
*This article is available both online and in print.&lt;br /&gt;
**LMU has not paid a fee for my access to this article.&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Homma, Iwahashi, Komatsu. (2003) Yeast Gene Expression During Growth at Low Temperature. &amp;#039;&amp;#039;Cryobiology&amp;#039;&amp;#039;, 46, doi: 10.1016/S0011-2240(03)00028-2&lt;br /&gt;
*PubMed abstract: https://www.ncbi.nlm.nih.gov/pubmed/12818212&lt;br /&gt;
*PubMed Central: &lt;br /&gt;
*HTML format: http://www.sciencedirect.com/science/article/pii/S0011224003000282?via%3Dihub&lt;br /&gt;
*PDF format: https://ac.els-cdn.com/S0011224003000282/1-s2.0-S0011224003000282-main.pdf?_tid=aa7fa05e-c5d2-11e7-88ae-00000aacb361&amp;amp;acdnat=1510289609_6ec25501ce7af9dcc6b521ef8a024164&lt;br /&gt;
*Copyright 2003 Elsevier Science (USA). It is open access.&lt;br /&gt;
*The publisher is Elsevier.&lt;br /&gt;
**This is a for-profit publisher&lt;br /&gt;
*This article is available both online and in print.&lt;br /&gt;
**LMU has not paid a fee for my access to this article.&lt;br /&gt;
*I could not find the data associated with this article.&lt;br /&gt;
&lt;br /&gt;
===Hayden&amp;#039;s Contribution===&lt;br /&gt;
&lt;br /&gt;
Dahlquist, K. D., Fitzpatrick, B. G., Camacho, E. T., Entzminger, S. D., &amp;amp; Wanner, N. C. (2015). Parameter Estimation for Gene Regulatory Networks from Microarray Data: Cold Shock Response in Saccharomyces cerevisiae. Bulletin of Mathematical Biology, 77(8), 1457–1492. http://doi.org/10.1007/s11538-015-0092-6&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/26420504&lt;br /&gt;
* PubMed Central:  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/&lt;br /&gt;
* Publisher Full Text (HTML):  https://link.springer.com/article/10.1007/s11538-015-0092-6&lt;br /&gt;
* Publisher Full Text (PDF):  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/pdf/11538_2015_Article_92.pdf&lt;br /&gt;
* Copyright: The Author(s) 2015. Open Access: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.&lt;br /&gt;
* Publisher: Bulletin of Mathematical Biology(scientific society)&lt;br /&gt;
* Availability: Online&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4636536/bin/11538_2015_92_MOESM1_ESM.zip&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ando, A., Nakamura, T., Murata, Y., Takagi, H. and Shima, J. (2007), Identification and classification of genes required for tolerance to freeze–thaw stress revealed by genome-wide screening of Saccharomyces cerevisiae deletion strains. FEMS Yeast Research, 7: 244–253. doi:10.1111/j.1567-1364.2006.00162.x&lt;br /&gt;
* PubMed Abstract:  https://www.ncbi.nlm.nih.gov/pubmed/16989656&lt;br /&gt;
* PubMed Central:  N/A&lt;br /&gt;
* Publisher Full Text (HTML):  https://academic.oup.com/femsyr/article/7/2/244/616825?searchresult=1&lt;br /&gt;
* Publisher Full Text (PDF):  http://onlinelibrary.wiley.com/doi/10.1111/j.1567-1364.2006.00162.x/epdf&lt;br /&gt;
* Copyright:  Copyright © 2007, Oxford University Press; Open Access after time has elapsed: This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. You must ask permission from the publisher to use the article.&lt;br /&gt;
* Publisher:  Published by Oxford University Press(respected open access organization)&lt;br /&gt;
* Availability:  Online and in print&lt;br /&gt;
* Did LMU pay a fee for this article: No&lt;br /&gt;
* Data: I couldn&amp;#039;t find any supplementary data other than the data provided in the article.&lt;br /&gt;
{{Pagedesiigner}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4561</id>
		<title>ArashLari Week 11</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4561"/>
				<updated>2017-11-14T10:03:59Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Outline and Presentation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Development Terms==&lt;br /&gt;
*Read: &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039;&lt;br /&gt;
*By: Lassi A. Liikkanen&lt;br /&gt;
This article introduced me to many terms I hadn&amp;#039;t heard in respect to design before, but the author did a good job of explaining them so I didn&amp;#039;t need to consult outside sources very much. I had heard of most of the analytics products before but there were a few I wasn&amp;#039;t familiar with. The following terms are defined according to my understanding after reading their definitions.&lt;br /&gt;
&lt;br /&gt;
*Generative Design&lt;br /&gt;
**A development process that is akin to evolution. The process is to set out design goals and an initial schema, and then go through several permutations of variation until arriving at the best option.  (Flake, 1998)&lt;br /&gt;
*Heat Maps&lt;br /&gt;
**Heat maps in regards to design are basically the same as heat maps in terms of population movement. It is a visual representation of where the average users cursor hovers and clicks and for what amount of time. (Liikkanen, 2017)&lt;br /&gt;
*User Screen Recordings&lt;br /&gt;
**A user screen recording is a literal video of the individual user&amp;#039;s screen during their session on the application. (Liikkanen, 2017)&lt;br /&gt;
*A/B Tests&lt;br /&gt;
** A controlled test with two variants. This is used to compare different potential design layouts and choose the most effective elements from them. (Kohavi, Longbotham 2015)&lt;br /&gt;
*Behavioural Analytics&lt;br /&gt;
**The contextual information around a users session on an application, including information such as the usage log, click-stream data, average time spent on each page, etc. (Liikkanen, 2017)&lt;br /&gt;
*Assistive Tools&lt;br /&gt;
** Tools that make tasks easier for humans but still require a human interaction. (Liikkanen, 2017)&lt;br /&gt;
*Agentive Tools&lt;br /&gt;
** Tools that do tasks for humans and eliminate the need for the humans to do anything related to the task. (Liikkanen, 2017)&lt;br /&gt;
*Net Promoter Score&lt;br /&gt;
** A measure from -100 to 100 of a customer&amp;#039;s willingness to refer a product or company to a peer. (NetPromoter, 2017)&lt;br /&gt;
*KISSmetrics&lt;br /&gt;
** A behavioural analytics service that provides automated tools for interpreting data from customers. (Kissmetrics, 2017).&lt;br /&gt;
*IBM TeaLeaf&lt;br /&gt;
**A company that IBM acquired that is focused on bettering customer experience through behavioural analytics. (IBM, 2017).&lt;br /&gt;
&lt;br /&gt;
==Outline and Presentation==&lt;br /&gt;
[[File:Data Driven Design.zip]]&lt;br /&gt;
===What is Data Driven Design?===&lt;br /&gt;
*Traditionally, products were designed by the designers intuition and opinion&lt;br /&gt;
**This is because collecting information about user activity has been difficult until recently&lt;br /&gt;
*The rise of technology and internet based services has led to evidenced-based design&lt;br /&gt;
**Companies and developers want to know that their intended users will be able to easily use their service before it affects sales&lt;br /&gt;
*Designing based off of results empirical user evidence is called data driven design&lt;br /&gt;
**There are assistive and agentive generative tools to help creative tasks&lt;br /&gt;
***A generative design process basically means designing and redesigning based on how the previous iteration was received&lt;br /&gt;
**It’s basically an assortment of tools at the disposal of the designers and the developers that they can use in a multitude of ways to gauge how effective their design is.&lt;br /&gt;
**The basic idea of this design philosophy is to collect data, combine it with other data, and analyze it for implementation in the final design&lt;br /&gt;
=== Data Driven Design of Web Services ===&lt;br /&gt;
*Web interaction design is a field that utilizes data design driven solutions frequently&lt;br /&gt;
**Major internet companies often build their own experiment-management platforms so they can run many different experiments in parallel with automation&lt;br /&gt;
*Data-collection can be separated into two types of solutions: Active and Passive&lt;br /&gt;
**Active data collection is reliant on user input, and as such it’s considered qualitative&lt;br /&gt;
***It doesn’t really fit the mold of DDD very well if the scale is large&lt;br /&gt;
***Surveys are often plagued with many issues such as reluctance to participate and low quality answers that don’t provide very much insight&lt;br /&gt;
***In smaller cases it is very useful, such as using an online focus group to get detailed reactions and responses&lt;br /&gt;
****This is costly, which is why large corporations don’t often do this&lt;br /&gt;
**Passive data collection, or passive tracking is any kind of recording of user activity&lt;br /&gt;
***Screen recordings, heat maps, experiment management, and descriptive behavioral analytics are some passive tracking tools&lt;br /&gt;
****Screen recordings are full recordings of the users screen for later analysis.&lt;br /&gt;
****Provides a very detailed view and a lot of useful implementation&lt;br /&gt;
****However, raises privacy and ethical concerns and can’t really be automated to gain insight&lt;br /&gt;
**Heat maps are a way to visualize the most frequently clicked on and hovered on spots of a page&lt;br /&gt;
***It isn’t always very clear because some pages might be context specific, but it still can provide enough information to help optimize the design of the page &lt;br /&gt;
**Experiment management is basically having 2 or more types of designs be tested on to find which features and design choices should be kept or removed&lt;br /&gt;
***It allows developers to find fail new ideas quickly so they don’t have to waste time with subpar designs&lt;br /&gt;
***They can be automated but their shortcoming is the numbers aren’t always that insightful&lt;br /&gt;
**Behavioral analytics are the precursor to all current DDD solutions&lt;br /&gt;
***It’s all the contextual data related to the visit, such as the amount of time spent and on what pages, what elements were clicked and in what order, etc.&lt;br /&gt;
***This information is more useful for business and marketing decisions rather than design decisions.&lt;br /&gt;
****Many companies offer analytics solutions for developers&lt;br /&gt;
*****Google is the biggest by far, but there are others such as Adobe Analytics, KISSMetrics, and IBM Tealeaf&lt;br /&gt;
=== Conclusion ===&lt;br /&gt;
*Data driven design provides designers a strong incentive to adopt a hypothesis-driven approach to design research&lt;br /&gt;
**Having a clear hypothesis is important as it will affect the way one interprets data and identify which results are the most significant&lt;br /&gt;
**The age of Data Driven Design draws heavily upon designer moral, integrity, and candor. &lt;br /&gt;
***Ethics of how data is collected and used is very important, and consent is key in ethical data acquisition. &lt;br /&gt;
*The future of data driven design will be with tools that couple seamlessly with design processes, be adaptive to change, and show maturity in addressing ethical questions.&lt;br /&gt;
**Designers will embrace more quantitative data as tools that allow for scalability become available&lt;br /&gt;
**Design will introduce assistive and agentive tools that do things with us and for us&lt;br /&gt;
*What will we use for our project?&lt;br /&gt;
**We won’t use any of the passive tools directly&lt;br /&gt;
***Although useful, we do not have the means to get enough different users to get fruitful information using these methods&lt;br /&gt;
***Although we might implement experiment-management within our own small group and see what we collectively thinks works best&lt;br /&gt;
**We will be using active data collection, and ask our fellow classmates to browse our site and give us feedback as they use it&lt;br /&gt;
***This level of interactivity with the end-user provide useful insight&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
Our group met thursday after class to schedule a time to meet over the weekend. Unfortunately we didn&amp;#039;t meet in person over the weekend due to scheduling conflicts. We updated each other over the phone and Nicole and I went over what the article and presentation where about over the weekend and worked on it digitally on monday night. I also kept in contact with Hayden and he and Mary filled me in on their part and helped Nicole and I out for the presentation.&lt;br /&gt;
&lt;br /&gt;
== Acknowledgements ==&lt;br /&gt;
*I worked with my homework partners Hayden, Mary, and Nicole. We mostly communicated via phone call or text message.&lt;br /&gt;
&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 01:21, 14 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
* LMU BioDB 2017. (2017). Week 11. Retrieved November 13, 2017, from https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_11&lt;br /&gt;
* Kohavi, Ron; Longbotham, Roger (2015). &amp;quot;Online Controlled Experiments and A/B Tests&amp;quot;. Accessed November 13, 2017, from http://www.exp-platform.com/Documents/2015%20Online%20Controlled%20Experiments_EncyclopediaOfMLDM.pdf&lt;br /&gt;
*Gary William Flake: The Computational Beauty of Nature: Computer Explorations of Fractals, Chaos, Complex Systems, and Adaptation. MIT Press 1998, ISBN 978-0-262-56127-3&lt;br /&gt;
*IBM (2017), IBM TeaLeaf, Accessed on November 13, 2017 from https://www.ibm.com/customer-engagement/tealeaf&lt;br /&gt;
*Net Promoter (2017), Net Promoter, accessed on November 13, 2017 from https://www.netpromoter.com/know/&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=File:Data_Driven_Design.zip&amp;diff=4560</id>
		<title>File:Data Driven Design.zip</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=File:Data_Driven_Design.zip&amp;diff=4560"/>
				<updated>2017-11-14T10:01:49Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: Arash and Nicole&amp;#039;s presentation for Page Desiigner&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Arash and Nicole&amp;#039;s presentation for Page Desiigner&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4559</id>
		<title>ArashLari Week 11</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4559"/>
				<updated>2017-11-14T10:00:30Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Electronic Notebook */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Development Terms==&lt;br /&gt;
*Read: &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039;&lt;br /&gt;
*By: Lassi A. Liikkanen&lt;br /&gt;
This article introduced me to many terms I hadn&amp;#039;t heard in respect to design before, but the author did a good job of explaining them so I didn&amp;#039;t need to consult outside sources very much. I had heard of most of the analytics products before but there were a few I wasn&amp;#039;t familiar with. The following terms are defined according to my understanding after reading their definitions.&lt;br /&gt;
&lt;br /&gt;
*Generative Design&lt;br /&gt;
**A development process that is akin to evolution. The process is to set out design goals and an initial schema, and then go through several permutations of variation until arriving at the best option.  (Flake, 1998)&lt;br /&gt;
*Heat Maps&lt;br /&gt;
**Heat maps in regards to design are basically the same as heat maps in terms of population movement. It is a visual representation of where the average users cursor hovers and clicks and for what amount of time. (Liikkanen, 2017)&lt;br /&gt;
*User Screen Recordings&lt;br /&gt;
**A user screen recording is a literal video of the individual user&amp;#039;s screen during their session on the application. (Liikkanen, 2017)&lt;br /&gt;
*A/B Tests&lt;br /&gt;
** A controlled test with two variants. This is used to compare different potential design layouts and choose the most effective elements from them. (Kohavi, Longbotham 2015)&lt;br /&gt;
*Behavioural Analytics&lt;br /&gt;
**The contextual information around a users session on an application, including information such as the usage log, click-stream data, average time spent on each page, etc. (Liikkanen, 2017)&lt;br /&gt;
*Assistive Tools&lt;br /&gt;
** Tools that make tasks easier for humans but still require a human interaction. (Liikkanen, 2017)&lt;br /&gt;
*Agentive Tools&lt;br /&gt;
** Tools that do tasks for humans and eliminate the need for the humans to do anything related to the task. (Liikkanen, 2017)&lt;br /&gt;
*Net Promoter Score&lt;br /&gt;
** A measure from -100 to 100 of a customer&amp;#039;s willingness to refer a product or company to a peer. (NetPromoter, 2017)&lt;br /&gt;
*KISSmetrics&lt;br /&gt;
** A behavioural analytics service that provides automated tools for interpreting data from customers. (Kissmetrics, 2017).&lt;br /&gt;
*IBM TeaLeaf&lt;br /&gt;
**A company that IBM acquired that is focused on bettering customer experience through behavioural analytics. (IBM, 2017).&lt;br /&gt;
&lt;br /&gt;
==Outline and Presentation==&lt;br /&gt;
===What is Data Driven Design?===&lt;br /&gt;
*Traditionally, products were designed by the designers intuition and opinion&lt;br /&gt;
**This is because collecting information about user activity has been difficult until recently&lt;br /&gt;
*The rise of technology and internet based services has led to evidenced-based design&lt;br /&gt;
**Companies and developers want to know that their intended users will be able to easily use their service before it affects sales&lt;br /&gt;
*Designing based off of results empirical user evidence is called data driven design&lt;br /&gt;
**There are assistive and agentive generative tools to help creative tasks&lt;br /&gt;
***A generative design process basically means designing and redesigning based on how the previous iteration was received&lt;br /&gt;
**It’s basically an assortment of tools at the disposal of the designers and the developers that they can use in a multitude of ways to gauge how effective their design is.&lt;br /&gt;
**The basic idea of this design philosophy is to collect data, combine it with other data, and analyze it for implementation in the final design&lt;br /&gt;
=== Data Driven Design of Web Services ===&lt;br /&gt;
*Web interaction design is a field that utilizes data design driven solutions frequently&lt;br /&gt;
**Major internet companies often build their own experiment-management platforms so they can run many different experiments in parallel with automation&lt;br /&gt;
*Data-collection can be separated into two types of solutions: Active and Passive&lt;br /&gt;
**Active data collection is reliant on user input, and as such it’s considered qualitative&lt;br /&gt;
***It doesn’t really fit the mold of DDD very well if the scale is large&lt;br /&gt;
***Surveys are often plagued with many issues such as reluctance to participate and low quality answers that don’t provide very much insight&lt;br /&gt;
***In smaller cases it is very useful, such as using an online focus group to get detailed reactions and responses&lt;br /&gt;
****This is costly, which is why large corporations don’t often do this&lt;br /&gt;
**Passive data collection, or passive tracking is any kind of recording of user activity&lt;br /&gt;
***Screen recordings, heat maps, experiment management, and descriptive behavioral analytics are some passive tracking tools&lt;br /&gt;
****Screen recordings are full recordings of the users screen for later analysis.&lt;br /&gt;
****Provides a very detailed view and a lot of useful implementation&lt;br /&gt;
****However, raises privacy and ethical concerns and can’t really be automated to gain insight&lt;br /&gt;
**Heat maps are a way to visualize the most frequently clicked on and hovered on spots of a page&lt;br /&gt;
***It isn’t always very clear because some pages might be context specific, but it still can provide enough information to help optimize the design of the page &lt;br /&gt;
**Experiment management is basically having 2 or more types of designs be tested on to find which features and design choices should be kept or removed&lt;br /&gt;
***It allows developers to find fail new ideas quickly so they don’t have to waste time with subpar designs&lt;br /&gt;
***They can be automated but their shortcoming is the numbers aren’t always that insightful&lt;br /&gt;
**Behavioral analytics are the precursor to all current DDD solutions&lt;br /&gt;
***It’s all the contextual data related to the visit, such as the amount of time spent and on what pages, what elements were clicked and in what order, etc.&lt;br /&gt;
***This information is more useful for business and marketing decisions rather than design decisions.&lt;br /&gt;
****Many companies offer analytics solutions for developers&lt;br /&gt;
*****Google is the biggest by far, but there are others such as Adobe Analytics, KISSMetrics, and IBM Tealeaf&lt;br /&gt;
=== Conclusion ===&lt;br /&gt;
*Data driven design provides designers a strong incentive to adopt a hypothesis-driven approach to design research&lt;br /&gt;
**Having a clear hypothesis is important as it will affect the way one interprets data and identify which results are the most significant&lt;br /&gt;
**The age of Data Driven Design draws heavily upon designer moral, integrity, and candor. &lt;br /&gt;
***Ethics of how data is collected and used is very important, and consent is key in ethical data acquisition. &lt;br /&gt;
*The future of data driven design will be with tools that couple seamlessly with design processes, be adaptive to change, and show maturity in addressing ethical questions.&lt;br /&gt;
**Designers will embrace more quantitative data as tools that allow for scalability become available&lt;br /&gt;
**Design will introduce assistive and agentive tools that do things with us and for us&lt;br /&gt;
*What will we use for our project?&lt;br /&gt;
**We won’t use any of the passive tools directly&lt;br /&gt;
***Although useful, we do not have the means to get enough different users to get fruitful information using these methods&lt;br /&gt;
***Although we might implement experiment-management within our own small group and see what we collectively thinks works best&lt;br /&gt;
**We will be using active data collection, and ask our fellow classmates to browse our site and give us feedback as they use it&lt;br /&gt;
***This level of interactivity with the end-user provide useful insight&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
Our group met thursday after class to schedule a time to meet over the weekend. Unfortunately we didn&amp;#039;t meet in person over the weekend due to scheduling conflicts. We updated each other over the phone and Nicole and I went over what the article and presentation where about over the weekend and worked on it digitally on monday night. I also kept in contact with Hayden and he and Mary filled me in on their part and helped Nicole and I out for the presentation.&lt;br /&gt;
&lt;br /&gt;
== Acknowledgements ==&lt;br /&gt;
*I worked with my homework partners Hayden, Mary, and Nicole. We mostly communicated via phone call or text message.&lt;br /&gt;
&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 01:21, 14 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
* LMU BioDB 2017. (2017). Week 11. Retrieved November 13, 2017, from https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_11&lt;br /&gt;
* Kohavi, Ron; Longbotham, Roger (2015). &amp;quot;Online Controlled Experiments and A/B Tests&amp;quot;. Accessed November 13, 2017, from http://www.exp-platform.com/Documents/2015%20Online%20Controlled%20Experiments_EncyclopediaOfMLDM.pdf&lt;br /&gt;
*Gary William Flake: The Computational Beauty of Nature: Computer Explorations of Fractals, Chaos, Complex Systems, and Adaptation. MIT Press 1998, ISBN 978-0-262-56127-3&lt;br /&gt;
*IBM (2017), IBM TeaLeaf, Accessed on November 13, 2017 from https://www.ibm.com/customer-engagement/tealeaf&lt;br /&gt;
*Net Promoter (2017), Net Promoter, accessed on November 13, 2017 from https://www.netpromoter.com/know/&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4557</id>
		<title>ArashLari Week 11</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4557"/>
				<updated>2017-11-14T09:57:31Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Development Terms==&lt;br /&gt;
*Read: &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039;&lt;br /&gt;
*By: Lassi A. Liikkanen&lt;br /&gt;
This article introduced me to many terms I hadn&amp;#039;t heard in respect to design before, but the author did a good job of explaining them so I didn&amp;#039;t need to consult outside sources very much. I had heard of most of the analytics products before but there were a few I wasn&amp;#039;t familiar with. The following terms are defined according to my understanding after reading their definitions.&lt;br /&gt;
&lt;br /&gt;
*Generative Design&lt;br /&gt;
**A development process that is akin to evolution. The process is to set out design goals and an initial schema, and then go through several permutations of variation until arriving at the best option.  (Flake, 1998)&lt;br /&gt;
*Heat Maps&lt;br /&gt;
**Heat maps in regards to design are basically the same as heat maps in terms of population movement. It is a visual representation of where the average users cursor hovers and clicks and for what amount of time. (Liikkanen, 2017)&lt;br /&gt;
*User Screen Recordings&lt;br /&gt;
**A user screen recording is a literal video of the individual user&amp;#039;s screen during their session on the application. (Liikkanen, 2017)&lt;br /&gt;
*A/B Tests&lt;br /&gt;
** A controlled test with two variants. This is used to compare different potential design layouts and choose the most effective elements from them. (Kohavi, Longbotham 2015)&lt;br /&gt;
*Behavioural Analytics&lt;br /&gt;
**The contextual information around a users session on an application, including information such as the usage log, click-stream data, average time spent on each page, etc. (Liikkanen, 2017)&lt;br /&gt;
*Assistive Tools&lt;br /&gt;
** Tools that make tasks easier for humans but still require a human interaction. (Liikkanen, 2017)&lt;br /&gt;
*Agentive Tools&lt;br /&gt;
** Tools that do tasks for humans and eliminate the need for the humans to do anything related to the task. (Liikkanen, 2017)&lt;br /&gt;
*Net Promoter Score&lt;br /&gt;
** A measure from -100 to 100 of a customer&amp;#039;s willingness to refer a product or company to a peer. (NetPromoter, 2017)&lt;br /&gt;
*KISSmetrics&lt;br /&gt;
** A behavioural analytics service that provides automated tools for interpreting data from customers. (Kissmetrics, 2017).&lt;br /&gt;
*IBM TeaLeaf&lt;br /&gt;
**A company that IBM acquired that is focused on bettering customer experience through behavioural analytics. (IBM, 2017).&lt;br /&gt;
&lt;br /&gt;
==Outline and Presentation==&lt;br /&gt;
===What is Data Driven Design?===&lt;br /&gt;
*Traditionally, products were designed by the designers intuition and opinion&lt;br /&gt;
**This is because collecting information about user activity has been difficult until recently&lt;br /&gt;
*The rise of technology and internet based services has led to evidenced-based design&lt;br /&gt;
**Companies and developers want to know that their intended users will be able to easily use their service before it affects sales&lt;br /&gt;
*Designing based off of results empirical user evidence is called data driven design&lt;br /&gt;
**There are assistive and agentive generative tools to help creative tasks&lt;br /&gt;
***A generative design process basically means designing and redesigning based on how the previous iteration was received&lt;br /&gt;
**It’s basically an assortment of tools at the disposal of the designers and the developers that they can use in a multitude of ways to gauge how effective their design is.&lt;br /&gt;
**The basic idea of this design philosophy is to collect data, combine it with other data, and analyze it for implementation in the final design&lt;br /&gt;
=== Data Driven Design of Web Services ===&lt;br /&gt;
*Web interaction design is a field that utilizes data design driven solutions frequently&lt;br /&gt;
**Major internet companies often build their own experiment-management platforms so they can run many different experiments in parallel with automation&lt;br /&gt;
*Data-collection can be separated into two types of solutions: Active and Passive&lt;br /&gt;
**Active data collection is reliant on user input, and as such it’s considered qualitative&lt;br /&gt;
***It doesn’t really fit the mold of DDD very well if the scale is large&lt;br /&gt;
***Surveys are often plagued with many issues such as reluctance to participate and low quality answers that don’t provide very much insight&lt;br /&gt;
***In smaller cases it is very useful, such as using an online focus group to get detailed reactions and responses&lt;br /&gt;
****This is costly, which is why large corporations don’t often do this&lt;br /&gt;
**Passive data collection, or passive tracking is any kind of recording of user activity&lt;br /&gt;
***Screen recordings, heat maps, experiment management, and descriptive behavioral analytics are some passive tracking tools&lt;br /&gt;
****Screen recordings are full recordings of the users screen for later analysis.&lt;br /&gt;
****Provides a very detailed view and a lot of useful implementation&lt;br /&gt;
****However, raises privacy and ethical concerns and can’t really be automated to gain insight&lt;br /&gt;
**Heat maps are a way to visualize the most frequently clicked on and hovered on spots of a page&lt;br /&gt;
***It isn’t always very clear because some pages might be context specific, but it still can provide enough information to help optimize the design of the page &lt;br /&gt;
**Experiment management is basically having 2 or more types of designs be tested on to find which features and design choices should be kept or removed&lt;br /&gt;
***It allows developers to find fail new ideas quickly so they don’t have to waste time with subpar designs&lt;br /&gt;
***They can be automated but their shortcoming is the numbers aren’t always that insightful&lt;br /&gt;
**Behavioral analytics are the precursor to all current DDD solutions&lt;br /&gt;
***It’s all the contextual data related to the visit, such as the amount of time spent and on what pages, what elements were clicked and in what order, etc.&lt;br /&gt;
***This information is more useful for business and marketing decisions rather than design decisions.&lt;br /&gt;
****Many companies offer analytics solutions for developers&lt;br /&gt;
*****Google is the biggest by far, but there are others such as Adobe Analytics, KISSMetrics, and IBM Tealeaf&lt;br /&gt;
=== Conclusion ===&lt;br /&gt;
*Data driven design provides designers a strong incentive to adopt a hypothesis-driven approach to design research&lt;br /&gt;
**Having a clear hypothesis is important as it will affect the way one interprets data and identify which results are the most significant&lt;br /&gt;
**The age of Data Driven Design draws heavily upon designer moral, integrity, and candor. &lt;br /&gt;
***Ethics of how data is collected and used is very important, and consent is key in ethical data acquisition. &lt;br /&gt;
*The future of data driven design will be with tools that couple seamlessly with design processes, be adaptive to change, and show maturity in addressing ethical questions.&lt;br /&gt;
**Designers will embrace more quantitative data as tools that allow for scalability become available&lt;br /&gt;
**Design will introduce assistive and agentive tools that do things with us and for us&lt;br /&gt;
*What will we use for our project?&lt;br /&gt;
**We won’t use any of the passive tools directly&lt;br /&gt;
***Although useful, we do not have the means to get enough different users to get fruitful information using these methods&lt;br /&gt;
***Although we might implement experiment-management within our own small group and see what we collectively thinks works best&lt;br /&gt;
**We will be using active data collection, and ask our fellow classmates to browse our site and give us feedback as they use it&lt;br /&gt;
***This level of interactivity with the end-user provide useful insight&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Acknowledgements ==&lt;br /&gt;
*I worked with my homework partners Hayden, Mary, and Nicole. We mostly communicated via phone call or text message.&lt;br /&gt;
&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 01:21, 14 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
* LMU BioDB 2017. (2017). Week 11. Retrieved November 13, 2017, from https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_11&lt;br /&gt;
* Kohavi, Ron; Longbotham, Roger (2015). &amp;quot;Online Controlled Experiments and A/B Tests&amp;quot;. Accessed November 13, 2017, from http://www.exp-platform.com/Documents/2015%20Online%20Controlled%20Experiments_EncyclopediaOfMLDM.pdf&lt;br /&gt;
*Gary William Flake: The Computational Beauty of Nature: Computer Explorations of Fractals, Chaos, Complex Systems, and Adaptation. MIT Press 1998, ISBN 978-0-262-56127-3&lt;br /&gt;
*IBM (2017), IBM TeaLeaf, Accessed on November 13, 2017 from https://www.ibm.com/customer-engagement/tealeaf&lt;br /&gt;
*Net Promoter (2017), Net Promoter, accessed on November 13, 2017 from https://www.netpromoter.com/know/&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4556</id>
		<title>ArashLari Week 11</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4556"/>
				<updated>2017-11-14T09:53:45Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Development Terms */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Development Terms==&lt;br /&gt;
*Read: &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039;&lt;br /&gt;
*By: Lassi A. Liikkanen&lt;br /&gt;
This article introduced me to many terms I hadn&amp;#039;t heard in respect to design before, but the author did a good job of explaining them so I didn&amp;#039;t need to consult outside sources very much. I had heard of most of the analytics products before but there were a few I wasn&amp;#039;t familiar with. The following terms are defined according to my understanding after reading their definitions.&lt;br /&gt;
&lt;br /&gt;
*Generative Design&lt;br /&gt;
**A development process that is akin to evolution. The process is to set out design goals and an initial schema, and then go through several permutations of variation until arriving at the best option.  (Flake, 1998)&lt;br /&gt;
*Heat Maps&lt;br /&gt;
**Heat maps in regards to design are basically the same as heat maps in terms of population movement. It is a visual representation of where the average users cursor hovers and clicks and for what amount of time. (Liikkanen, 2017)&lt;br /&gt;
*User Screen Recordings&lt;br /&gt;
**A user screen recording is a literal video of the individual user&amp;#039;s screen during their session on the application. (Liikkanen, 2017)&lt;br /&gt;
*A/B Tests&lt;br /&gt;
** A controlled test with two variants. This is used to compare different potential design layouts and choose the most effective elements from them. (Kohavi, Longbotham 2015)&lt;br /&gt;
*Behavioural Analytics&lt;br /&gt;
**The contextual information around a users session on an application, including information such as the usage log, click-stream data, average time spent on each page, etc. (Liikkanen, 2017)&lt;br /&gt;
*Assistive Tools&lt;br /&gt;
** Tools that make tasks easier for humans but still require a human interaction. (Liikkanen, 2017)&lt;br /&gt;
*Agentive Tools&lt;br /&gt;
** Tools that do tasks for humans and eliminate the need for the humans to do anything related to the task. (Liikkanen, 2017)&lt;br /&gt;
*Net Promoter Score&lt;br /&gt;
** A measure from -100 to 100 of a customer&amp;#039;s willingness to refer a product or company to a peer. (NetPromoter, 2017)&lt;br /&gt;
*KISSmetrics&lt;br /&gt;
** A behavioural analytics service that provides automated tools for interpreting data from customers. (Kissmetrics, 2017).&lt;br /&gt;
*IBM TeaLeaf&lt;br /&gt;
**A company that IBM acquired that is focused on bettering customer experience through behavioural analytics. (IBM, 2017).&lt;br /&gt;
&lt;br /&gt;
==Outline and Presentation==&lt;br /&gt;
===What is Data Driven Design?===&lt;br /&gt;
*Traditionally, products were designed by the designers intuition and opinion&lt;br /&gt;
**This is because collecting information about user activity has been difficult until recently&lt;br /&gt;
*The rise of technology and internet based services has led to evidenced-based design&lt;br /&gt;
**Companies and developers want to know that their intended users will be able to easily use their service before it affects sales&lt;br /&gt;
*Designing based off of results empirical user evidence is called data driven design&lt;br /&gt;
**There are assistive and agentive generative tools to help creative tasks&lt;br /&gt;
***A generative design process basically means designing and redesigning based on how the previous iteration was received&lt;br /&gt;
**It’s basically an assortment of tools at the disposal of the designers and the developers that they can use in a multitude of ways to gauge how effective their design is.&lt;br /&gt;
**The basic idea of this design philosophy is to collect data, combine it with other data, and analyze it for implementation in the final design&lt;br /&gt;
=== Data Driven Design of Web Services ===&lt;br /&gt;
*Web interaction design is a field that utilizes data design driven solutions frequently&lt;br /&gt;
**Major internet companies often build their own experiment-management platforms so they can run many different experiments in parallel with automation&lt;br /&gt;
*Data-collection can be separated into two types of solutions: Active and Passive&lt;br /&gt;
**Active data collection is reliant on user input, and as such it’s considered qualitative&lt;br /&gt;
***It doesn’t really fit the mold of DDD very well if the scale is large&lt;br /&gt;
***Surveys are often plagued with many issues such as reluctance to participate and low quality answers that don’t provide very much insight&lt;br /&gt;
***In smaller cases it is very useful, such as using an online focus group to get detailed reactions and responses&lt;br /&gt;
****This is costly, which is why large corporations don’t often do this&lt;br /&gt;
**Passive data collection, or passive tracking is any kind of recording of user activity&lt;br /&gt;
***Screen recordings, heat maps, experiment management, and descriptive behavioral analytics are some passive tracking tools&lt;br /&gt;
****Screen recordings are full recordings of the users screen for later analysis.&lt;br /&gt;
****Provides a very detailed view and a lot of useful implementation&lt;br /&gt;
****However, raises privacy and ethical concerns and can’t really be automated to gain insight&lt;br /&gt;
**Heat maps are a way to visualize the most frequently clicked on and hovered on spots of a page&lt;br /&gt;
***It isn’t always very clear because some pages might be context specific, but it still can provide enough information to help optimize the design of the page &lt;br /&gt;
**Experiment management is basically having 2 or more types of designs be tested on to find which features and design choices should be kept or removed&lt;br /&gt;
***It allows developers to find fail new ideas quickly so they don’t have to waste time with subpar designs&lt;br /&gt;
***They can be automated but their shortcoming is the numbers aren’t always that insightful&lt;br /&gt;
**Behavioral analytics are the precursor to all current DDD solutions&lt;br /&gt;
***It’s all the contextual data related to the visit, such as the amount of time spent and on what pages, what elements were clicked and in what order, etc.&lt;br /&gt;
***This information is more useful for business and marketing decisions rather than design decisions.&lt;br /&gt;
****Many companies offer analytics solutions for developers&lt;br /&gt;
*****Google is the biggest by far, but there are others such as Adobe Analytics, KISSMetrics, and IBM Tealeaf&lt;br /&gt;
=== Conclusion ===&lt;br /&gt;
*Data driven design provides designers a strong incentive to adopt a hypothesis-driven approach to design research&lt;br /&gt;
**Having a clear hypothesis is important as it will affect the way one interprets data and identify which results are the most significant&lt;br /&gt;
**The age of Data Driven Design draws heavily upon designer moral, integrity, and candor. &lt;br /&gt;
***Ethics of how data is collected and used is very important, and consent is key in ethical data acquisition. &lt;br /&gt;
*The future of data driven design will be with tools that couple seamlessly with design processes, be adaptive to change, and show maturity in addressing ethical questions.&lt;br /&gt;
**Designers will embrace more quantitative data as tools that allow for scalability become available&lt;br /&gt;
**Design will introduce assistive and agentive tools that do things with us and for us&lt;br /&gt;
*What will we use for our project?&lt;br /&gt;
**We won’t use any of the passive tools directly&lt;br /&gt;
***Although useful, we do not have the means to get enough different users to get fruitful information using these methods&lt;br /&gt;
***Although we might implement experiment-management within our own small group and see what we collectively thinks works best&lt;br /&gt;
**We will be using active data collection, and ask our fellow classmates to browse our site and give us feedback as they use it&lt;br /&gt;
***This level of interactivity with the end-user provide useful insight&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Acknowledgements ==&lt;br /&gt;
*I worked with my homework partners Hayden, Mary, and Nicole. We mostly communicated via phone call or text message.&lt;br /&gt;
&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 01:21, 14 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
* LMU BioDB 2017. (2017). Week 11. Retrieved November 13, 2017, from https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_11&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4548</id>
		<title>ArashLari Week 11</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4548"/>
				<updated>2017-11-14T09:29:11Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Outline and Presentation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Development Terms==&lt;br /&gt;
*Read: &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039;&lt;br /&gt;
*By: Lassi A. Liikkanen&lt;br /&gt;
&lt;br /&gt;
==Outline and Presentation==&lt;br /&gt;
===What is Data Driven Design?===&lt;br /&gt;
*Traditionally, products were designed by the designers intuition and opinion&lt;br /&gt;
**This is because collecting information about user activity has been difficult until recently&lt;br /&gt;
*The rise of technology and internet based services has led to evidenced-based design&lt;br /&gt;
**Companies and developers want to know that their intended users will be able to easily use their service before it affects sales&lt;br /&gt;
*Designing based off of results empirical user evidence is called data driven design&lt;br /&gt;
**There are assistive and agentive generative tools to help creative tasks&lt;br /&gt;
***A generative design process basically means designing and redesigning based on how the previous iteration was received&lt;br /&gt;
**It’s basically an assortment of tools at the disposal of the designers and the developers that they can use in a multitude of ways to gauge how effective their design is.&lt;br /&gt;
**The basic idea of this design philosophy is to collect data, combine it with other data, and analyze it for implementation in the final design&lt;br /&gt;
=== Data Driven Design of Web Services ===&lt;br /&gt;
*Web interaction design is a field that utilizes data design driven solutions frequently&lt;br /&gt;
**Major internet companies often build their own experiment-management platforms so they can run many different experiments in parallel with automation&lt;br /&gt;
*Data-collection can be separated into two types of solutions: Active and Passive&lt;br /&gt;
**Active data collection is reliant on user input, and as such it’s considered qualitative&lt;br /&gt;
***It doesn’t really fit the mold of DDD very well if the scale is large&lt;br /&gt;
***Surveys are often plagued with many issues such as reluctance to participate and low quality answers that don’t provide very much insight&lt;br /&gt;
***In smaller cases it is very useful, such as using an online focus group to get detailed reactions and responses&lt;br /&gt;
****This is costly, which is why large corporations don’t often do this&lt;br /&gt;
**Passive data collection, or passive tracking is any kind of recording of user activity&lt;br /&gt;
***Screen recordings, heat maps, experiment management, and descriptive behavioral analytics are some passive tracking tools&lt;br /&gt;
****Screen recordings are full recordings of the users screen for later analysis.&lt;br /&gt;
****Provides a very detailed view and a lot of useful implementation&lt;br /&gt;
****However, raises privacy and ethical concerns and can’t really be automated to gain insight&lt;br /&gt;
**Heat maps are a way to visualize the most frequently clicked on and hovered on spots of a page&lt;br /&gt;
***It isn’t always very clear because some pages might be context specific, but it still can provide enough information to help optimize the design of the page &lt;br /&gt;
**Experiment management is basically having 2 or more types of designs be tested on to find which features and design choices should be kept or removed&lt;br /&gt;
***It allows developers to find fail new ideas quickly so they don’t have to waste time with subpar designs&lt;br /&gt;
***They can be automated but their shortcoming is the numbers aren’t always that insightful&lt;br /&gt;
**Behavioral analytics are the precursor to all current DDD solutions&lt;br /&gt;
***It’s all the contextual data related to the visit, such as the amount of time spent and on what pages, what elements were clicked and in what order, etc.&lt;br /&gt;
***This information is more useful for business and marketing decisions rather than design decisions.&lt;br /&gt;
****Many companies offer analytics solutions for developers&lt;br /&gt;
*****Google is the biggest by far, but there are others such as Adobe Analytics, KISSMetrics, and IBM Tealeaf&lt;br /&gt;
=== Conclusion ===&lt;br /&gt;
*Data driven design provides designers a strong incentive to adopt a hypothesis-driven approach to design research&lt;br /&gt;
**Having a clear hypothesis is important as it will affect the way one interprets data and identify which results are the most significant&lt;br /&gt;
**The age of Data Driven Design draws heavily upon designer moral, integrity, and candor. &lt;br /&gt;
***Ethics of how data is collected and used is very important, and consent is key in ethical data acquisition. &lt;br /&gt;
*The future of data driven design will be with tools that couple seamlessly with design processes, be adaptive to change, and show maturity in addressing ethical questions.&lt;br /&gt;
**Designers will embrace more quantitative data as tools that allow for scalability become available&lt;br /&gt;
**Design will introduce assistive and agentive tools that do things with us and for us&lt;br /&gt;
*What will we use for our project?&lt;br /&gt;
**We won’t use any of the passive tools directly&lt;br /&gt;
***Although useful, we do not have the means to get enough different users to get fruitful information using these methods&lt;br /&gt;
***Although we might implement experiment-management within our own small group and see what we collectively thinks works best&lt;br /&gt;
**We will be using active data collection, and ask our fellow classmates to browse our site and give us feedback as they use it&lt;br /&gt;
***This level of interactivity with the end-user provide useful insight&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Acknowledgements ==&lt;br /&gt;
*I worked with my homework partners Hayden, Mary, and Nicole. We mostly communicated via phone call or text message.&lt;br /&gt;
&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 01:21, 14 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
* LMU BioDB 2017. (2017). Week 11. Retrieved November 13, 2017, from https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_11&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4546</id>
		<title>ArashLari Week 11</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_11&amp;diff=4546"/>
				<updated>2017-11-14T09:21:52Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: preparing page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Development Terms==&lt;br /&gt;
*Read: &amp;#039;&amp;#039;The Data-Driven Design Era in Professional Web Design&amp;#039;&amp;#039;&lt;br /&gt;
*By: Lassi A. Liikkanen&lt;br /&gt;
&lt;br /&gt;
==Outline and Presentation==&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Acknowledgements ==&lt;br /&gt;
*I worked with my homework partners Hayden, Mary, and Nicole. We mostly communicated via phone call or text message.&lt;br /&gt;
&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 01:21, 14 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* Liikkanen, L. (2017). The Data-Driven Design Era in Professional Web Design. Accessed November 13, 2017, from http://delivery.acm.org/10.1145/3130000/3121355/p52-liikkanen.pdf?ip=157.242.223.254&amp;amp;id=3121355&amp;amp;acc=ACTIVE%20SERVICE&amp;amp;key=80B0E63637265656%2E958C566062FD1C18%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35&amp;amp;CFID=829067610&amp;amp;CFTOKEN=20249523&amp;amp;__acm__=1510614806_1e8b314e23f771f9b139d99596801365&lt;br /&gt;
* LMU BioDB 2017. (2017). Week 11. Retrieved November 13, 2017, from https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_11&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Template:ArashLari&amp;diff=4545</id>
		<title>Template:ArashLari</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Template:ArashLari&amp;diff=4545"/>
				<updated>2017-11-14T09:17:31Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[User:ArashLari|Arash Lari]]&lt;br /&gt;
&lt;br /&gt;
[[Main_Page| BIOL/CMSI 367-01: Biological Databases Fall 2017]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Assignments&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
*[[Week_1|Week 1]]&lt;br /&gt;
*[[Week_2|Week 2]]&lt;br /&gt;
*[[Week_3|Week 3]]&lt;br /&gt;
*[[Week_4|Week 4]]&lt;br /&gt;
*[[Week_5|Week 5]]&lt;br /&gt;
*[[Week_6|Week 6]]&lt;br /&gt;
*[[Week_7|Week 7]]&lt;br /&gt;
*[[Week_8|Week 8]]&lt;br /&gt;
*[[Week_9|Week 9]]&lt;br /&gt;
*[[Week_10|Week 10]]&lt;br /&gt;
*[[Week_11|Week 11]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Journal Entries&amp;#039;&amp;#039;&amp;#039;:&lt;br /&gt;
*[[ArashLari_Week_2|ArashLari Week 2]]&lt;br /&gt;
*[[ArashLari_Week_3|ArashLari Week 3]]&lt;br /&gt;
*[[ArashLari_Week_4|ArashLari Week 4]]&lt;br /&gt;
*[[ArashLari_Week_5|ArashLari Week 5]]&lt;br /&gt;
*[[ArashLari_Week_6|ArashLari Week 6]]&lt;br /&gt;
*[[ArashLari_Week_7|ArashLari Week 7]]&lt;br /&gt;
*[[ArashLari_Week_8|ArashLari Week 8]]&lt;br /&gt;
*[[ArashLari_Week_9|ArashLari Week 9]]&lt;br /&gt;
*[[ArashLari_Week_10|ArashLari Week 10]]&lt;br /&gt;
*[[ArashLari_Week_11|ArashLari Week 11]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Shared Journals&amp;#039;&amp;#039;&amp;#039;:&lt;br /&gt;
*[[Class_Journal_Week_1|ArashLari Week 1 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_2|ArashLari Week 2 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_3|ArashLari Week 3 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_4|ArashLari Week 4 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_5|ArashLari Week 5 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_6|ArashLari Week 6 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_7|ArashLari Week 7 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_8|ArashLari Week 8 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_9|ArashLari Week 9 Journal]]&lt;br /&gt;
*[[Class_Journal_Week_10|ArashLari Week 10 Journal]]&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Class_Journal_Week_10&amp;diff=3988</id>
		<title>Class Journal Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=Class_Journal_Week_10&amp;diff=3988"/>
				<updated>2017-11-07T04:11:35Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* QLanners Responses */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Class Journal Week 10=&lt;br /&gt;
==Hayden Hinsch&amp;#039;s Responses==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{hhinsch}}&lt;br /&gt;
&lt;br /&gt;
==Mary Balducci&amp;#039;s Responses==&lt;br /&gt;
#I would want for my teammates to be available if I have questions about the work, and also to feel like they can ask me questions. I would want us all to share equal amounts of the work, and to be able to get in touch with each other if we need help with something.&lt;br /&gt;
#I think communication makes teamwork go smoothly. If we are all able to tell each other what we&amp;#039;re working on and how we&amp;#039;re doing it, I think it helps everyone better understand the project being done. This also includes being responsive to questions and figuring out who is responsible for each aspect of the project together.&lt;br /&gt;
#I think teamwork does not go smoothly when members of the team are not responsive. I think it&amp;#039;s harder when I&amp;#039;m not entirely sure what another person in my group is doing, or if I have a question and they are not available to answer it.&lt;br /&gt;
&lt;br /&gt;
[[User:Mbalducc|Mbalducc]] ([[User talk:Mbalducc|talk]]) 07:44, 3 November 2017 (PDT)&lt;br /&gt;
&lt;br /&gt;
==Zachary Van Ysseldyk&amp;#039;s Responses==&lt;br /&gt;
#As far as characteristics for a teammate, I value those who do not procrastinate and plan out how the assignment will get done to avoid unnecessary stress. Stringing along the same thought, I think that communication is crucial so that every person on the team is on the same page. I would also value those who assume the same amount of work as everybody else so that we all get a fair and well deserved grade.&lt;br /&gt;
#Bleeding in from question 1, I think that solid communication and a laid out plan will help the project go smoothly. Knowing when things will get done and how long they will take will help for smooth project completion.&lt;br /&gt;
#On the other hand, poor communication will greatly negatively affect a project. People might be doing the same things, people might not understand what they are doing  which leads to frustration and division among the team. Also if somebody does not put in a sufficient amount of effort, this will anger others as the person who didn&amp;#039;t do the the work should not receive the same letter grade.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[User:Zvanysse|Zvanysse]] ([[User talk:Zvanysse|talk]]) 13:36, 5 November 2017 (PST)&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
{{Template:Zvanysse}}&lt;br /&gt;
&lt;br /&gt;
==Dina Bashoura&amp;#039;s Responses==&lt;br /&gt;
#I would like a partner who is well equipped in computer science, since I am lagging in that department. I also would like my partner to be good at communicating so that we can distinguish who should do what task and work together to make the overall project flow. &lt;br /&gt;
# Things like communication, trust, reliability, and good team chemistry make teamwork go smoothly. &lt;br /&gt;
#Things like lack of communication, doing sections not assigned to you or not assigning sections at all, not showing up to group meetings, and not being prepared when group meetings take place are things that make teamwork fail.&lt;br /&gt;
[[User:Dbashour|Dbashour]] ([[User talk:Dbashour|talk]]) 14:45, 6 November 2017 (PST) &lt;br /&gt;
{{template:dbashour}}&lt;br /&gt;
&lt;br /&gt;
==Eddie Azinge&amp;#039;s Responses==&lt;br /&gt;
# I don&amp;#039;t find myself requiring very much from my teammates, just that the work that they hold themselves accountable for gets done at some point or another, and that inconsistencies in their work do not end up propogating upwards and affecting the status of the entire group, specifically because everyone has their own circumstances and priorities; as long as they deliver on their promises they&amp;#039;re good in my book.&lt;br /&gt;
# Communication is key to teamwork; but trust and flexibility also play huge roles as well. &lt;br /&gt;
# Somewhat antithetical to the last question, a lack of trust and need to keep constant tabs on the members of the project often leads to rushed work, resentment, and dissidence within the team.&lt;br /&gt;
[[User:Cazinge|Cazinge]] ([[User talk:Cazinge|talk]]) 15:46, 6 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Edward Bachoura&amp;#039;s Response==&lt;br /&gt;
# I am looking for teammates that are flexible with their schedules so that we can actually find time to meet. Also, looking for teammates that are accountable for themselves.&lt;br /&gt;
# I find it important that whenever you work on a team, there should be some fun involved with the assignment, no matter the topic. When everybody is happy, it is usually easier to do the work at hand.&lt;br /&gt;
# Teamwork doesn&amp;#039;t go smoothly when someone is unaccountable and makes themselves become more a negative weight rather than a help on the team.&lt;br /&gt;
[[User:Ebachour|Ebachour]] ([[User talk:Ebachour|talk]]) 16:54, 6 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
==Antonio Porras&amp;#039;s Responses==&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;What kinds of characteristics do you want in your teammates, and why?&amp;#039;&amp;#039;&amp;#039; I look for teammates who are willing to take initiative and are able to communicate effectively about what needs to get done and what needs to be changed. Team members who aren&amp;#039;t willing to speak their minds makes the process difficult and I look for these qualities because I want our group to achieve our goal and do so effectively.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;What kinds of things make teamwork go smoothly?&amp;#039;&amp;#039;&amp;#039; Communication is extremely important in my opinion and there has to be someone taking charge with respect to delegating some tasks. I actually prefer not to be in this position but instead delegated a task because once I have some responsibility I take it seriously as it represents my work ethic.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;What kinds of things make teamwork not go so smoothly?&amp;#039;&amp;#039;&amp;#039; Team members who put off work put a lot of pressure on the entire team. In addition, teams that don&amp;#039;t have a uniform direction can be misdirected and may even miss the target in terms of goals.&lt;br /&gt;
&lt;br /&gt;
[[User:Aporras1|Aporras1]] ([[User talk:Aporras1|talk]]) 17:44, 6 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
{{Template:Aporras1Links}}&lt;br /&gt;
&lt;br /&gt;
==Emma Tyrnauer&amp;#039;s Responses==&lt;br /&gt;
#The kind of characteristics that I want in my teammates are good communication skills and responsibility over their contributions (in terms of meeting deadlines and asking for help when it is needed). Furthermore, I think being detail oriented is important in group setting to ensure everything is being completed properly. &lt;br /&gt;
#Good communication and collaboration makes teamwork go smoothly. The ability to divide and conquer is very important so that while the assignment is completed in a group setting and collaboration occurs consistently throughout the process, the strengths of each team member are being used and emphasized. &lt;br /&gt;
#Bad communication and a lack of responsibility make teamwork go not so smoothly. Also, not being able to trust your teammates and ask for help when it is needed represents poor teamwork.&lt;br /&gt;
&lt;br /&gt;
[[User:Emmatyrnauer|Emmatyrnauer]] ([[User talk:Emmatyrnauer|talk]]) 17:55, 6 November 2017 (PST)&lt;br /&gt;
&lt;br /&gt;
{{Emmatyrnauer}} &lt;br /&gt;
&lt;br /&gt;
[[Category:Shared]]&lt;br /&gt;
[[Category:Journal Entry]]&lt;br /&gt;
&lt;br /&gt;
==Blair Hamilton&amp;#039;s Response==&lt;br /&gt;
#What kinds of characteristics do you want in your teammates, and why?&lt;br /&gt;
#*For a teammate I would like organization when it comes to deadlines, but also able to work independently of the group. Being able to disperse tasks is very helpful when it comes to big projects, so having a teammate who appreciated independent work, with good communication can be super helpful. I also would love a teammate who can critique my work as well in order to make sure the project as a whole gets done well and accurately.&lt;br /&gt;
#What kinds of things make teamwork go smoothly?&lt;br /&gt;
#*In order for the project to smoothly, communication is a big part. If a partner is being silent or not asking questions when he/she is confused, then the project suffers.&lt;br /&gt;
#What kinds of things make teamwork not go so smoothly?&lt;br /&gt;
#*Partners who don&amp;#039;t contribute, don&amp;#039;t ask questions and don&amp;#039;t follow up make projects go not-so-smoothly. Deadlines and helping the entire group project makes it go quicker and much easier!&lt;br /&gt;
&lt;br /&gt;
[[User:Bhamilton18|Bhamilton18]] ([[User talk:Bhamilton18|talk]]) 18:49, 6 November 2017 (PST)&lt;br /&gt;
{{Bhamilton18}}&lt;br /&gt;
&lt;br /&gt;
==QLanners Responses==&lt;br /&gt;
#There are a number of characteristics that I want in a good teammate, but among the most important ones are accountability and good communication. Group projects are much more effective when all of the partners in the group do the tasks assigned to them when they say they will. Furthermore, when problems do arise (as they always do), good communication skills can help limit these problems and make them much more manageable.&lt;br /&gt;
#Perhaps the most important thing to make teamwork go smoothly is effective planning. If all of the tasks can be mapped out, and everyone is given a job to complete by a certain deadline, the overall project will progress much faster and with fewer complications.&lt;br /&gt;
#There are several things that can make teamwork not go smoothly, but poor communication is definitely the number one culprit. Without communication, it is impossible to even set times to meet and work on the project. And without meetings and communication, team members become confused as to what they should be doing and that results in partners either not doing their work, or doing a poor job of it.&lt;br /&gt;
&lt;br /&gt;
[[User:Qlanners|Qlanners]] ([[User talk:Qlanners|talk]]) 19:51, 6 November 2017 (PST)&lt;br /&gt;
{{Template:QLannersLinks}}&lt;br /&gt;
&lt;br /&gt;
== Arash Lari&amp;#039;s Responses==&lt;br /&gt;
# I want my teammate and I to be able to have open, honest communication with each other and both of a drive and motivation to submit quality work. If we agree on the latter, and according to the former, then any other issues that come up would be resolved easily.&lt;br /&gt;
# As mentioned previously, communication is vital. To add to that, I would say reaching an agreement on the work dynamic is important as well. It&amp;#039;s important that each member of the team agrees on what their responsibilities are in order to achieve optimal performance.&lt;br /&gt;
# Again, if teammates don&amp;#039;t communicate with each other and try to organize time well it can lead to a lot of stressed out last minute work. &lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 20:11, 6 November 2017 (PST)&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=File:Work.zip&amp;diff=3977</id>
		<title>File:Work.zip</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=File:Work.zip&amp;diff=3977"/>
				<updated>2017-11-07T02:20:03Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: ArashLari uploaded a new version of File:Work.zip&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;All the work files for the Week 10 assignment&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3976</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3976"/>
				<updated>2017-11-07T02:18:00Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: summary paragraph&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
[[File:Work.zip]]&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;Note: for this to work, you must replace all instances of &amp;quot;#DIV/0&amp;quot; with empty text, or else the program will not run properly.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
For this section, I chose &amp;#039;&amp;#039;&amp;#039;Profile 2&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* I chose this profile because it seemed to have an interesting reaction to cold shock. It showed a strong negative expression change at minute 30, but at minute 90 it seems that the genes seemed to have &amp;quot;bounced back&amp;quot; and expressed a similar (but less extreme) change in the positive range. This is shown by the profile type of &amp;quot;(0, -2, -2, 0, 1  0)&amp;quot;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There are 49 genes assigned to this profile.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There were 18.7 genes expected, so more genes than expected were effected.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* The p value for the enrichment of genes in this profile is 2.1 E-9, so very small.&lt;br /&gt;
  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  &lt;br /&gt;
 There were 9 genes associated with this profile at p &amp;lt;0.05.&lt;br /&gt;
The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 There were actually NO GO terms associated with a corrected p value &amp;lt; 0.05. This makes sense as dHMO1 is a special case.&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
==== My GO Terms defined ====&lt;br /&gt;
All of this information was taken directly from [http://geneontology.org http://geneontology.org].&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0031399&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: regulation of protein modification process&lt;br /&gt;
 Ontology: biological_process&lt;br /&gt;
 Definition: Any process that modulates the frequency, rate or extent of the covalent alteration of one or more amino acid residues within a protein.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0050794&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: regulation of cellular process&lt;br /&gt;
 Ontology: biological_process&lt;br /&gt;
 Definition: Any process that modulates the frequency, rate or extent of a cellular process, any of those that are carried out at the cellular level, but are not necessarily restricted to a single cell. For example, cell communication occurs among more than one cell, but occurs at the cellular level.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0098588&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: bounding membrane of organelle&lt;br /&gt;
 Ontology: cellular_component&lt;br /&gt;
 Definition: The lipid bilayer that forms the outer-most layer of an organelle.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0050789&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: regulation of biological process&lt;br /&gt;
 Ontology: biological_process&lt;br /&gt;
 Definition: Any process that modulates the frequency, rate or extent of a biological process. Biological processes are regulated by many means; examples include the control of gene expression, protein modification or interaction with a protein or substrate molecule.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0006796&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: phosphate-containing compound metabolic process&lt;br /&gt;
 Ontology: biological_process&lt;br /&gt;
 Definition: The chemical reactions and pathways involving the phosphate group, the anion or salt of any phosphoric acid.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0005794&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: Golgi apparatus&lt;br /&gt;
 Ontology: cellular_component&lt;br /&gt;
 Definition: A compound membranous cytoplasmic organelle of eukaryotic cells, consisting of flattened, ribosome-free vesicles arranged in a more or less regular stack. The Golgi apparatus differs from the endoplasmic reticulum in often having slightly thicker membranes, appearing in sections as a characteristic shallow semicircle so that the convex side (cis or entry face) abuts the endoplasmic reticulum, secretory vesicles emerging from the concave side (trans or exit face). In vertebrate cells there is usually one such organelle, while in invertebrates and plants, where they are known usually as dictyosomes, there may be several scattered in the cytoplasm. The Golgi apparatus processes proteins produced on the ribosomes of the rough endoplasmic reticulum; such processing includes modification of the core oligosaccharides of glycoproteins, and the sorting and packaging of proteins for transport to a variety of cellular locations. Three different regions of the Golgi are now recognized both in terms of structure and function: cis, in the vicinity of the cis face, trans, in the vicinity of the trans face, and medial, lying between the cis and trans regions.&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
== Summary of Knowledge ==&lt;br /&gt;
 After processing all of the data from the spreadsheets of dHMO1, and reading the definitions of the genes most effected in profile #2, I learned some interesting information. It appears that dHMO1 &amp;quot;turns off&amp;quot; genes related to protein inscription when it&amp;#039;s cold in order to conserve energy, and when it warms up again it seems to kick it into full gear in order to compensate for when it was too cold. Of course my rudimentary, limited knowledge of biology limits my understanding of this process, but this seems to be the main idea.&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3973</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3973"/>
				<updated>2017-11-07T02:08:38Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Electronic Notebook */ added GO terms&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
[[File:Work.zip]]&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;Note: for this to work, you must replace all instances of &amp;quot;#DIV/0&amp;quot; with empty text, or else the program will not run properly.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
For this section, I chose &amp;#039;&amp;#039;&amp;#039;Profile 2&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* I chose this profile because it seemed to have an interesting reaction to cold shock. It showed a strong negative expression change at minute 30, but at minute 90 it seems that the genes seemed to have &amp;quot;bounced back&amp;quot; and expressed a similar (but less extreme) change in the positive range. This is shown by the profile type of &amp;quot;(0, -2, -2, 0, 1  0)&amp;quot;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There are 49 genes assigned to this profile.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There were 18.7 genes expected, so more genes than expected were effected.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* The p value for the enrichment of genes in this profile is 2.1 E-9, so very small.&lt;br /&gt;
  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  &lt;br /&gt;
 There were 9 genes associated with this profile at p &amp;lt;0.05.&lt;br /&gt;
The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 There were actually NO GO terms associated with a corrected p value &amp;lt; 0.05. This makes sense as dHMO1 is a special case.&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
==== My GO Terms defined ====&lt;br /&gt;
All of this information was taken directly from [http://geneontology.org http://geneontology.org].&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0031399&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: regulation of protein modification process&lt;br /&gt;
 Ontology: biological_process&lt;br /&gt;
 Definition: Any process that modulates the frequency, rate or extent of the covalent alteration of one or more amino acid residues within a protein.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0050794&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: regulation of cellular process&lt;br /&gt;
 Ontology: biological_process&lt;br /&gt;
 Definition: Any process that modulates the frequency, rate or extent of a cellular process, any of those that are carried out at the cellular level, but are not necessarily restricted to a single cell. For example, cell communication occurs among more than one cell, but occurs at the cellular level.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0098588&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: bounding membrane of organelle&lt;br /&gt;
 Ontology: cellular_component&lt;br /&gt;
 Definition: The lipid bilayer that forms the outer-most layer of an organelle.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0050789&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: regulation of biological process&lt;br /&gt;
 Ontology: biological_process&lt;br /&gt;
 Definition: Any process that modulates the frequency, rate or extent of a biological process. Biological processes are regulated by many means; examples include the control of gene expression, protein modification or interaction with a protein or substrate molecule.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0006796&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: phosphate-containing compound metabolic process&lt;br /&gt;
 Ontology: biological_process&lt;br /&gt;
 Definition: The chemical reactions and pathways involving the phosphate group, the anion or salt of any phosphoric acid.&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Accession: GO:0005794&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Name: Golgi apparatus&lt;br /&gt;
 Ontology: cellular_component&lt;br /&gt;
 Definition: A compound membranous cytoplasmic organelle of eukaryotic cells, consisting of flattened, ribosome-free vesicles arranged in a more or less regular stack. The Golgi apparatus differs from the endoplasmic reticulum in often having slightly thicker membranes, appearing in sections as a characteristic shallow semicircle so that the convex side (cis or entry face) abuts the endoplasmic reticulum, secretory vesicles emerging from the concave side (trans or exit face). In vertebrate cells there is usually one such organelle, while in invertebrates and plants, where they are known usually as dictyosomes, there may be several scattered in the cytoplasm. The Golgi apparatus processes proteins produced on the ribosomes of the rough endoplasmic reticulum; such processing includes modification of the core oligosaccharides of glycoproteins, and the sorting and packaging of proteins for transport to a variety of cellular locations. Three different regions of the Golgi are now recognized both in terms of structure and function: cis, in the vicinity of the cis face, trans, in the vicinity of the trans face, and medial, lying between the cis and trans regions.&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3969</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3969"/>
				<updated>2017-11-07T01:45:07Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Electronic Notebook */ updated answers&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
[[File:Work.zip]]&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;Note: for this to work, you must replace all instances of &amp;quot;#DIV/0&amp;quot; with empty text, or else the program will not run properly.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
For this section, I chose &amp;#039;&amp;#039;&amp;#039;Profile 2&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* I chose this profile because it seemed to have an interesting reaction to cold shock. It showed a strong negative expression change at minute 30, but at minute 90 it seems that the genes seemed to have &amp;quot;bounced back&amp;quot; and expressed a similar (but less extreme) change in the positive range. This is shown by the profile type of &amp;quot;(0, -2, -2, 0, 1  0)&amp;quot;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There are 49 genes assigned to this profile.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There were 18.7 genes expected, so more genes than expected were effected.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* The p value for the enrichment of genes in this profile is 2.1 E-9, so very small.&lt;br /&gt;
  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  &lt;br /&gt;
 There were 9 genes associated with this profile at p &amp;lt;0.05.&lt;br /&gt;
The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 There were actually NO GO terms associated with a corrected p value &amp;lt; 0.05. This makes sense as dHMO1 is a special case.&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3882</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3882"/>
				<updated>2017-11-06T03:33:54Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Electronic Notebook */ answering more questions from part 5&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
[[File:Work.zip]]&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;Note: for this to work, you must replace all instances of &amp;quot;#DIV/0&amp;quot; with empty text, or else the program will not run properly.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
For this section, I chose &amp;#039;&amp;#039;&amp;#039;Profile 2&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* I chose this profile because it seemed to have an interesting reaction to cold shock. It showed a strong negative expression change at minute 30, but at minute 90 it seems that the genes seemed to have &amp;quot;bounced back&amp;quot; and expressed a similar (but less extreme) change in the positive range.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There are 157 genes that belong to this profile.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There were around a 1000 genes that passed the p-value filter, so around that number of genes. &lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* TODO&lt;br /&gt;
  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  &lt;br /&gt;
 There were 9 genes associated with this profile at p &amp;lt;0.05.&lt;br /&gt;
The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 There were actually NO GO terms associated with a corrected p value &amp;lt; 0.05. This makes sense as dHMO1 is a special case.&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3881</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3881"/>
				<updated>2017-11-06T03:27:28Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Electronic Notebook */ Answering first questions about profile 2&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
[[File:Work.zip]]&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;Note: for this to work, you must replace all instances of &amp;quot;#DIV/0&amp;quot; with empty text, or else the program will not run properly.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
For this section, I chose &amp;#039;&amp;#039;&amp;#039;Profile 2&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* I chose this profile because it seemed to have an interesting reaction to cold shock. It showed a strong negative expression change at minute 30, but at minute 90 it seems that the genes seemed to have &amp;quot;bounced back&amp;quot; and expressed a similar (but less extreme) change in the positive range.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There are 157 genes that belong to this profile.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* There were around a 1000 genes that passed the p-value filter, so around that number of genes. &lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* TODO&lt;br /&gt;
  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3880</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3880"/>
				<updated>2017-11-06T03:13:15Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* File */ this is a link to all the files used for this assignment&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
[[File:Work.zip]]&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;Note: for this to work, you must replace all instances of &amp;quot;#DIV/0&amp;quot; with empty text, or else the program will not run properly.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3879</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3879"/>
				<updated>2017-11-06T03:12:05Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* File */ added my zip file&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
[[File:Work.zip] This is a link to all the files used for this assignment]&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;Note: for this to work, you must replace all instances of &amp;quot;#DIV/0&amp;quot; with empty text, or else the program will not run properly.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3878</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3878"/>
				<updated>2017-11-06T03:10:56Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Electronic Notebook */ added a special case for #DIV/0&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;Note: for this to work, you must replace all instances of &amp;quot;#DIV/0&amp;quot; with empty text, or else the program will not run properly.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3877</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3877"/>
				<updated>2017-11-06T03:08:03Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Clustering and GO Term Enrichment with stem */ added our special case&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** &amp;#039;&amp;#039;&amp;#039;It should be noted that because dHMO1 is a special case, we will use the regular p-value instead of the B-H corrected value.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3876</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3876"/>
				<updated>2017-11-06T03:06:41Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Electronic Notebook */ replaced all instances of &amp;quot;(STRAIN)&amp;quot; with &amp;quot;dHMO1&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;dHMO1_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;dHMO1_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;dHMO1_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3875</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3875"/>
				<updated>2017-11-06T03:04:55Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: references addition&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;(STRAIN)_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;(STRAIN)_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;(STRAIN)_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
==References==&lt;br /&gt;
#LMU BioDB 2017. (2017). Week 10. Retrieved November 2, 2017, from &lt;br /&gt;
https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_10&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 19:04, 5 November 2017 (PST)&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3874</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3874"/>
				<updated>2017-11-06T03:03:16Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Acknowledgements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;(STRAIN)_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;(STRAIN)_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;(STRAIN)_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
==Acknowledgements==&lt;br /&gt;
Hayden and I worked on this assignment together, we compare results together in class and texted each other if we had any questions.&lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3873</id>
		<title>ArashLari Week 10</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_10&amp;diff=3873"/>
				<updated>2017-11-06T03:01:56Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: setting up page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==File==&lt;br /&gt;
&lt;br /&gt;
==Electronic Notebook==&lt;br /&gt;
==== Clustering and GO Term Enrichment with stem ====&lt;br /&gt;
&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Prepare your microarray data file for loading into STEM.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#* Download your Excel workbook that you used for your [[Week 8]] assignment.&lt;br /&gt;
#* Insert a new worksheet into your Excel workbook, and name it &amp;quot;(STRAIN)_stem&amp;quot;.&lt;br /&gt;
#* Select all of the data from your &amp;quot;(STRAIN)_ANOVA&amp;quot; worksheet and Paste special &amp;gt; paste values into your &amp;quot;(STRAIN)_stem&amp;quot; worksheet.&lt;br /&gt;
#** Your leftmost column should have the column header &amp;quot;Master_Index&amp;quot;.  Rename this column to &amp;quot;SPOT&amp;quot;.  Column B should be named &amp;quot;ID&amp;quot;.  Rename this column to &amp;quot;Gene Symbol&amp;quot;.  Delete the column named &amp;quot;Standard_Name&amp;quot;.&lt;br /&gt;
#** Filter the data on the B-H corrected p value to be &amp;gt; 0.05 (that&amp;#039;s &amp;#039;&amp;#039;&amp;#039;greater than&amp;#039;&amp;#039;&amp;#039; in this case).&lt;br /&gt;
#*** Once the data has been filtered, select all of the rows (except for your header row) and delete the rows by right-clicking and choosing &amp;quot;Delete Row&amp;quot; from the context menu.  Undo the filter.  This ensures that we will cluster only the genes with a &amp;quot;significant&amp;quot; change in expression and not the noise.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Record the number of genes left in your electronic notebook.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
#** Delete all of the data columns &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;EXCEPT&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; for the Average Log Fold change columns for each timepoint (for example, wt_AvgLogFC_t15, etc.).&lt;br /&gt;
#** Rename the data columns with just the time and units (for example, 15m, 30m, etc.).&lt;br /&gt;
#** Save your work.  Then use &amp;#039;&amp;#039;Save As&amp;#039;&amp;#039; to save this spreadsheet as Text (Tab-delimited) (*.txt).  Click OK to the warnings and close your file.&lt;br /&gt;
#*** Note that you should turn on the file extensions if you have not already done so.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Now download and extract the STEM software.&amp;#039;&amp;#039;&amp;#039;  [http://www.cs.cmu.edu/~jernst/stem/ Click here to go to the STEM web site].&lt;br /&gt;
#* Click on the [http://www.andrew.cmu.edu/user/zivbj/stemreg.html download link], register, and download the &amp;lt;code&amp;gt;stem.zip&amp;lt;/code&amp;gt; file to your Desktop.&lt;br /&gt;
#* Unzip the file.  In Seaver 120, you can right click on the file icon and select the menu item &amp;#039;&amp;#039;7-zip &amp;gt; Extract Here&amp;#039;&amp;#039;.&lt;br /&gt;
#* This will create a folder called &amp;lt;code&amp;gt;stem&amp;lt;/code&amp;gt;.  Inside the folder, double-click on the &amp;lt;code&amp;gt;stem.jar&amp;lt;/code&amp;gt; to launch the STEM program.&lt;br /&gt;
&amp;lt;!--#** In Seaver 120, we encountered an issue where the program would not launch on the Windows XP machines due to a lack of memory. (Even though the computers have been upgraded to Windows 7, do this to launch the program.)  To get around this problem, launch STEM from the command line.&lt;br /&gt;
#*** Go to the start menu and click on &amp;#039;&amp;#039;Programs &amp;gt; Accessories &amp;gt; Command Prompt&amp;#039;&amp;#039;.&lt;br /&gt;
#*** You will need to navigate to the directory (folder) in which the STEM program resides.  If you followed the instructions above and extracted the stem folder to the Desktop, type the following:  &amp;lt;code&amp;gt;cd Desktop\stem&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.&lt;br /&gt;
#*** To launch the program then type:  &amp;lt;code&amp;gt;java -mx512M -jar stem.jar -d defaults.txt&amp;lt;/code&amp;gt;  and press &amp;quot;Enter&amp;quot;.  This will launch the program with less memory allocated to it.--&amp;gt;&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Running STEM&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## In section 1 (Expression Data Info) of the the main STEM interface window, click on the &amp;#039;&amp;#039;Browse...&amp;#039;&amp;#039; button to navigate to and select your file.&lt;br /&gt;
##* Click on the radio button &amp;#039;&amp;#039;No normalization/add 0&amp;#039;&amp;#039;.&lt;br /&gt;
##* Check the box next to &amp;#039;&amp;#039;Spot IDs included in the data file&amp;#039;&amp;#039;.&lt;br /&gt;
## In section 2 (Gene Info) of the main STEM interface window, select &amp;#039;&amp;#039;Saccharomyces cerevisiae (SGD)&amp;#039;&amp;#039;, from the drop-down menu for Gene Annotation Source.  Select &amp;#039;&amp;#039;No cross references&amp;#039;&amp;#039;, from the Cross Reference Source drop-down menu.  Select &amp;#039;&amp;#039;No Gene Locations&amp;#039;&amp;#039; from the Gene Location Source drop-down menu.&lt;br /&gt;
## In section 3 (Options) of the main STEM interface window, make sure that the Clustering Method says &amp;quot;STEM Clustering Method&amp;quot; and do not change the defaults for Maximum Number of Model Profiles or Maximum Unit Change in Model Profiles between Time Points.&lt;br /&gt;
## In section 4 (Execute) click on the yellow Execute button to run STEM.&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Viewing and Saving STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## A new window will open called &amp;quot;All STEM Profiles (1)&amp;quot;.  Each box corresponds to a model expression profile.  Colored profiles have a statistically significant number of genes assigned; they are arranged in order from most to least significant p value.  Profiles with the same color belong to the same cluster of profiles.  The number in each box is simply an ID number for the profile.&lt;br /&gt;
##* Click on the button that says &amp;quot;Interface Options...&amp;quot;.  At the bottom of the Interface Options window that appears below where it says &amp;quot;X-axis scale should be:&amp;quot;, click on the radio button that says &amp;quot;Based on real time&amp;quot;.  Then close the Interface Options window.&lt;br /&gt;
##*Take a screenshot of this window (on a PC, simultaneously press the &amp;lt;code&amp;gt;Alt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PrintScreen&amp;lt;/code&amp;gt; buttons to save the view in the active window to the clipboard) and paste it into a PowerPoint presentation to save your figures.&lt;br /&gt;
## Click on each of the SIGNIFICANT profiles (the colored ones) to open a window showing a more detailed plot containing all of the genes in that profile.&lt;br /&gt;
##* Take a screenshot of each of the individual profile windows and save the images in your PowerPoint presentation.&lt;br /&gt;
##* At the bottom of each profile window, there are two yellow buttons &amp;quot;Profile Gene Table&amp;quot; and &amp;quot;Profile GO Table&amp;quot;.  For each of the profiles, click on the &amp;quot;Profile Gene Table&amp;quot; button to see the list of genes belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_genelist.txt&amp;quot;, where you replace the number symbol with the actual profile number.&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
##* For each of the significant profiles, click on the &amp;quot;Profile GO Table&amp;quot; to see the list of Gene Ontology terms belonging to the profile.  In the window that appears, click on the &amp;quot;Save Table&amp;quot; button and save the file to your desktop.  Make your filename descriptive of the contents, e.g. &amp;quot;wt_profile#_GOlist.txt&amp;quot;, where you use &amp;quot;wt&amp;quot;, &amp;quot;dGLN3&amp;quot;, etc. to indicate the dataset and where you replace the number symbol with the actual profile number.  At this point you have saved all of the primary data from the STEM software and it&amp;#039;s time to interpret the results!&lt;br /&gt;
##** Upload these files to the wiki and link to them on your individual journal page.  (Note that it will be easier to zip all the files together and upload them as one file).&lt;br /&gt;
# &amp;#039;&amp;#039;&amp;#039;Analyzing and Interpreting STEM Results&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
## Select &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;one&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; of the profiles you saved in the previous step for further intepretation of the data.  I suggest that you choose one that has a pattern of up- or down-regulated genes at the cold shock timepoints.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Each member of your group should choose a different profile.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Answer the following:&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Why did you select this profile?  In other words, why was it interesting to you?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many genes were expected to belong to this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;What is the p value for the enrichment of genes in this profile?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  Bear in mind that we just finished computing p values to determine whether each individual gene had a significant change in gene expression at each time point.  This p value determines whether the number of genes that show this particular expression profile across the time points is significantly more than expected.&lt;br /&gt;
##* Open the GO list file you saved for this profile in Excel.  This list shows all of the Gene Ontology terms that are associated with genes that fit this profile.  Select the third row and then choose from the menu Data &amp;gt; Filter &amp;gt; Autofilter.  Filter on the &amp;quot;p-value&amp;quot; column to show only GO terms that have a p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile at p &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;  The GO list also has a column called &amp;quot;Corrected p-value&amp;quot;.  This correction is needed because the software has performed thousands of significance tests.  Filter on the &amp;quot;Corrected p-value&amp;quot; column to show only GO terms that have a corrected p value of &amp;lt; 0.05.  &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;How many GO terms are associated with this profile with a corrected p value &amp;lt; 0.05?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##* Select 6 Gene Ontology terms from your filtered list (either p &amp;lt; 0.05 or corrected p &amp;lt; 0.05).  &lt;br /&gt;
##** Each member of the group will be reporting on his or her own cluster in your presentation next week.  You should take care to choose terms that are the most significant, but that are also not too redundant.  For example, &amp;quot;RNA metabolism&amp;quot; and &amp;quot;RNA biosynthesis&amp;quot; are redundant with each other because they mean almost the same thing.&lt;br /&gt;
##**&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Look up the definitions for each of the terms at [http://geneontology.org http://geneontology.org].  In your final presentation, you will discuss the biological interpretation of these GO terms.  In other words, why does the cell react to cold shock by changing the expression of genes associated with these GO terms?  Also, what does this have to do with the transcription factor that was deleted from your strain?&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
##** To easily look up the definitions, go to [http://geneontology.org http://geneontology.org].&lt;br /&gt;
##** Copy and paste the GO ID (e.g. GO:0044848) into the search field at center top of the page called &amp;quot;Search GO Data&amp;quot;.&lt;br /&gt;
##** In the [http://amigo.geneontology.org/amigo/medial_search?q=GO%3A0044848 results] page, click on the button that says &amp;quot;Link to detailed information about &amp;lt;term&amp;gt;, in this case &amp;quot;biological phase&amp;quot;&amp;quot;. &lt;br /&gt;
##** The definition will be on the next results page, e.g. [http://amigo.geneontology.org/amigo/term/GO:0044848 here].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;This is the stopping point for the Week 10 Assignment.&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; We will pick up the next steps in the analysis in subsequent weeks.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
==Acknowledgements==&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=File:Work.zip&amp;diff=3823</id>
		<title>File:Work.zip</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=File:Work.zip&amp;diff=3823"/>
				<updated>2017-11-02T23:17:19Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: All the work files for the Week 10 assignment&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;All the work files for the Week 10 assignment&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3701</id>
		<title>ArashLari Week 9</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3701"/>
				<updated>2017-10-31T06:12:31Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Electronic Workbook */ clarifying what passed means&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Workbook = &lt;br /&gt;
For the purposes of testing I used the following files: &lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.xlsx&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.sif&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.graphml&lt;br /&gt;
Then proceed to the GRNSight-beta from the link provided in the instructions for this assignment&lt;br /&gt;
*Note: A test passing means that it satisfied all the criteria detailed in the instructions&lt;br /&gt;
== Test 1 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 2 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 3 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 4 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 5 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 6 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 7 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 8 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 9 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 10 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 11 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 12 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 13 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 14 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 15 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 16 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 17 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 18 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Observations == &lt;br /&gt;
While they all passed, it should be noted that for tests 7 through 12, the user can technically see all the numbers, but sometimes they might overlap and become hard to read.&lt;br /&gt;
This can be seen in the following image:&lt;br /&gt;
&lt;br /&gt;
[[File:ArashObservation.png]]&lt;br /&gt;
&lt;br /&gt;
= Web Service API Exploration =&lt;br /&gt;
While I was originally confused as to what the assignment was asking for, once we figured it out it became much clearer. I simply went to the ensemble api page, and found the command that returned the json file using the gene name. The example given on the website had the species as &amp;quot;homo_sapien&amp;quot;, so i changed that to &amp;quot;saccharomyces_cerevisiae&amp;quot; in the url and put the name of a random yeast file to test it. This process worked, but because the instructions pointed to [http://rest.ensembl.org/documentation/info/lookup] I used the ID retrieved from the first command and placed it in the command given from this page to do it the way the instructions alluded to.&lt;br /&gt;
==Deliverable==&lt;br /&gt;
*Note: to find the json file for any other gene, simply replace the text that says &amp;quot;GENE&amp;quot; in the url with your desired gene name. (this code won&amp;#039;t work as it&amp;#039;s generic)&lt;br /&gt;
 curl &amp;#039;http://rest.ensembl.org/lookup/symbol/saccharomyces_cerevisiae/GENE?&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
From there you could put the id retrieved from the json file into the url where it says &amp;quot;ID&amp;quot; in uppercase, but the json file above also returns all the relevant information already. &lt;br /&gt;
 curl &amp;#039;http://rest.ensembl.org/lookup/id/ID?expand=1&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
Nicole Kalcic was my partner and we met up once and worked over text message. I also worked with Zach Van Ysseldyk and Antoni Porras on the Web API section and we figured out how to return the desired deliverable together. &lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 15:36, 30 October 2017 (PDT)&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3698</id>
		<title>ArashLari Week 9</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3698"/>
				<updated>2017-10-31T06:11:28Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Deliverable */ formatting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Workbook = &lt;br /&gt;
For the purposes of testing I used the following files: &lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.xlsx&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.sif&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.graphml&lt;br /&gt;
Then proceed to the GRNSight-beta from the link provided in the instructions for this assignment&lt;br /&gt;
== Test 1 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 2 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 3 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 4 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 5 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 6 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 7 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 8 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 9 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 10 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 11 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 12 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 13 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 14 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 15 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 16 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 17 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 18 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Observations == &lt;br /&gt;
While they all passed, it should be noted that for tests 7 through 12, the user can technically see all the numbers, but sometimes they might overlap and become hard to read.&lt;br /&gt;
This can be seen in the following image:&lt;br /&gt;
&lt;br /&gt;
[[File:ArashObservation.png]]&lt;br /&gt;
&lt;br /&gt;
= Web Service API Exploration =&lt;br /&gt;
While I was originally confused as to what the assignment was asking for, once we figured it out it became much clearer. I simply went to the ensemble api page, and found the command that returned the json file using the gene name. The example given on the website had the species as &amp;quot;homo_sapien&amp;quot;, so i changed that to &amp;quot;saccharomyces_cerevisiae&amp;quot; in the url and put the name of a random yeast file to test it. This process worked, but because the instructions pointed to [http://rest.ensembl.org/documentation/info/lookup] I used the ID retrieved from the first command and placed it in the command given from this page to do it the way the instructions alluded to.&lt;br /&gt;
==Deliverable==&lt;br /&gt;
*Note: to find the json file for any other gene, simply replace the text that says &amp;quot;GENE&amp;quot; in the url with your desired gene name. (this code won&amp;#039;t work as it&amp;#039;s generic)&lt;br /&gt;
 curl &amp;#039;http://rest.ensembl.org/lookup/symbol/saccharomyces_cerevisiae/GENE?&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
From there you could put the id retrieved from the json file into the url where it says &amp;quot;ID&amp;quot; in uppercase, but the json file above also returns all the relevant information already. &lt;br /&gt;
 curl &amp;#039;http://rest.ensembl.org/lookup/id/ID?expand=1&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
Nicole Kalcic was my partner and we met up once and worked over text message. I also worked with Zach Van Ysseldyk and Antoni Porras on the Web API section and we figured out how to return the desired deliverable together. &lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 15:36, 30 October 2017 (PDT)&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3696</id>
		<title>ArashLari Week 9</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3696"/>
				<updated>2017-10-31T06:10:52Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Web Service API Exploration */ Made it generic and added a &amp;quot;how i did it&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Workbook = &lt;br /&gt;
For the purposes of testing I used the following files: &lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.xlsx&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.sif&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.graphml&lt;br /&gt;
Then proceed to the GRNSight-beta from the link provided in the instructions for this assignment&lt;br /&gt;
== Test 1 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 2 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 3 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 4 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 5 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 6 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 7 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 8 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 9 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 10 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 11 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 12 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 13 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 14 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 15 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 16 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 17 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 18 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Observations == &lt;br /&gt;
While they all passed, it should be noted that for tests 7 through 12, the user can technically see all the numbers, but sometimes they might overlap and become hard to read.&lt;br /&gt;
This can be seen in the following image:&lt;br /&gt;
&lt;br /&gt;
[[File:ArashObservation.png]]&lt;br /&gt;
&lt;br /&gt;
= Web Service API Exploration =&lt;br /&gt;
While I was originally confused as to what the assignment was asking for, once we figured it out it became much clearer. I simply went to the ensemble api page, and found the command that returned the json file using the gene name. The example given on the website had the species as &amp;quot;homo_sapien&amp;quot;, so i changed that to &amp;quot;saccharomyces_cerevisiae&amp;quot; in the url and put the name of a random yeast file to test it. This process worked, but because the instructions pointed to [http://rest.ensembl.org/documentation/info/lookup] I used the ID retrieved from the first command and placed it in the command given from this page to do it the way the instructions alluded to.&lt;br /&gt;
==Deliverable==&lt;br /&gt;
*Note: to find the json file for any other gene, simply replace the text that says &amp;quot;GENE&amp;quot; in the url with your desired gene name. (this code won&amp;#039;t work as it&amp;#039;s generic)&lt;br /&gt;
curl &amp;#039;http://rest.ensembl.org/lookup/symbol/saccharomyces_cerevisiae/GENE?&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
From there you could put the id retrieved from the json file into the url where it says &amp;quot;ID&amp;quot; in uppercase, but the json file above also returns all the relevant information already. &lt;br /&gt;
curl &amp;#039;http://rest.ensembl.org/lookup/id/ID?expand=1&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
Nicole Kalcic was my partner and we met up once and worked over text message. I also worked with Zach Van Ysseldyk and Antoni Porras on the Web API section and we figured out how to return the desired deliverable together. &lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 15:36, 30 October 2017 (PDT)&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3687</id>
		<title>ArashLari Week 9</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3687"/>
				<updated>2017-10-31T06:03:54Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Ensemble URL */ updated deliverable&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Workbook = &lt;br /&gt;
For the purposes of testing I used the following files: &lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.xlsx&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.sif&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.graphml&lt;br /&gt;
Then proceed to the GRNSight-beta from the link provided in the instructions for this assignment&lt;br /&gt;
== Test 1 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 2 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 3 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 4 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 5 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 6 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 7 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 8 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 9 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 10 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 11 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 12 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 13 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 14 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 15 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 16 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 17 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 18 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Observations == &lt;br /&gt;
While they all passed, it should be noted that for tests 7 through 12, the user can technically see all the numbers, but sometimes they might overlap and become hard to read.&lt;br /&gt;
This can be seen in the following image:&lt;br /&gt;
&lt;br /&gt;
[[File:ArashObservation.png]]&lt;br /&gt;
&lt;br /&gt;
= Web Service API Exploration =&lt;br /&gt;
&lt;br /&gt;
==Deliverable==&lt;br /&gt;
*Note: to find the json file for any other gene, simply replace the text that says &amp;quot;ACT1&amp;quot; in the url with your desired gene name.&lt;br /&gt;
curl &amp;#039;http://rest.ensembl.org/lookup/symbol/saccharomyces_cerevisiae/ACT1?&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
Nicole Kalcic was my partner and we met up once and worked over text message. I also worked with Zach Van Ysseldyk and Antoni Porras on the Web API section and we figured out how to return the desired deliverable together. &lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 15:36, 30 October 2017 (PDT)&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3682</id>
		<title>ArashLari Week 9</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3682"/>
				<updated>2017-10-31T06:01:35Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Acknowledgements */ added them&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Workbook = &lt;br /&gt;
For the purposes of testing I used the following files: &lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.xlsx&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.sif&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.graphml&lt;br /&gt;
Then proceed to the GRNSight-beta from the link provided in the instructions for this assignment&lt;br /&gt;
== Test 1 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 2 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 3 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 4 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 5 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 6 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 7 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 8 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 9 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 10 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 11 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 12 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 13 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 14 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 15 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 16 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 17 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 18 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Observations == &lt;br /&gt;
While they all passed, it should be noted that for tests 7 through 12, the user can technically see all the numbers, but sometimes they might overlap and become hard to read.&lt;br /&gt;
This can be seen in the following image:&lt;br /&gt;
&lt;br /&gt;
[[File:ArashObservation.png]]&lt;br /&gt;
&lt;br /&gt;
= Ensemble URL =&lt;br /&gt;
curl &amp;#039;http://rest.ensembl.org/lookup/symbol/saccharomyces_cerevisiae/ACT1?&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
Nicole Kalcic was my partner and we met up once and worked over text message. I also worked with Zach Van Ysseldyk and Antoni Porras on the Web API section and we figured out how to return the desired deliverable together. &lt;br /&gt;
While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 15:36, 30 October 2017 (PDT)&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3680</id>
		<title>ArashLari Week 9</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=ArashLari_Week_9&amp;diff=3680"/>
				<updated>2017-10-31T05:59:51Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: /* Observations */ uploaded image&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Electronic Workbook = &lt;br /&gt;
For the purposes of testing I used the following files: &lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.xlsx&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.sif&lt;br /&gt;
*21-genes_31-edges_Schade-data_estimation_output.graphml&lt;br /&gt;
Then proceed to the GRNSight-beta from the link provided in the instructions for this assignment&lt;br /&gt;
== Test 1 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 2 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 3 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 4 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 5 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 6 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Show With Mouse Over&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 7 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 8 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 9 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 10 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 11 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 12 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Always Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 13 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 14 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 15 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Check&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 16 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Open&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 17 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import SIF&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Test 18 ==&lt;br /&gt;
Instructions:&lt;br /&gt;
*Load Graph - File Menu -&amp;gt; Import GraphML&lt;br /&gt;
*Restrict Graph to Viewport - Uncheck&lt;br /&gt;
*Hide/Show Edge Weights - Select &amp;quot;Never Show Edge Weights&amp;quot;&lt;br /&gt;
Result: &amp;#039;&amp;#039;&amp;#039;PASSED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
== Observations == &lt;br /&gt;
While they all passed, it should be noted that for tests 7 through 12, the user can technically see all the numbers, but sometimes they might overlap and become hard to read.&lt;br /&gt;
This can be seen in the following image:&lt;br /&gt;
&lt;br /&gt;
[[File:ArashObservation.png]]&lt;br /&gt;
&lt;br /&gt;
= Ensemble URL =&lt;br /&gt;
curl &amp;#039;http://rest.ensembl.org/lookup/symbol/saccharomyces_cerevisiae/ACT1?&amp;#039; -H &amp;#039;Content-type:application/json&amp;#039;&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
&lt;br /&gt;
[[User:ArashLari|ArashLari]] ([[User talk:ArashLari|talk]]) 15:36, 30 October 2017 (PDT)&lt;br /&gt;
{{Template:ArashLari}}&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	<entry>
		<id>https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=File:ArashObservation.png&amp;diff=3679</id>
		<title>File:ArashObservation.png</title>
		<link rel="alternate" type="text/html" href="https://xmlpipedb.lmucs.io/biodb/fall2017/index.php?title=File:ArashObservation.png&amp;diff=3679"/>
				<updated>2017-10-31T05:58:51Z</updated>
		
		<summary type="html">&lt;p&gt;ArashLari: An observation i made during testing&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;An observation i made during testing&lt;/div&gt;</summary>
		<author><name>ArashLari</name></author>	</entry>

	</feed>