updating docs

docs/labguide/environment/code_of_conduct.html

@@ -393,7 +393,7 @@ <h1 class="title">Code of conduct</h1>
 </header>
 
 
-<p>All lab members and guests are expected to adhere to the following code of conduct. In addition, all Stanford University affiliates are required to adhere to the <a href="https://adminguide.stanford.edu/chapter-1/subchapter-1/policy-1-1-1">University Code of Conduct</a>. For definitions of an act of intolerance &amp; hate crime escalation policy please see this page on University <a href="https://deanofstudents.stanford.edu/acts-intolerance-protocol/overview/definitions">AOI</a>. If you wish to speak with someone outside of the lab regarding an incident that occured in or outside of the lab, the university has this<a href="https://deanofstudents.stanford.edu/acts-intolerance-protocol/talk-someone">list of resources.</a></p>
+<p>All lab members and guests are expected to adhere to the following code of conduct. In addition, all Stanford University affiliates are required to adhere to the <a href="https://adminguide.stanford.edu/chapter-1/subchapter-1/policy-1-1-1">University Code of Conduct</a>. For definitions of an act of intolerance &amp; hate crime escalation policy please see this page on University <a href="https://deanofstudents.stanford.edu/acts-intolerance-protocol/overview/definitions">AOI</a>. If you wish to speak with someone outside of the lab regarding an incident that occurred in or outside of the lab, the university has this<a href="https://deanofstudents.stanford.edu/acts-intolerance-protocol/talk-someone">list of resources.</a></p>
 <section id="statement-of-intent" class="level2">
 <h2 class="anchored" data-anchor-id="statement-of-intent">Statement of intent</h2>
 <p>Our lab is dedicated to providing a safe and welcoming environment for everyone. We do not tolerate harassment for any form of identity such as but not limited to: sex, gender identity, age, sexual orientation, disability including mental illness, physical appearance, body size, race, ethnicity, religion (including the lack thereof), or socioeconomic status. We do not tolerate harassment of lab members or guests in any form. Sexual language and imagery is not appropriate for any lab event or venue, including talks, workshops, parties, Twitter and other online media.</p>

docs/labguide/research/intellectual_property.html

@@ -382,7 +382,7 @@ <h2 id="toc-title">On this page</h2>
 <h1>Intellectual property</h1>
 <p>All products of research at Stanford (including data and code) are the property of the University. However, faculty have wide latitude to release software as open source under the University’s <a href="https://otl.stanford.edu/open-source-stanford">open source policy</a>, as long as it doesn’t conflict with any other obligations. Students are allowed to release code under an open source license at Stanford with faculty permission; students in the Poldracklab have blanket permission to do so, as all of our code is intended to be made open available, as discussed in the section on <a href="https://poldracklab.github.io/research/code_management.html">code sharing</a>. After leaving the lab, trainees can continue to reuse any code or other research materials (e.g.&nbsp;stimuli) developed as part of their work in the lab as long as the code has been released under an open source license and they continue to abide by the terms of the license.</p>
 <p>As discussed in the section on <a href="https://poldracklab.github.io/research/data_management.html">data management and sharing</a>, all data collected within our laboratory is meant to be shared upon submission of the related paper. In cases where these data can be deidentified they will be shared under a public domain dedication (CC0), which places no restrictions on their use by other researchers. Thus, any researcher can continue to use those data once they leave the lab. In other cases it may be necessary to restrict data sharing (e.g.&nbsp;when the data cannot be deidentified), in which case researchers will need to obtain a data use agreement from Stanford in order to access those data at their new institution. Dr.&nbsp;Poldrack commits to supporting any such requests, unless they violate other obligations of his or the University.</p>
-<p>In many cases we use data within the lab under Data Use Agreements (such as the ABCD or HCP datasets), and any researcher wishing to use such datasets must be explcitly listed on the DUA. Once a researcher is no longer included in the Stanford DUA for a particular dataset, they must no longer access the dataset via Stanford computer systems.</p>
+<p>In many cases we use data within the lab under Data Use Agreements (such as the ABCD or HCP datasets), and any researcher wishing to use such datasets must be explicitly listed on the DUA. Once a researcher is no longer included in the Stanford DUA for a particular dataset, they must no longer access the dataset via Stanford computer systems.</p>
 <section id="research-ideas" class="level2">
 <h2 class="anchored" data-anchor-id="research-ideas">Research ideas</h2>
 <p>When a trainee leaves the lab, there is often uncertainty about which ideas are theirs to pursue independently and which must be pursued in collaboration with their former mentor. It is difficult to specify a blanket policy on this issue, as it will depend on many different circumstances. Trainees are encouraged to discuss this issue openly with Dr.&nbsp;Poldrack prior to departing the lab, to prevent any misunderstandings. In many cases Dr.&nbsp;Poldrack will be happy for the trainee to take the ideas and pursue them independently in their new position; this has happened on a number of occasions. In other cases, particularly when the ideas were developed in close collaboration with Dr.&nbsp;Poldrack, there may be an expectation that further development of the ideas will occur through collaborative efforts.</p>

docs/labguide/research/statistical_methods.html

@@ -395,7 +395,7 @@ <h2 class="anchored" data-anchor-id="need-help">Need help?</h2>
 <h2 class="anchored" data-anchor-id="multiple-testing">Multiple testing</h2>
 <ul>
 <li>Methods for multiple testing correction should be chosen prior to data analysis and reported in the preregistration document.</li>
-<li>The nature of grouping for multiple testing corrections (e.g., parameter within single models, sets ot models, etc) should be pre-specified.</li>
+<li>The nature of grouping for multiple testing corrections (e.g., parameter within single models, sets of models, etc) should be pre-specified.</li>
 <li>For fMRI data, if using cluster-based thresholding the cluster forming threshold must be Z ≥ 3.1 if using parametric thresholding. There are no restrictions on threshold when using nonparametric thresholding, but the threshold should be pre-specified.</li>
 </ul>
 </section>

docs/publications.html

@@ -385,7 +385,7 @@ <h1 class="title">Publications</h1>
 </header>
 
 
-<div id="3440275c" class="cell" data-message="false" data-execution_count="1">
+<div id="8b4d4720" class="cell" data-message="false" data-execution_count="1">
 <section id="section" class="level3">
 <h3 class="anchored" data-anchor-id="section">2024</h3>
 <p>Demidenko MI, Mumford JA, Poldrack RA (2024). Impact of analytic decisions on test-retest reliability of individual and group estimates in functional magnetic resonance imaging: a multiverse analysis using the monetary incentive delay task. <em>bioRxiv</em>. <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC10983911">OA</a> <a href="https://doi.org/10.1101/2024.03.19.585755">DOI</a></p>