diff --git a/404.html b/404.html index 84777f7ad8b7c249663a9659e5ee3ec6650b6f89..67ae3b6121832d912f230caccbe7d335c3d986ab 100644 --- a/404.html +++ b/404.html @@ -10,16 +10,16 @@
+ | + |
---|---|
![]() |
+
|
+
![]() |
+
|
+
![]() |
+
|
+
![]() |
+
|
+
![]() |
+
|
+
![]() |
+
|
+
Hugo uses Markdown for its simple content format. However, there are a lot of things that Markdown doesn’t support well. You could use pure HTML to expand possibilities.
- -But this happens to be a bad idea. Everyone uses Markdown because it’s pure and simple to read even non-rendered. You should avoid HTML to keep it as simple as possible.
- -To avoid this limitations, Hugo created shortcodes. A shortcode is a simple snippet inside a page.
- -Hugo-theme-learn provides multiple shortcodes on top of existing ones.
- + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -hugo server
, Hugo génère le fic
+
+
+
diff --git a/fr/tags/index.html b/fr/tags/index.html
index 36da7827359556be8fc125422c816d74775f683b..5a479057cd5c51ba5756149157aecb6a4623728c 100644
--- a/fr/tags/index.html
+++ b/fr/tags/index.html
@@ -699,5 +699,8 @@
+
+
+
diff --git a/fr/tutorial/how_to_access_data/index.html b/fr/tutorial/how_to_access_data/index.html
index 5f2500f1a6fd3daa525a8c133f5e3f70563624af..eef4e5271b2f211e25dfa8527d82b52420cfbb37 100644
--- a/fr/tutorial/how_to_access_data/index.html
+++ b/fr/tutorial/how_to_access_data/index.html
@@ -860,6 +860,9 @@ weight = 5
+
+
+
diff --git a/fr/tutorial/index.html b/fr/tutorial/index.html
index 07c5f8b5c4cc13057feda0e3369b7b044c5f7383..9ee04ee19f4bd16dbacabf7c40bd5326044d12b7 100644
--- a/fr/tutorial/index.html
+++ b/fr/tutorial/index.html
@@ -671,6 +671,9 @@
+
+
+
diff --git a/fr/vitrine/index.html b/fr/vitrine/index.html
index d11b6f75274db2477178dd41ba2eade324daf1fd..25260d45b6be153f4a6ae4c38d0322a2e843e389 100644
--- a/fr/vitrine/index.html
+++ b/fr/vitrine/index.html
@@ -692,6 +692,9 @@
+
+
+
diff --git a/github/index.html b/github/index.html
index efcc88e37e676bda960b6d25dbcc9f58acfb2e1d..a330656cbc8ab0ef7a9d9816b1ff598862deff6b 100644
--- a/github/index.html
+++ b/github/index.html
@@ -1,5 +1,5 @@
-
+
@@ -10,22 +10,22 @@
- Our gloal is to only develop open source tools. You will find here a list of the major -repositories hosting our programs
- -This site is designed to help you with the preparation of your +experiment and subsequent data processing and analysis. If you are not familiar with neutron imaging and may be +interested in collaborating with us, visit the publications page to review the science we do.
+ +For industrial applications, please contact Hassina Bilheux
+ +We recommend that you discuss your experiment with the instrument team as soon as you receive +approval of your beam time.
+We would like to thank the contribution from the research community in the implementation of this +web site, and always welcome your comments to improve it (contact +Jean Bilheux).
+Web site logo: Ryzewski K., Herringer S., Bilheux H.Z., Walker L., Sheldon B., Voisin S., Bilheux J., Finocchiaro V., Neutron imaging of archaeological bronzes at the Oak Ridge National Laboratory Physics Procedia, 43, 343-351 (2013).
+ +Introduction here (Hassina)
+ + + -We recommend that you discuss your experiment with the instrument team several weeks before your -beam time.
-Feel free to update this content, just click the Edit this page link displayed on top right of each page, and pullrequest it
+ + + + + + + + + + + -Your modification will be deployed automatically when merged.
-This current documentation has been statically generated with Hugo with a simple command : hugo -t hugo-theme-learn
– source code is available here at GitHub
Automatically published and hosted thanks to Netlify. Read more about Automated HUGO deployments with Netlify
-This must be completed by all participants to the experiment before the first day of experiment.
+Received training e-mail from user office (neutronusers@ornl.gov)?
+ +Completed online training if assigned? ORNL guess portal
+ +Scheduled onsite training and tour for HFIR access?
+ +Followed attached procedure to access CG-1D data?
+ +Followed attached procedure to access CG-1D analysis computer?
+ + + + + +In order to optimize your experiment time, we recommend you to go through the +check lists from this Before your Arrival menu.
+ +Feel free to print out the pdf version +and check out the items one by one.
+ +Para optimizar su tiempo de experimento, le recomendamos que revise el -verifique listas de este menú Prepare Venue.
- -Siéntase libre de imprimir la pdf versión -y mira los artículos uno por uno.
+ + + + + + + + + + + -To be completed by the Principal Investigator (PI) of the experiment at least 3 weeks before beam time.
+You can access your proposal using the IPTS page
+ +Confirmed samples (adding any new samples, and including composition)?
+ +Confirmed need for lab space?
+ +Confirmed experiment team that will be present at beam time (add any new members)?
+ +Confirmed experiment equipment and/or sample environment?
+ + + + + +To be completed by the Principal Investigator (PI) of the experiment
+Provided all safety documentation for user provided equipment immediately?
+ +Shipped/delivered all user provided equipment at least 2 +weeks prior to beam time for electrical and safety inspection?
+ +Answered all safety related questions through IPTS?
+ +Ensured that sample environment requested equipment is available +and compatible with experiment/beam line?
+ +Written a Job Hazard Analysis (JHA) for hands on work at HFIR?
+ + + + + +Your samples must be confirmed in IPTS + before shipping.
+ +Neutron Sciences User Sample IPTS #XXXX
+Oak Ridge National Laboratory / HFIR Site
+Bldg 7972 DP1
+Oak Ridge, TN, 37831
+USA
+
+
+If you prefer to bring your samples, please go first to the Sample Management Desk located in the Cold Guide Hall +and work with Kristin Nevius to have all your samples labeled with an item Barcode before +proceeding to the beamline.
+ + + + + +