diff --git a/assets/css/styles_feeling_responsive.css b/assets/css/styles_feeling_responsive.css
index c0a47555..0cfabecb 100644
--- a/assets/css/styles_feeling_responsive.css
+++ b/assets/css/styles_feeling_responsive.css
@@ -1,4 +1,4 @@
-.font-size-h1{font-size:2.441em}.font-size-h2{font-size:1.953em}.font-size-h3{font-size:1.563em}.font-size-h4{font-size:1.25em}.font-size-h5{font-size:1.152em}meta.foundation-version{font-family:"/5.5.0/"}meta.foundation-mq-small{font-family:"/only screen/";width:0em}meta.foundation-mq-small-only{font-family:"/only screen and (max-width: 40em)/";width:0em}meta.foundation-mq-medium{font-family:"/only screen and (min-width:40.063em)/";width:40.063em}meta.foundation-mq-medium-only{font-family:"/only screen and (min-width:40.063em) and (max-width:64em)/";width:40.063em}meta.foundation-mq-large{font-family:"/only screen and (min-width:64.063em)/";width:64.063em}meta.foundation-mq-large-only{font-family:"/only screen and (min-width:64.063em) and (max-width:90em)/";width:64.063em}meta.foundation-mq-xlarge{font-family:"/only screen and (min-width:90.063em)/";width:90.063em}meta.foundation-mq-xlarge-only{font-family:"/only screen and (min-width:90.063em) and (max-width:120em)/";width:90.063em}meta.foundation-mq-xxlarge{font-family:"/only screen and (min-width:120.063em)/";width:120.063em}meta.foundation-data-attribute-namespace{font-family:false}html,body{height:100%}*,*:before,*:after{-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box}html,body{font-size:16px}body{background:#fdfdfd;color:#111;padding:0;margin:0;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:normal;font-style:normal;line-height:1.5;position:relative;cursor:auto}a:hover{cursor:pointer}img{max-width:100%;height:auto}img{-ms-interpolation-mode:bicubic}#map_canvas img,#map_canvas embed,#map_canvas object,.map_canvas img,.map_canvas embed,.map_canvas object{max-width:none !important}.left{float:left !important}.right{float:right !important}.clearfix:before,.clearfix:after{content:" ";display:table}.clearfix:after{clear:both}.hide{display:none !important;visibility:hidden}.invisible{visibility:hidden}.antialiased{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}img{display:inline-block;vertical-align:middle}textarea{height:auto;min-height:50px}select{width:100%}/*! normalize.css v3.0.2 | MIT License | git.io/normalize */html{font-family:sans-serif;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%}body{margin:0}article,aside,details,figcaption,figure,footer,header,hgroup,main,menu,nav,section,summary{display:block}audio,canvas,progress,video{display:inline-block;vertical-align:baseline}audio:not([controls]){display:none;height:0}[hidden],template{display:none}a{background-color:rgba(0,0,0,0)}a:active,a:hover{outline:0}abbr[title]{border-bottom:1px dotted}b,strong{font-weight:bold}dfn{font-style:italic}h1{font-size:2em;margin:.67em 0}mark{background:#ff0;color:#000}small{font-size:80%}sub,sup{font-size:75%;line-height:0;position:relative;vertical-align:baseline}sup{top:-0.5em}sub{bottom:-0.25em}img{border:0}svg:not(:root){overflow:hidden}figure{margin:1em 40px}hr{-moz-box-sizing:content-box;box-sizing:content-box;height:0}pre{overflow:auto}code,kbd,pre,samp{font-family:monospace,monospace;font-size:1em}button,input,optgroup,select,textarea{color:inherit;font:inherit;margin:0}button{overflow:visible}button,select{text-transform:none}button,html input[type=button],input[type=reset],input[type=submit]{-webkit-appearance:button;cursor:pointer}button[disabled],html input[disabled]{cursor:default}button::-moz-focus-inner,input::-moz-focus-inner{border:0;padding:0}input{line-height:normal}input[type=checkbox],input[type=radio]{box-sizing:border-box;padding:0}input[type=number]::-webkit-inner-spin-button,input[type=number]::-webkit-outer-spin-button{height:auto}input[type=search]{-webkit-appearance:textfield;-moz-box-sizing:content-box;-webkit-box-sizing:content-box;box-sizing:content-box}input[type=search]::-webkit-search-cancel-button,input[type=search]::-webkit-search-decoration{-webkit-appearance:none}fieldset{border:1px solid silver;margin:0 2px;padding:.35em .625em .75em}legend{border:0;padding:0}textarea{overflow:auto}optgroup{font-weight:bold}table{border-collapse:collapse;border-spacing:0}td,th{padding:0}.row{width:100%;margin-left:auto;margin-right:auto;margin-top:0;margin-bottom:0;max-width:93.75rem}.row:before,.row:after{content:" ";display:table}.row:after{clear:both}.row.collapse>.column,.row.collapse>.columns{padding-left:0;padding-right:0}.row.collapse .row{margin-left:0;margin-right:0}.row .row{width:auto;margin-left:-0.9375rem;margin-right:-0.9375rem;margin-top:0;margin-bottom:0;max-width:none}.row .row:before,.row .row:after{content:" ";display:table}.row .row:after{clear:both}.row .row.collapse{width:auto;margin:0;max-width:none}.row .row.collapse:before,.row .row.collapse:after{content:" ";display:table}.row .row.collapse:after{clear:both}.column,.columns{padding-left:.9375rem;padding-right:.9375rem;width:100%;float:left}[class*=column]+[class*=column]:last-child{float:right}[class*=column]+[class*=column].end{float:left}@media only screen{.small-push-0{position:relative;left:0%;right:auto}.small-pull-0{position:relative;right:0%;left:auto}.small-push-1{position:relative;left:8.3333333333%;right:auto}.small-pull-1{position:relative;right:8.3333333333%;left:auto}.small-push-2{position:relative;left:16.6666666667%;right:auto}.small-pull-2{position:relative;right:16.6666666667%;left:auto}.small-push-3{position:relative;left:25%;right:auto}.small-pull-3{position:relative;right:25%;left:auto}.small-push-4{position:relative;left:33.3333333333%;right:auto}.small-pull-4{position:relative;right:33.3333333333%;left:auto}.small-push-5{position:relative;left:41.6666666667%;right:auto}.small-pull-5{position:relative;right:41.6666666667%;left:auto}.small-push-6{position:relative;left:50%;right:auto}.small-pull-6{position:relative;right:50%;left:auto}.small-push-7{position:relative;left:58.3333333333%;right:auto}.small-pull-7{position:relative;right:58.3333333333%;left:auto}.small-push-8{position:relative;left:66.6666666667%;right:auto}.small-pull-8{position:relative;right:66.6666666667%;left:auto}.small-push-9{position:relative;left:75%;right:auto}.small-pull-9{position:relative;right:75%;left:auto}.small-push-10{position:relative;left:83.3333333333%;right:auto}.small-pull-10{position:relative;right:83.3333333333%;left:auto}.small-push-11{position:relative;left:91.6666666667%;right:auto}.small-pull-11{position:relative;right:91.6666666667%;left:auto}.column,.columns{position:relative;padding-left:.9375rem;padding-right:.9375rem;float:left}.small-1{width:8.3333333333%}.small-2{width:16.6666666667%}.small-3{width:25%}.small-4{width:33.3333333333%}.small-5{width:41.6666666667%}.small-6{width:50%}.small-7{width:58.3333333333%}.small-8{width:66.6666666667%}.small-9{width:75%}.small-10{width:83.3333333333%}.small-11{width:91.6666666667%}.small-12{width:100%}.small-offset-0{margin-left:0% !important}.small-offset-1{margin-left:8.3333333333% !important}.small-offset-2{margin-left:16.6666666667% !important}.small-offset-3{margin-left:25% !important}.small-offset-4{margin-left:33.3333333333% !important}.small-offset-5{margin-left:41.6666666667% !important}.small-offset-6{margin-left:50% !important}.small-offset-7{margin-left:58.3333333333% !important}.small-offset-8{margin-left:66.6666666667% !important}.small-offset-9{margin-left:75% !important}.small-offset-10{margin-left:83.3333333333% !important}.small-offset-11{margin-left:91.6666666667% !important}.small-reset-order{margin-left:0;margin-right:0;left:auto;right:auto;float:left}.column.small-centered,.columns.small-centered{margin-left:auto;margin-right:auto;float:none}.column.small-uncentered,.columns.small-uncentered{margin-left:0;margin-right:0;float:left}.column.small-centered:last-child,.columns.small-centered:last-child{float:none}.column.small-uncentered:last-child,.columns.small-uncentered:last-child{float:left}.column.small-uncentered.opposite,.columns.small-uncentered.opposite{float:right}.row.small-collapse>.column,.row.small-collapse>.columns{padding-left:0;padding-right:0}.row.small-collapse .row{margin-left:0;margin-right:0}.row.small-uncollapse>.column,.row.small-uncollapse>.columns{padding-left:.9375rem;padding-right:.9375rem;float:left}}@media only screen and (min-width:40.063em){.medium-push-0{position:relative;left:0%;right:auto}.medium-pull-0{position:relative;right:0%;left:auto}.medium-push-1{position:relative;left:8.3333333333%;right:auto}.medium-pull-1{position:relative;right:8.3333333333%;left:auto}.medium-push-2{position:relative;left:16.6666666667%;right:auto}.medium-pull-2{position:relative;right:16.6666666667%;left:auto}.medium-push-3{position:relative;left:25%;right:auto}.medium-pull-3{position:relative;right:25%;left:auto}.medium-push-4{position:relative;left:33.3333333333%;right:auto}.medium-pull-4{position:relative;right:33.3333333333%;left:auto}.medium-push-5{position:relative;left:41.6666666667%;right:auto}.medium-pull-5{position:relative;right:41.6666666667%;left:auto}.medium-push-6{position:relative;left:50%;right:auto}.medium-pull-6{position:relative;right:50%;left:auto}.medium-push-7{position:relative;left:58.3333333333%;right:auto}.medium-pull-7{position:relative;right:58.3333333333%;left:auto}.medium-push-8{position:relative;left:66.6666666667%;right:auto}.medium-pull-8{position:relative;right:66.6666666667%;left:auto}.medium-push-9{position:relative;left:75%;right:auto}.medium-pull-9{position:relative;right:75%;left:auto}.medium-push-10{position:relative;left:83.3333333333%;right:auto}.medium-pull-10{position:relative;right:83.3333333333%;left:auto}.medium-push-11{position:relative;left:91.6666666667%;right:auto}.medium-pull-11{position:relative;right:91.6666666667%;left:auto}.column,.columns{position:relative;padding-left:.9375rem;padding-right:.9375rem;float:left}.medium-1{width:8.3333333333%}.medium-2{width:16.6666666667%}.medium-3{width:25%}.medium-4{width:33.3333333333%}.medium-5{width:41.6666666667%}.medium-6{width:50%}.medium-7{width:58.3333333333%}.medium-8{width:66.6666666667%}.medium-9{width:75%}.medium-10{width:83.3333333333%}.medium-11{width:91.6666666667%}.medium-12{width:100%}.medium-offset-0{margin-left:0% !important}.medium-offset-1{margin-left:8.3333333333% !important}.medium-offset-2{margin-left:16.6666666667% !important}.medium-offset-3{margin-left:25% !important}.medium-offset-4{margin-left:33.3333333333% !important}.medium-offset-5{margin-left:41.6666666667% !important}.medium-offset-6{margin-left:50% !important}.medium-offset-7{margin-left:58.3333333333% !important}.medium-offset-8{margin-left:66.6666666667% !important}.medium-offset-9{margin-left:75% !important}.medium-offset-10{margin-left:83.3333333333% !important}.medium-offset-11{margin-left:91.6666666667% !important}.medium-reset-order{margin-left:0;margin-right:0;left:auto;right:auto;float:left}.column.medium-centered,.columns.medium-centered{margin-left:auto;margin-right:auto;float:none}.column.medium-uncentered,.columns.medium-uncentered{margin-left:0;margin-right:0;float:left}.column.medium-centered:last-child,.columns.medium-centered:last-child{float:none}.column.medium-uncentered:last-child,.columns.medium-uncentered:last-child{float:left}.column.medium-uncentered.opposite,.columns.medium-uncentered.opposite{float:right}.row.medium-collapse>.column,.row.medium-collapse>.columns{padding-left:0;padding-right:0}.row.medium-collapse .row{margin-left:0;margin-right:0}.row.medium-uncollapse>.column,.row.medium-uncollapse>.columns{padding-left:.9375rem;padding-right:.9375rem;float:left}.push-0{position:relative;left:0%;right:auto}.pull-0{position:relative;right:0%;left:auto}.push-1{position:relative;left:8.3333333333%;right:auto}.pull-1{position:relative;right:8.3333333333%;left:auto}.push-2{position:relative;left:16.6666666667%;right:auto}.pull-2{position:relative;right:16.6666666667%;left:auto}.push-3{position:relative;left:25%;right:auto}.pull-3{position:relative;right:25%;left:auto}.push-4{position:relative;left:33.3333333333%;right:auto}.pull-4{position:relative;right:33.3333333333%;left:auto}.push-5{position:relative;left:41.6666666667%;right:auto}.pull-5{position:relative;right:41.6666666667%;left:auto}.push-6{position:relative;left:50%;right:auto}.pull-6{position:relative;right:50%;left:auto}.push-7{position:relative;left:58.3333333333%;right:auto}.pull-7{position:relative;right:58.3333333333%;left:auto}.push-8{position:relative;left:66.6666666667%;right:auto}.pull-8{position:relative;right:66.6666666667%;left:auto}.push-9{position:relative;left:75%;right:auto}.pull-9{position:relative;right:75%;left:auto}.push-10{position:relative;left:83.3333333333%;right:auto}.pull-10{position:relative;right:83.3333333333%;left:auto}.push-11{position:relative;left:91.6666666667%;right:auto}.pull-11{position:relative;right:91.6666666667%;left:auto}}@media only screen and (min-width:64.063em){.large-push-0{position:relative;left:0%;right:auto}.large-pull-0{position:relative;right:0%;left:auto}.large-push-1{position:relative;left:8.3333333333%;right:auto}.large-pull-1{position:relative;right:8.3333333333%;left:auto}.large-push-2{position:relative;left:16.6666666667%;right:auto}.large-pull-2{position:relative;right:16.6666666667%;left:auto}.large-push-3{position:relative;left:25%;right:auto}.large-pull-3{position:relative;right:25%;left:auto}.large-push-4{position:relative;left:33.3333333333%;right:auto}.large-pull-4{position:relative;right:33.3333333333%;left:auto}.large-push-5{position:relative;left:41.6666666667%;right:auto}.large-pull-5{position:relative;right:41.6666666667%;left:auto}.large-push-6{position:relative;left:50%;right:auto}.large-pull-6{position:relative;right:50%;left:auto}.large-push-7{position:relative;left:58.3333333333%;right:auto}.large-pull-7{position:relative;right:58.3333333333%;left:auto}.large-push-8{position:relative;left:66.6666666667%;right:auto}.large-pull-8{position:relative;right:66.6666666667%;left:auto}.large-push-9{position:relative;left:75%;right:auto}.large-pull-9{position:relative;right:75%;left:auto}.large-push-10{position:relative;left:83.3333333333%;right:auto}.large-pull-10{position:relative;right:83.3333333333%;left:auto}.large-push-11{position:relative;left:91.6666666667%;right:auto}.large-pull-11{position:relative;right:91.6666666667%;left:auto}.column,.columns{position:relative;padding-left:.9375rem;padding-right:.9375rem;float:left}.large-1{width:8.3333333333%}.large-2{width:16.6666666667%}.large-3{width:25%}.large-4{width:33.3333333333%}.large-5{width:41.6666666667%}.large-6{width:50%}.large-7{width:58.3333333333%}.large-8{width:66.6666666667%}.large-9{width:75%}.large-10{width:83.3333333333%}.large-11{width:91.6666666667%}.large-12{width:100%}.large-offset-0{margin-left:0% !important}.large-offset-1{margin-left:8.3333333333% !important}.large-offset-2{margin-left:16.6666666667% !important}.large-offset-3{margin-left:25% !important}.large-offset-4{margin-left:33.3333333333% !important}.large-offset-5{margin-left:41.6666666667% !important}.large-offset-6{margin-left:50% !important}.large-offset-7{margin-left:58.3333333333% !important}.large-offset-8{margin-left:66.6666666667% !important}.large-offset-9{margin-left:75% !important}.large-offset-10{margin-left:83.3333333333% !important}.large-offset-11{margin-left:91.6666666667% !important}.large-reset-order{margin-left:0;margin-right:0;left:auto;right:auto;float:left}.column.large-centered,.columns.large-centered{margin-left:auto;margin-right:auto;float:none}.column.large-uncentered,.columns.large-uncentered{margin-left:0;margin-right:0;float:left}.column.large-centered:last-child,.columns.large-centered:last-child{float:none}.column.large-uncentered:last-child,.columns.large-uncentered:last-child{float:left}.column.large-uncentered.opposite,.columns.large-uncentered.opposite{float:right}.row.large-collapse>.column,.row.large-collapse>.columns{padding-left:0;padding-right:0}.row.large-collapse .row{margin-left:0;margin-right:0}.row.large-uncollapse>.column,.row.large-uncollapse>.columns{padding-left:.9375rem;padding-right:.9375rem;float:left}.push-0{position:relative;left:0%;right:auto}.pull-0{position:relative;right:0%;left:auto}.push-1{position:relative;left:8.3333333333%;right:auto}.pull-1{position:relative;right:8.3333333333%;left:auto}.push-2{position:relative;left:16.6666666667%;right:auto}.pull-2{position:relative;right:16.6666666667%;left:auto}.push-3{position:relative;left:25%;right:auto}.pull-3{position:relative;right:25%;left:auto}.push-4{position:relative;left:33.3333333333%;right:auto}.pull-4{position:relative;right:33.3333333333%;left:auto}.push-5{position:relative;left:41.6666666667%;right:auto}.pull-5{position:relative;right:41.6666666667%;left:auto}.push-6{position:relative;left:50%;right:auto}.pull-6{position:relative;right:50%;left:auto}.push-7{position:relative;left:58.3333333333%;right:auto}.pull-7{position:relative;right:58.3333333333%;left:auto}.push-8{position:relative;left:66.6666666667%;right:auto}.pull-8{position:relative;right:66.6666666667%;left:auto}.push-9{position:relative;left:75%;right:auto}.pull-9{position:relative;right:75%;left:auto}.push-10{position:relative;left:83.3333333333%;right:auto}.pull-10{position:relative;right:83.3333333333%;left:auto}.push-11{position:relative;left:91.6666666667%;right:auto}.pull-11{position:relative;right:91.6666666667%;left:auto}}button,.button{border-style:solid;border-width:0;cursor:pointer;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:normal;line-height:normal;margin:0 0 1.25rem;position:relative;text-decoration:none;text-align:center;-webkit-appearance:none;border-radius:0;display:inline-block;padding-top:1rem;padding-right:2rem;padding-bottom:1.0625rem;padding-left:2rem;font-size:1rem;background-color:#334d5c;border-color:#293e4a;color:#fff;transition:background-color 300ms ease-out}button:hover,button:focus,.button:hover,.button:focus{background-color:#293e4a}button:hover,button:focus,.button:hover,.button:focus{color:#fff}button.secondary,.button.secondary{background-color:#a1d044;border-color:#84b02c;color:#fff}button.secondary:hover,button.secondary:focus,.button.secondary:hover,.button.secondary:focus{background-color:#84b02c}button.secondary:hover,button.secondary:focus,.button.secondary:hover,.button.secondary:focus{color:#fff}button.success,.button.success{background-color:#a1d044;border-color:#84b02c;color:#fff}button.success:hover,button.success:focus,.button.success:hover,.button.success:focus{background-color:#84b02c}button.success:hover,button.success:focus,.button.success:hover,.button.success:focus{color:#fff}button.alert,.button.alert{background-color:#df4949;border-color:#c92323;color:#fff}button.alert:hover,button.alert:focus,.button.alert:hover,.button.alert:focus{background-color:#c92323}button.alert:hover,button.alert:focus,.button.alert:hover,.button.alert:focus{color:#fff}button.warning,.button.warning{background-color:#be6409;border-color:#985007;color:#fff}button.warning:hover,button.warning:focus,.button.warning:hover,.button.warning:focus{background-color:#985007}button.warning:hover,button.warning:focus,.button.warning:hover,.button.warning:focus{color:#fff}button.info,.button.info{background-color:#334d5c;border-color:#293e4a;color:#fff}button.info:hover,button.info:focus,.button.info:hover,.button.info:focus{background-color:#293e4a}button.info:hover,button.info:focus,.button.info:hover,.button.info:focus{color:#fff}button.large,.button.large{padding-top:1.125rem;padding-right:2.25rem;padding-bottom:1.1875rem;padding-left:2.25rem;font-size:1.25rem}button.small,.button.small{padding-top:.875rem;padding-right:1.75rem;padding-bottom:.9375rem;padding-left:1.75rem;font-size:.8125rem}button.tiny,.button.tiny{padding-top:.625rem;padding-right:1.25rem;padding-bottom:.6875rem;padding-left:1.25rem;font-size:.6875rem}button.expand,.button.expand{padding-right:0;padding-left:0;width:100%}button.left-align,.button.left-align{text-align:left;text-indent:.75rem}button.right-align,.button.right-align{text-align:right;padding-right:.75rem}button.radius,.button.radius{border-radius:3px}button.round,.button.round{border-radius:1000px}button.disabled,button[disabled],.button.disabled,.button[disabled]{background-color:#334d5c;border-color:#293e4a;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled:hover,button.disabled:focus,button[disabled]:hover,button[disabled]:focus,.button.disabled:hover,.button.disabled:focus,.button[disabled]:hover,.button[disabled]:focus{background-color:#293e4a}button.disabled:hover,button.disabled:focus,button[disabled]:hover,button[disabled]:focus,.button.disabled:hover,.button.disabled:focus,.button[disabled]:hover,.button[disabled]:focus{color:#fff}button.disabled:hover,button.disabled:focus,button[disabled]:hover,button[disabled]:focus,.button.disabled:hover,.button.disabled:focus,.button[disabled]:hover,.button[disabled]:focus{background-color:#334d5c}button.disabled.secondary,button[disabled].secondary,.button.disabled.secondary,.button[disabled].secondary{background-color:#a1d044;border-color:#84b02c;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.secondary:hover,button.disabled.secondary:focus,button[disabled].secondary:hover,button[disabled].secondary:focus,.button.disabled.secondary:hover,.button.disabled.secondary:focus,.button[disabled].secondary:hover,.button[disabled].secondary:focus{background-color:#84b02c}button.disabled.secondary:hover,button.disabled.secondary:focus,button[disabled].secondary:hover,button[disabled].secondary:focus,.button.disabled.secondary:hover,.button.disabled.secondary:focus,.button[disabled].secondary:hover,.button[disabled].secondary:focus{color:#fff}button.disabled.secondary:hover,button.disabled.secondary:focus,button[disabled].secondary:hover,button[disabled].secondary:focus,.button.disabled.secondary:hover,.button.disabled.secondary:focus,.button[disabled].secondary:hover,.button[disabled].secondary:focus{background-color:#a1d044}button.disabled.success,button[disabled].success,.button.disabled.success,.button[disabled].success{background-color:#a1d044;border-color:#84b02c;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.success:hover,button.disabled.success:focus,button[disabled].success:hover,button[disabled].success:focus,.button.disabled.success:hover,.button.disabled.success:focus,.button[disabled].success:hover,.button[disabled].success:focus{background-color:#84b02c}button.disabled.success:hover,button.disabled.success:focus,button[disabled].success:hover,button[disabled].success:focus,.button.disabled.success:hover,.button.disabled.success:focus,.button[disabled].success:hover,.button[disabled].success:focus{color:#fff}button.disabled.success:hover,button.disabled.success:focus,button[disabled].success:hover,button[disabled].success:focus,.button.disabled.success:hover,.button.disabled.success:focus,.button[disabled].success:hover,.button[disabled].success:focus{background-color:#a1d044}button.disabled.alert,button[disabled].alert,.button.disabled.alert,.button[disabled].alert{background-color:#df4949;border-color:#c92323;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.alert:hover,button.disabled.alert:focus,button[disabled].alert:hover,button[disabled].alert:focus,.button.disabled.alert:hover,.button.disabled.alert:focus,.button[disabled].alert:hover,.button[disabled].alert:focus{background-color:#c92323}button.disabled.alert:hover,button.disabled.alert:focus,button[disabled].alert:hover,button[disabled].alert:focus,.button.disabled.alert:hover,.button.disabled.alert:focus,.button[disabled].alert:hover,.button[disabled].alert:focus{color:#fff}button.disabled.alert:hover,button.disabled.alert:focus,button[disabled].alert:hover,button[disabled].alert:focus,.button.disabled.alert:hover,.button.disabled.alert:focus,.button[disabled].alert:hover,.button[disabled].alert:focus{background-color:#df4949}button.disabled.warning,button[disabled].warning,.button.disabled.warning,.button[disabled].warning{background-color:#be6409;border-color:#985007;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.warning:hover,button.disabled.warning:focus,button[disabled].warning:hover,button[disabled].warning:focus,.button.disabled.warning:hover,.button.disabled.warning:focus,.button[disabled].warning:hover,.button[disabled].warning:focus{background-color:#985007}button.disabled.warning:hover,button.disabled.warning:focus,button[disabled].warning:hover,button[disabled].warning:focus,.button.disabled.warning:hover,.button.disabled.warning:focus,.button[disabled].warning:hover,.button[disabled].warning:focus{color:#fff}button.disabled.warning:hover,button.disabled.warning:focus,button[disabled].warning:hover,button[disabled].warning:focus,.button.disabled.warning:hover,.button.disabled.warning:focus,.button[disabled].warning:hover,.button[disabled].warning:focus{background-color:#be6409}button.disabled.info,button[disabled].info,.button.disabled.info,.button[disabled].info{background-color:#334d5c;border-color:#293e4a;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.info:hover,button.disabled.info:focus,button[disabled].info:hover,button[disabled].info:focus,.button.disabled.info:hover,.button.disabled.info:focus,.button[disabled].info:hover,.button[disabled].info:focus{background-color:#293e4a}button.disabled.info:hover,button.disabled.info:focus,button[disabled].info:hover,button[disabled].info:focus,.button.disabled.info:hover,.button.disabled.info:focus,.button[disabled].info:hover,.button[disabled].info:focus{color:#fff}button.disabled.info:hover,button.disabled.info:focus,button[disabled].info:hover,button[disabled].info:focus,.button.disabled.info:hover,.button.disabled.info:focus,.button[disabled].info:hover,.button[disabled].info:focus{background-color:#334d5c}button::-moz-focus-inner{border:0;padding:0}@media only screen and (min-width:40.063em){button,.button{display:inline-block}}form{margin:0 0 1rem}form .row .row{margin:0 -0.5rem}form .row .row .column,form .row .row .columns{padding:0 .5rem}form .row .row.collapse{margin:0}form .row .row.collapse .column,form .row .row.collapse .columns{padding:0}form .row .row.collapse input{-webkit-border-bottom-right-radius:0;-webkit-border-top-right-radius:0;border-bottom-right-radius:0;border-top-right-radius:0}form .row input.column,form .row input.columns,form .row textarea.column,form .row textarea.columns{padding-left:.5rem}label{font-size:.875rem;color:#4d4d4d;cursor:pointer;display:block;font-weight:normal;line-height:1.5;margin-bottom:0}label.right{float:none !important;text-align:right}label.inline{margin:0 0 1rem 0;padding:.5625rem 0}label small{text-transform:capitalize;color:#676767}.prefix,.postfix{display:block;position:relative;z-index:2;text-align:center;width:100%;padding-top:0;padding-bottom:0;border-style:solid;border-width:1px;overflow:hidden;font-size:.875rem;height:2.3125rem;line-height:2.3125rem}.postfix.button{padding-left:0;padding-right:0;padding-top:0;padding-bottom:0;text-align:center;border:none}.prefix.button{padding-left:0;padding-right:0;padding-top:0;padding-bottom:0;text-align:center;border:none}.prefix.button.radius{border-radius:0;-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}.postfix.button.radius{border-radius:0;-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}.prefix.button.round{border-radius:0;-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}.postfix.button.round{border-radius:0;-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}span.prefix,label.prefix{background:#f2f2f2;border-right:none;color:#333;border-color:#ccc}span.postfix,label.postfix{background:#f2f2f2;border-left:none;color:#333;border-color:#ccc}input[type=text],input[type=password],input[type=date],input[type=datetime],input[type=datetime-local],input[type=month],input[type=week],input[type=email],input[type=number],input[type=search],input[type=tel],input[type=time],input[type=url],input[type=color],textarea{-webkit-appearance:none;border-radius:0;background-color:#fff;font-family:inherit;border-style:solid;border-width:1px;border-color:#ccc;box-shadow:inset 0 1px 2px rgba(0,0,0,.1);color:rgba(0,0,0,.75);display:block;font-size:.875rem;margin:0 0 1rem 0;padding:.5rem;height:2.3125rem;width:100%;-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box;transition:box-shadow .45s,border-color .45s ease-in-out}input[type=text]:focus,input[type=password]:focus,input[type=date]:focus,input[type=datetime]:focus,input[type=datetime-local]:focus,input[type=month]:focus,input[type=week]:focus,input[type=email]:focus,input[type=number]:focus,input[type=search]:focus,input[type=tel]:focus,input[type=time]:focus,input[type=url]:focus,input[type=color]:focus,textarea:focus{box-shadow:0 0 5px #999;border-color:#999}input[type=text]:focus,input[type=password]:focus,input[type=date]:focus,input[type=datetime]:focus,input[type=datetime-local]:focus,input[type=month]:focus,input[type=week]:focus,input[type=email]:focus,input[type=number]:focus,input[type=search]:focus,input[type=tel]:focus,input[type=time]:focus,input[type=url]:focus,input[type=color]:focus,textarea:focus{background:#fafafa;border-color:#999;outline:none}input[type=text]:disabled,input[type=password]:disabled,input[type=date]:disabled,input[type=datetime]:disabled,input[type=datetime-local]:disabled,input[type=month]:disabled,input[type=week]:disabled,input[type=email]:disabled,input[type=number]:disabled,input[type=search]:disabled,input[type=tel]:disabled,input[type=time]:disabled,input[type=url]:disabled,input[type=color]:disabled,textarea:disabled{background-color:#ddd;cursor:default}input[type=text][disabled],input[type=text][readonly],fieldset[disabled] input[type=text],input[type=password][disabled],input[type=password][readonly],fieldset[disabled] input[type=password],input[type=date][disabled],input[type=date][readonly],fieldset[disabled] input[type=date],input[type=datetime][disabled],input[type=datetime][readonly],fieldset[disabled] input[type=datetime],input[type=datetime-local][disabled],input[type=datetime-local][readonly],fieldset[disabled] input[type=datetime-local],input[type=month][disabled],input[type=month][readonly],fieldset[disabled] input[type=month],input[type=week][disabled],input[type=week][readonly],fieldset[disabled] input[type=week],input[type=email][disabled],input[type=email][readonly],fieldset[disabled] input[type=email],input[type=number][disabled],input[type=number][readonly],fieldset[disabled] input[type=number],input[type=search][disabled],input[type=search][readonly],fieldset[disabled] input[type=search],input[type=tel][disabled],input[type=tel][readonly],fieldset[disabled] input[type=tel],input[type=time][disabled],input[type=time][readonly],fieldset[disabled] input[type=time],input[type=url][disabled],input[type=url][readonly],fieldset[disabled] input[type=url],input[type=color][disabled],input[type=color][readonly],fieldset[disabled] input[type=color],textarea[disabled],textarea[readonly],fieldset[disabled] textarea{background-color:#ddd;cursor:default}input[type=text].radius,input[type=password].radius,input[type=date].radius,input[type=datetime].radius,input[type=datetime-local].radius,input[type=month].radius,input[type=week].radius,input[type=email].radius,input[type=number].radius,input[type=search].radius,input[type=tel].radius,input[type=time].radius,input[type=url].radius,input[type=color].radius,textarea.radius{border-radius:3px}form .row .prefix-radius.row.collapse input,form .row .prefix-radius.row.collapse textarea,form .row .prefix-radius.row.collapse select{border-radius:0;-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}form .row .prefix-radius.row.collapse .prefix{border-radius:0;-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}form .row .postfix-radius.row.collapse input,form .row .postfix-radius.row.collapse textarea,form .row .postfix-radius.row.collapse select{border-radius:0;-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}form .row .postfix-radius.row.collapse .postfix{border-radius:0;-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}form .row .prefix-round.row.collapse input,form .row .prefix-round.row.collapse textarea,form .row .prefix-round.row.collapse select{border-radius:0;-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}form .row .prefix-round.row.collapse .prefix{border-radius:0;-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}form .row .postfix-round.row.collapse input,form .row .postfix-round.row.collapse textarea,form .row .postfix-round.row.collapse select{border-radius:0;-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}form .row .postfix-round.row.collapse .postfix{border-radius:0;-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}input[type=submit]{-webkit-appearance:none;border-radius:0}textarea[rows]{height:auto}textarea{max-width:100%}select{-webkit-appearance:none !important;border-radius:0;background-color:#fafafa;background-image:url(data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZlcnNpb249IjEuMSIgeD0iMTJweCIgeT0iMHB4IiB3aWR0aD0iMjRweCIgaGVpZ2h0PSIzcHgiIHZpZXdCb3g9IjAgMCA2IDMiIGVuYWJsZS1iYWNrZ3JvdW5kPSJuZXcgMCAwIDYgMyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI+PHBvbHlnb24gcG9pbnRzPSI1Ljk5MiwwIDIuOTkyLDMgLTAuMDA4LDAgIi8+PC9zdmc+);background-position:100% center;background-repeat:no-repeat;border-style:solid;border-width:1px;border-color:#ccc;padding:.5rem;font-size:.875rem;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;color:rgba(0,0,0,.75);line-height:normal;border-radius:0;height:2.3125rem}select::-ms-expand{display:none}select.radius{border-radius:3px}select:hover{background-color:#f3f3f3;border-color:#999}select:disabled{background-color:#ddd;cursor:default}input[type=file],input[type=checkbox],input[type=radio],select{margin:0 0 1rem 0}input[type=checkbox]+label,input[type=radio]+label{display:inline-block;margin-left:.5rem;margin-right:1rem;margin-bottom:0;vertical-align:baseline}input[type=file]{width:100%}fieldset{border:1px solid #ddd;padding:1.25rem;margin:1.125rem 0}fieldset legend{font-weight:bold;background:#fff;padding:0 .1875rem;margin:0;margin-left:-0.1875rem}[data-abide] .error small.error,[data-abide] .error span.error,[data-abide] span.error,[data-abide] small.error{display:block;padding:.375rem .5625rem .5625rem;margin-top:-1px;margin-bottom:1rem;font-size:.75rem;font-weight:normal;font-style:italic;background:#df4949;color:#fff}[data-abide] span.error,[data-abide] small.error{display:none}span.error,small.error{display:block;padding:.375rem .5625rem .5625rem;margin-top:-1px;margin-bottom:1rem;font-size:.75rem;font-weight:normal;font-style:italic;background:#df4949;color:#fff}.error input,.error textarea,.error select{margin-bottom:0}.error input[type=checkbox],.error input[type=radio]{margin-bottom:1rem}.error label,.error label.error{color:#df4949}.error small.error{display:block;padding:.375rem .5625rem .5625rem;margin-top:-1px;margin-bottom:1rem;font-size:.75rem;font-weight:normal;font-style:italic;background:#df4949;color:#fff}.error>label>small{color:#676767;background:rgba(0,0,0,0);padding:0;text-transform:capitalize;font-style:normal;font-size:60%;margin:0;display:inline}.error span.error-message{display:block}input.error,textarea.error,select.error{margin-bottom:0}label.error{color:#df4949}meta.foundation-mq-topbar{font-family:"/only screen and (min-width: 64.063em)/";width:64.063em}.contain-to-grid{width:100%;background:#fdfdfd}.contain-to-grid .top-bar{margin-bottom:0}.fixed{width:100%;left:0;position:fixed;top:0;z-index:99}.fixed.expanded:not(.top-bar){overflow-y:auto;height:auto;width:100%;max-height:100%}.fixed.expanded:not(.top-bar) .title-area{position:fixed;width:100%;z-index:99}.fixed.expanded:not(.top-bar) .top-bar-section{z-index:98;margin-top:3.125rem}.top-bar{overflow:hidden;height:3.125rem;line-height:3.125rem;position:relative;background:#fdfdfd;margin-bottom:0}.top-bar ul{margin-bottom:0;list-style:none}.top-bar .row{max-width:none}.top-bar form,.top-bar input{margin-bottom:0}.top-bar input{height:1.75rem;padding-top:.35rem;padding-bottom:.35rem;font-size:.75rem}.top-bar .button,.top-bar button{padding-top:.4125rem;padding-bottom:.4125rem;margin-bottom:0;font-size:.75rem}@media only screen and (max-width: 40em){.top-bar .button,.top-bar button{position:relative;top:-1px}}.top-bar .title-area{position:relative;margin:0}.top-bar .name{height:3.125rem;margin:0;font-size:16px}.top-bar .name h1,.top-bar .name h2,.top-bar .name h3,.top-bar .name h4,.top-bar .name p,.top-bar .name span{line-height:3.125rem;font-size:1.1875rem;margin:0}.top-bar .name h1 a,.top-bar .name h2 a,.top-bar .name h3 a,.top-bar .name h4 a,.top-bar .name p a,.top-bar .name span a{font-weight:bold;color:#000;width:75%;display:block;padding:0 1.0416666667rem}.top-bar .toggle-topbar{position:absolute;right:0;top:0}.top-bar .toggle-topbar a{color:#000;text-transform:uppercase;font-size:.8125rem;font-weight:bold;position:relative;display:block;padding:0 1.0416666667rem;height:3.125rem;line-height:3.125rem}.top-bar .toggle-topbar.menu-icon{top:50%;margin-top:-16px}.top-bar .toggle-topbar.menu-icon a{height:34px;line-height:33px;padding:0 2.6041666667rem 0 1.0416666667rem;color:#000;position:relative}.top-bar .toggle-topbar.menu-icon a span::after{content:"";position:absolute;display:block;height:0;top:50%;margin-top:-8px;right:1.0416666667rem;box-shadow:0 0 0 1px #000,0 7px 0 1px #000,0 14px 0 1px #000;width:16px}.top-bar .toggle-topbar.menu-icon a span:hover:after{box-shadow:0 0 0 1px "",0 7px 0 1px "",0 14px 0 1px ""}.top-bar.expanded{height:auto;background:rgba(0,0,0,0)}.top-bar.expanded .title-area{background:#fdfdfd}.top-bar.expanded .toggle-topbar a{color:#a1d044}.top-bar.expanded .toggle-topbar a span::after{box-shadow:0 0 0 1px #a1d044,0 7px 0 1px #a1d044,0 14px 0 1px #a1d044}.top-bar-section{left:0;position:relative;width:auto;transition:left 300ms ease-out}.top-bar-section ul{padding:0;width:100%;height:auto;display:block;font-size:16px;margin:0}.top-bar-section .divider,.top-bar-section [role=separator]{border-top:solid 0px #7f7f7f;clear:both;height:1px;width:100%}.top-bar-section ul li{background:#a1d044}.top-bar-section ul li>a{display:block;width:100%;color:#000;padding:12px 0 12px 0;padding-left:1.0416666667rem;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-size:.9375rem;font-weight:normal;text-transform:uppercase}.top-bar-section ul li>a.button{font-size:.9375rem;padding-right:1.0416666667rem;padding-left:1.0416666667rem;background-color:#334d5c;border-color:#293e4a;color:#fff}.top-bar-section ul li>a.button:hover,.top-bar-section ul li>a.button:focus{background-color:#293e4a}.top-bar-section ul li>a.button:hover,.top-bar-section ul li>a.button:focus{color:#fff}.top-bar-section ul li>a.button.secondary{background-color:#a1d044;border-color:#84b02c;color:#fff}.top-bar-section ul li>a.button.secondary:hover,.top-bar-section ul li>a.button.secondary:focus{background-color:#84b02c}.top-bar-section ul li>a.button.secondary:hover,.top-bar-section ul li>a.button.secondary:focus{color:#fff}.top-bar-section ul li>a.button.success{background-color:#a1d044;border-color:#84b02c;color:#fff}.top-bar-section ul li>a.button.success:hover,.top-bar-section ul li>a.button.success:focus{background-color:#84b02c}.top-bar-section ul li>a.button.success:hover,.top-bar-section ul li>a.button.success:focus{color:#fff}.top-bar-section ul li>a.button.alert{background-color:#df4949;border-color:#c92323;color:#fff}.top-bar-section ul li>a.button.alert:hover,.top-bar-section ul li>a.button.alert:focus{background-color:#c92323}.top-bar-section ul li>a.button.alert:hover,.top-bar-section ul li>a.button.alert:focus{color:#fff}.top-bar-section ul li>a.button.warning{background-color:#be6409;border-color:#985007;color:#fff}.top-bar-section ul li>a.button.warning:hover,.top-bar-section ul li>a.button.warning:focus{background-color:#985007}.top-bar-section ul li>a.button.warning:hover,.top-bar-section ul li>a.button.warning:focus{color:#fff}.top-bar-section ul li>button{font-size:.9375rem;padding-right:1.0416666667rem;padding-left:1.0416666667rem;background-color:#334d5c;border-color:#293e4a;color:#fff}.top-bar-section ul li>button:hover,.top-bar-section ul li>button:focus{background-color:#293e4a}.top-bar-section ul li>button:hover,.top-bar-section ul li>button:focus{color:#fff}.top-bar-section ul li>button.secondary{background-color:#a1d044;border-color:#84b02c;color:#fff}.top-bar-section ul li>button.secondary:hover,.top-bar-section ul li>button.secondary:focus{background-color:#84b02c}.top-bar-section ul li>button.secondary:hover,.top-bar-section ul li>button.secondary:focus{color:#fff}.top-bar-section ul li>button.success{background-color:#a1d044;border-color:#84b02c;color:#fff}.top-bar-section ul li>button.success:hover,.top-bar-section ul li>button.success:focus{background-color:#84b02c}.top-bar-section ul li>button.success:hover,.top-bar-section ul li>button.success:focus{color:#fff}.top-bar-section ul li>button.alert{background-color:#df4949;border-color:#c92323;color:#fff}.top-bar-section ul li>button.alert:hover,.top-bar-section ul li>button.alert:focus{background-color:#c92323}.top-bar-section ul li>button.alert:hover,.top-bar-section ul li>button.alert:focus{color:#fff}.top-bar-section ul li>button.warning{background-color:#be6409;border-color:#985007;color:#fff}.top-bar-section ul li>button.warning:hover,.top-bar-section ul li>button.warning:focus{background-color:#985007}.top-bar-section ul li>button.warning:hover,.top-bar-section ul li>button.warning:focus{color:#fff}.top-bar-section ul li:hover:not(.has-form)>a{background-color:#555;background:#a1d044;color:#000}.top-bar-section ul li.active>a{background:#a1d044;color:#000}.top-bar-section ul li.active>a:hover{background:#45b29d;color:#000}.top-bar-section .has-form{padding:1.0416666667rem}.top-bar-section .has-dropdown{position:relative}.top-bar-section .has-dropdown>a:after{content:"";display:block;width:0;height:0;border:inset 5px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0) rgba(51,77,92,.4);border-left-style:solid;margin-right:1.0416666667rem;margin-top:-4.5px;position:absolute;top:50%;right:0}.top-bar-section .has-dropdown.moved{position:static}.top-bar-section .has-dropdown.moved>.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important;width:100%}.top-bar-section .has-dropdown.moved>a:after{display:none}.top-bar-section .dropdown{padding:0;position:absolute;left:100%;top:0;z-index:99;display:block;position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}.top-bar-section .dropdown li{width:100%;height:auto}.top-bar-section .dropdown li a{font-weight:normal;padding:8px 1.0416666667rem}.top-bar-section .dropdown li a.parent-link{font-weight:normal}.top-bar-section .dropdown li.title h5,.top-bar-section .dropdown li.parent-link{margin-bottom:0;margin-top:0;font-size:1.125rem}.top-bar-section .dropdown li.title h5 a,.top-bar-section .dropdown li.parent-link a{color:#000;display:block}.top-bar-section .dropdown li.title h5 a:hover,.top-bar-section .dropdown li.parent-link a:hover{background:none}.top-bar-section .dropdown li.has-form{padding:8px 1.0416666667rem}.top-bar-section .dropdown li .button,.top-bar-section .dropdown li button{top:auto}.top-bar-section .dropdown label{padding:8px 1.0416666667rem 2px;margin-bottom:0;text-transform:uppercase;color:#45b29d;font-weight:bold;font-size:.625rem}.js-generated{display:block}@media only screen and (min-width: 64.063em){.top-bar{background:#fdfdfd;overflow:visible}.top-bar:before,.top-bar:after{content:" ";display:table}.top-bar:after{clear:both}.top-bar .toggle-topbar{display:none}.top-bar .title-area{float:left}.top-bar .name h1 a{width:auto}.top-bar input,.top-bar .button,.top-bar button{font-size:.875rem;position:relative;height:1.75rem;top:.6875rem}.top-bar.expanded{background:#fdfdfd}.contain-to-grid .top-bar{max-width:93.75rem;margin:0 auto;margin-bottom:0}.top-bar-section{transition:none 0 0;left:0 !important}.top-bar-section ul{width:auto;height:auto !important;display:inline}.top-bar-section ul li{float:left}.top-bar-section ul li .js-generated{display:none}.top-bar-section li.hover>a:not(.button){background-color:#555;background:#a1d044;color:#000}.top-bar-section li:not(.has-form) a:not(.button){padding:0 1.0416666667rem;line-height:3.125rem;background:#fdfdfd}.top-bar-section li:not(.has-form) a:not(.button):hover{background-color:#555;background:#a1d044}.top-bar-section li.active:not(.has-form) a:not(.button){padding:0 1.0416666667rem;line-height:3.125rem;color:#000;background:#a1d044}.top-bar-section li.active:not(.has-form) a:not(.button):hover{background:#45b29d;color:#000}.top-bar-section .has-dropdown>a{padding-right:2.2916666667rem !important}.top-bar-section .has-dropdown>a:after{content:"";display:block;width:0;height:0;border:inset 5px;border-color:rgba(51,77,92,.4) rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0);border-top-style:solid;margin-top:-2.5px;top:1.5625rem}.top-bar-section .has-dropdown.moved{position:relative}.top-bar-section .has-dropdown.moved>.dropdown{display:block;position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}.top-bar-section .has-dropdown.hover>.dropdown,.top-bar-section .has-dropdown.not-click:hover>.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important}.top-bar-section .has-dropdown>a:focus+.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important}.top-bar-section .has-dropdown .dropdown li.has-dropdown>a:after{border:none;content:"»";top:1rem;margin-top:-1px;right:5px;line-height:1.2}.top-bar-section .dropdown{left:0;top:auto;background:rgba(0,0,0,0);min-width:100%}.top-bar-section .dropdown li a{color:#000;line-height:3.125rem;white-space:nowrap;padding:12px 1.0416666667rem;background:#45b29d}.top-bar-section .dropdown li:not(.has-form):not(.active)>a:not(.button){color:#000;background:#45b29d}.top-bar-section .dropdown li:not(.has-form):not(.active):hover>a:not(.button){color:#000;background-color:#555;background:#a1d044}.top-bar-section .dropdown li label{white-space:nowrap;background:#333}.top-bar-section .dropdown li .dropdown{left:100%;top:0}.top-bar-section>ul>.divider,.top-bar-section>ul>[role=separator]{border-bottom:none;border-top:none;border-right:solid 0px #fdfdfd;clear:none;height:3.125rem;width:0}.top-bar-section .has-form{background:#fdfdfd;padding:0 1.0416666667rem;height:3.125rem}.top-bar-section .right li .dropdown{left:auto;right:0}.top-bar-section .right li .dropdown li .dropdown{right:100%}.top-bar-section .left li .dropdown{right:auto;left:0}.top-bar-section .left li .dropdown li .dropdown{left:100%}.no-js .top-bar-section ul li:hover>a{background-color:#555;background:#a1d044;color:#000}.no-js .top-bar-section ul li:active>a{background:#a1d044;color:#000}.no-js .top-bar-section .has-dropdown:hover>.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important}.no-js .top-bar-section .has-dropdown>a:focus+.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important}}.accordion{margin-bottom:0}.accordion:before,.accordion:after{content:" ";display:table}.accordion:after{clear:both}.accordion .accordion-navigation,.accordion dd{display:block;margin-bottom:0 !important}.accordion .accordion-navigation.active>a,.accordion dd.active>a{background:#e8e8e8}.accordion .accordion-navigation>a,.accordion dd>a{background:#efefef;color:#222;padding:.75rem;display:block;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-size:1rem}.accordion .accordion-navigation>a:hover,.accordion dd>a:hover{background:#e3e3e3}.accordion .accordion-navigation>.content,.accordion dd>.content{display:none;padding:.9375rem}.accordion .accordion-navigation>.content.active,.accordion dd>.content.active{display:block;background:#fdfdfd}.alert-box{border-style:solid;border-width:1px;display:block;font-weight:normal;margin-bottom:1.25rem;position:relative;padding:.875rem 1.5rem .875rem .875rem;font-size:.9375rem;transition:opacity 300ms ease-out;background-color:#334d5c;border-color:#2c424f;color:#fff}.alert-box .close{font-size:1.375rem;padding:9px 6px 4px;line-height:0;position:absolute;top:50%;margin-top:-0.6875rem;right:.25rem;color:#333;opacity:.3;background:inherit}.alert-box .close:hover,.alert-box .close:focus{opacity:.5}.alert-box.radius{border-radius:3px}.alert-box.round{border-radius:1000px}.alert-box.success{background-color:#a1d044;border-color:#8ebe30;color:#fff}.alert-box.alert{background-color:#df4949;border-color:#d82626;color:#fff}.alert-box.secondary{background-color:#a1d044;border-color:#8ebe30;color:#fff}.alert-box.warning{background-color:#be6409;border-color:#a35608;color:#fff}.alert-box.info{background-color:#334d5c;border-color:#2c424f;color:#fff}.alert-box.alert-close{opacity:0}.breadcrumbs{display:block;padding:.5625rem .875rem .5625rem;overflow:hidden;margin-left:0;list-style:none;border-style:solid;border-width:0;background-color:#e4e4e4;border-color:#e4e4e4;border-radius:0}.breadcrumbs>*{margin:0;float:left;font-size:.6875rem;line-height:.6875rem;text-transform:uppercase;color:#334d5c}.breadcrumbs>*:hover a,.breadcrumbs>*:focus a{text-decoration:underline}.breadcrumbs>* a{color:#334d5c}.breadcrumbs>*.current{cursor:default;color:#333}.breadcrumbs>*.current a{cursor:default;color:#333}.breadcrumbs>*.current:hover,.breadcrumbs>*.current:hover a,.breadcrumbs>*.current:focus,.breadcrumbs>*.current:focus a{text-decoration:none}.breadcrumbs>*.unavailable{color:#999}.breadcrumbs>*.unavailable a{color:#999}.breadcrumbs>*.unavailable:hover,.breadcrumbs>*.unavailable:hover a,.breadcrumbs>*.unavailable:focus,.breadcrumbs>*.unavailable a:focus{text-decoration:none;color:#999;cursor:default}.breadcrumbs>*:before{content:"/";color:#aaa;margin:0 .75rem;position:relative;top:1px}.breadcrumbs>*:first-child:before{content:" ";margin:0}[aria-label=breadcrumbs] [aria-hidden=true]:after{content:"/"}[class*=block-grid-]{display:block;padding:0;margin:0 -0.625rem}[class*=block-grid-]:before,[class*=block-grid-]:after{content:" ";display:table}[class*=block-grid-]:after{clear:both}[class*=block-grid-]>li{display:block;height:auto;float:left;padding:0 .625rem 1.25rem}@media only screen{.small-block-grid-1>li{width:100%;list-style:none}.small-block-grid-1>li:nth-of-type(1n){clear:none}.small-block-grid-1>li:nth-of-type(1n+1){clear:both}.small-block-grid-2>li{width:50%;list-style:none}.small-block-grid-2>li:nth-of-type(1n){clear:none}.small-block-grid-2>li:nth-of-type(2n+1){clear:both}.small-block-grid-3>li{width:33.3333333333%;list-style:none}.small-block-grid-3>li:nth-of-type(1n){clear:none}.small-block-grid-3>li:nth-of-type(3n+1){clear:both}.small-block-grid-4>li{width:25%;list-style:none}.small-block-grid-4>li:nth-of-type(1n){clear:none}.small-block-grid-4>li:nth-of-type(4n+1){clear:both}.small-block-grid-5>li{width:20%;list-style:none}.small-block-grid-5>li:nth-of-type(1n){clear:none}.small-block-grid-5>li:nth-of-type(5n+1){clear:both}.small-block-grid-6>li{width:16.6666666667%;list-style:none}.small-block-grid-6>li:nth-of-type(1n){clear:none}.small-block-grid-6>li:nth-of-type(6n+1){clear:both}.small-block-grid-7>li{width:14.2857142857%;list-style:none}.small-block-grid-7>li:nth-of-type(1n){clear:none}.small-block-grid-7>li:nth-of-type(7n+1){clear:both}.small-block-grid-8>li{width:12.5%;list-style:none}.small-block-grid-8>li:nth-of-type(1n){clear:none}.small-block-grid-8>li:nth-of-type(8n+1){clear:both}.small-block-grid-9>li{width:11.1111111111%;list-style:none}.small-block-grid-9>li:nth-of-type(1n){clear:none}.small-block-grid-9>li:nth-of-type(9n+1){clear:both}.small-block-grid-10>li{width:10%;list-style:none}.small-block-grid-10>li:nth-of-type(1n){clear:none}.small-block-grid-10>li:nth-of-type(10n+1){clear:both}.small-block-grid-11>li{width:9.0909090909%;list-style:none}.small-block-grid-11>li:nth-of-type(1n){clear:none}.small-block-grid-11>li:nth-of-type(11n+1){clear:both}.small-block-grid-12>li{width:8.3333333333%;list-style:none}.small-block-grid-12>li:nth-of-type(1n){clear:none}.small-block-grid-12>li:nth-of-type(12n+1){clear:both}}@media only screen and (min-width:40.063em){.medium-block-grid-1>li{width:100%;list-style:none}.medium-block-grid-1>li:nth-of-type(1n){clear:none}.medium-block-grid-1>li:nth-of-type(1n+1){clear:both}.medium-block-grid-2>li{width:50%;list-style:none}.medium-block-grid-2>li:nth-of-type(1n){clear:none}.medium-block-grid-2>li:nth-of-type(2n+1){clear:both}.medium-block-grid-3>li{width:33.3333333333%;list-style:none}.medium-block-grid-3>li:nth-of-type(1n){clear:none}.medium-block-grid-3>li:nth-of-type(3n+1){clear:both}.medium-block-grid-4>li{width:25%;list-style:none}.medium-block-grid-4>li:nth-of-type(1n){clear:none}.medium-block-grid-4>li:nth-of-type(4n+1){clear:both}.medium-block-grid-5>li{width:20%;list-style:none}.medium-block-grid-5>li:nth-of-type(1n){clear:none}.medium-block-grid-5>li:nth-of-type(5n+1){clear:both}.medium-block-grid-6>li{width:16.6666666667%;list-style:none}.medium-block-grid-6>li:nth-of-type(1n){clear:none}.medium-block-grid-6>li:nth-of-type(6n+1){clear:both}.medium-block-grid-7>li{width:14.2857142857%;list-style:none}.medium-block-grid-7>li:nth-of-type(1n){clear:none}.medium-block-grid-7>li:nth-of-type(7n+1){clear:both}.medium-block-grid-8>li{width:12.5%;list-style:none}.medium-block-grid-8>li:nth-of-type(1n){clear:none}.medium-block-grid-8>li:nth-of-type(8n+1){clear:both}.medium-block-grid-9>li{width:11.1111111111%;list-style:none}.medium-block-grid-9>li:nth-of-type(1n){clear:none}.medium-block-grid-9>li:nth-of-type(9n+1){clear:both}.medium-block-grid-10>li{width:10%;list-style:none}.medium-block-grid-10>li:nth-of-type(1n){clear:none}.medium-block-grid-10>li:nth-of-type(10n+1){clear:both}.medium-block-grid-11>li{width:9.0909090909%;list-style:none}.medium-block-grid-11>li:nth-of-type(1n){clear:none}.medium-block-grid-11>li:nth-of-type(11n+1){clear:both}.medium-block-grid-12>li{width:8.3333333333%;list-style:none}.medium-block-grid-12>li:nth-of-type(1n){clear:none}.medium-block-grid-12>li:nth-of-type(12n+1){clear:both}}@media only screen and (min-width:64.063em){.large-block-grid-1>li{width:100%;list-style:none}.large-block-grid-1>li:nth-of-type(1n){clear:none}.large-block-grid-1>li:nth-of-type(1n+1){clear:both}.large-block-grid-2>li{width:50%;list-style:none}.large-block-grid-2>li:nth-of-type(1n){clear:none}.large-block-grid-2>li:nth-of-type(2n+1){clear:both}.large-block-grid-3>li{width:33.3333333333%;list-style:none}.large-block-grid-3>li:nth-of-type(1n){clear:none}.large-block-grid-3>li:nth-of-type(3n+1){clear:both}.large-block-grid-4>li{width:25%;list-style:none}.large-block-grid-4>li:nth-of-type(1n){clear:none}.large-block-grid-4>li:nth-of-type(4n+1){clear:both}.large-block-grid-5>li{width:20%;list-style:none}.large-block-grid-5>li:nth-of-type(1n){clear:none}.large-block-grid-5>li:nth-of-type(5n+1){clear:both}.large-block-grid-6>li{width:16.6666666667%;list-style:none}.large-block-grid-6>li:nth-of-type(1n){clear:none}.large-block-grid-6>li:nth-of-type(6n+1){clear:both}.large-block-grid-7>li{width:14.2857142857%;list-style:none}.large-block-grid-7>li:nth-of-type(1n){clear:none}.large-block-grid-7>li:nth-of-type(7n+1){clear:both}.large-block-grid-8>li{width:12.5%;list-style:none}.large-block-grid-8>li:nth-of-type(1n){clear:none}.large-block-grid-8>li:nth-of-type(8n+1){clear:both}.large-block-grid-9>li{width:11.1111111111%;list-style:none}.large-block-grid-9>li:nth-of-type(1n){clear:none}.large-block-grid-9>li:nth-of-type(9n+1){clear:both}.large-block-grid-10>li{width:10%;list-style:none}.large-block-grid-10>li:nth-of-type(1n){clear:none}.large-block-grid-10>li:nth-of-type(10n+1){clear:both}.large-block-grid-11>li{width:9.0909090909%;list-style:none}.large-block-grid-11>li:nth-of-type(1n){clear:none}.large-block-grid-11>li:nth-of-type(11n+1){clear:both}.large-block-grid-12>li{width:8.3333333333%;list-style:none}.large-block-grid-12>li:nth-of-type(1n){clear:none}.large-block-grid-12>li:nth-of-type(12n+1){clear:both}}.button-group{list-style:none;margin:0;left:0}.button-group:before,.button-group:after{content:" ";display:table}.button-group:after{clear:both}.button-group>li{margin:0 -2px;display:inline-block}.button-group>li>button,.button-group>li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group>li:first-child button,.button-group>li:first-child .button{border-left:0}.button-group.stack>li{margin:0 -2px;display:inline-block;display:block;margin:0;float:none}.button-group.stack>li>button,.button-group.stack>li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.stack>li:first-child button,.button-group.stack>li:first-child .button{border-left:0}.button-group.stack>li>button,.button-group.stack>li .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.stack>li:first-child button,.button-group.stack>li:first-child .button{border-top:0}.button-group.stack-for-small>li{margin:0 -2px;display:inline-block}.button-group.stack-for-small>li>button,.button-group.stack-for-small>li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.stack-for-small>li:first-child button,.button-group.stack-for-small>li:first-child .button{border-left:0}@media only screen and (max-width: 40em){.button-group.stack-for-small>li{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.stack-for-small>li>button,.button-group.stack-for-small>li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.stack-for-small>li:first-child button,.button-group.stack-for-small>li:first-child .button{border-left:0}.button-group.stack-for-small>li>button,.button-group.stack-for-small>li .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.stack-for-small>li:first-child button,.button-group.stack-for-small>li:first-child .button{border-top:0}}.button-group.radius>*{margin:0 -2px;display:inline-block}.button-group.radius>*>button,.button-group.radius>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.radius>*:first-child button,.button-group.radius>*:first-child .button{border-left:0}.button-group.radius>*,.button-group.radius>*>a,.button-group.radius>*>button,.button-group.radius>*>.button{border-radius:0}.button-group.radius>*:first-child,.button-group.radius>*:first-child>a,.button-group.radius>*:first-child>button,.button-group.radius>*:first-child>.button{-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}.button-group.radius>*:last-child,.button-group.radius>*:last-child>a,.button-group.radius>*:last-child>button,.button-group.radius>*:last-child>.button{-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}.button-group.radius.stack>*{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.radius.stack>*>button,.button-group.radius.stack>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.radius.stack>*:first-child button,.button-group.radius.stack>*:first-child .button{border-left:0}.button-group.radius.stack>*>button,.button-group.radius.stack>* .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.radius.stack>*:first-child button,.button-group.radius.stack>*:first-child .button{border-top:0}.button-group.radius.stack>*,.button-group.radius.stack>*>a,.button-group.radius.stack>*>button,.button-group.radius.stack>*>.button{border-radius:0}.button-group.radius.stack>*:first-child,.button-group.radius.stack>*:first-child>a,.button-group.radius.stack>*:first-child>button,.button-group.radius.stack>*:first-child>.button{-webkit-top-left-radius:3px;-webkit-top-right-radius:3px;border-top-left-radius:3px;border-top-right-radius:3px}.button-group.radius.stack>*:last-child,.button-group.radius.stack>*:last-child>a,.button-group.radius.stack>*:last-child>button,.button-group.radius.stack>*:last-child>.button{-webkit-bottom-left-radius:3px;-webkit-bottom-right-radius:3px;border-bottom-left-radius:3px;border-bottom-right-radius:3px}@media only screen and (min-width:40.063em){.button-group.radius.stack-for-small>*{margin:0 -2px;display:inline-block}.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.radius.stack-for-small>*:first-child button,.button-group.radius.stack-for-small>*:first-child .button{border-left:0}.button-group.radius.stack-for-small>*,.button-group.radius.stack-for-small>*>a,.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>*>.button{border-radius:0}.button-group.radius.stack-for-small>*:first-child,.button-group.radius.stack-for-small>*:first-child>a,.button-group.radius.stack-for-small>*:first-child>button,.button-group.radius.stack-for-small>*:first-child>.button{-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}.button-group.radius.stack-for-small>*:last-child,.button-group.radius.stack-for-small>*:last-child>a,.button-group.radius.stack-for-small>*:last-child>button,.button-group.radius.stack-for-small>*:last-child>.button{-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}}@media only screen and (max-width: 40em){.button-group.radius.stack-for-small>*{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.radius.stack-for-small>*:first-child button,.button-group.radius.stack-for-small>*:first-child .button{border-left:0}.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>* .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.radius.stack-for-small>*:first-child button,.button-group.radius.stack-for-small>*:first-child .button{border-top:0}.button-group.radius.stack-for-small>*,.button-group.radius.stack-for-small>*>a,.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>*>.button{border-radius:0}.button-group.radius.stack-for-small>*:first-child,.button-group.radius.stack-for-small>*:first-child>a,.button-group.radius.stack-for-small>*:first-child>button,.button-group.radius.stack-for-small>*:first-child>.button{-webkit-top-left-radius:3px;-webkit-top-right-radius:3px;border-top-left-radius:3px;border-top-right-radius:3px}.button-group.radius.stack-for-small>*:last-child,.button-group.radius.stack-for-small>*:last-child>a,.button-group.radius.stack-for-small>*:last-child>button,.button-group.radius.stack-for-small>*:last-child>.button{-webkit-bottom-left-radius:3px;-webkit-bottom-right-radius:3px;border-bottom-left-radius:3px;border-bottom-right-radius:3px}}.button-group.round>*{margin:0 -2px;display:inline-block}.button-group.round>*>button,.button-group.round>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.round>*:first-child button,.button-group.round>*:first-child .button{border-left:0}.button-group.round>*,.button-group.round>*>a,.button-group.round>*>button,.button-group.round>*>.button{border-radius:0}.button-group.round>*:first-child,.button-group.round>*:first-child>a,.button-group.round>*:first-child>button,.button-group.round>*:first-child>.button{-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}.button-group.round>*:last-child,.button-group.round>*:last-child>a,.button-group.round>*:last-child>button,.button-group.round>*:last-child>.button{-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}.button-group.round.stack>*{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.round.stack>*>button,.button-group.round.stack>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.round.stack>*:first-child button,.button-group.round.stack>*:first-child .button{border-left:0}.button-group.round.stack>*>button,.button-group.round.stack>* .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.round.stack>*:first-child button,.button-group.round.stack>*:first-child .button{border-top:0}.button-group.round.stack>*,.button-group.round.stack>*>a,.button-group.round.stack>*>button,.button-group.round.stack>*>.button{border-radius:0}.button-group.round.stack>*:first-child,.button-group.round.stack>*:first-child>a,.button-group.round.stack>*:first-child>button,.button-group.round.stack>*:first-child>.button{-webkit-top-left-radius:1rem;-webkit-top-right-radius:1rem;border-top-left-radius:1rem;border-top-right-radius:1rem}.button-group.round.stack>*:last-child,.button-group.round.stack>*:last-child>a,.button-group.round.stack>*:last-child>button,.button-group.round.stack>*:last-child>.button{-webkit-bottom-left-radius:1rem;-webkit-bottom-right-radius:1rem;border-bottom-left-radius:1rem;border-bottom-right-radius:1rem}@media only screen and (min-width:40.063em){.button-group.round.stack-for-small>*{margin:0 -2px;display:inline-block}.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.round.stack-for-small>*:first-child button,.button-group.round.stack-for-small>*:first-child .button{border-left:0}.button-group.round.stack-for-small>*,.button-group.round.stack-for-small>*>a,.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>*>.button{border-radius:0}.button-group.round.stack-for-small>*:first-child,.button-group.round.stack-for-small>*:first-child>a,.button-group.round.stack-for-small>*:first-child>button,.button-group.round.stack-for-small>*:first-child>.button{-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}.button-group.round.stack-for-small>*:last-child,.button-group.round.stack-for-small>*:last-child>a,.button-group.round.stack-for-small>*:last-child>button,.button-group.round.stack-for-small>*:last-child>.button{-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}}@media only screen and (max-width: 40em){.button-group.round.stack-for-small>*{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.round.stack-for-small>*:first-child button,.button-group.round.stack-for-small>*:first-child .button{border-left:0}.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>* .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.round.stack-for-small>*:first-child button,.button-group.round.stack-for-small>*:first-child .button{border-top:0}.button-group.round.stack-for-small>*,.button-group.round.stack-for-small>*>a,.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>*>.button{border-radius:0}.button-group.round.stack-for-small>*:first-child,.button-group.round.stack-for-small>*:first-child>a,.button-group.round.stack-for-small>*:first-child>button,.button-group.round.stack-for-small>*:first-child>.button{-webkit-top-left-radius:1rem;-webkit-top-right-radius:1rem;border-top-left-radius:1rem;border-top-right-radius:1rem}.button-group.round.stack-for-small>*:last-child,.button-group.round.stack-for-small>*:last-child>a,.button-group.round.stack-for-small>*:last-child>button,.button-group.round.stack-for-small>*:last-child>.button{-webkit-bottom-left-radius:1rem;-webkit-bottom-right-radius:1rem;border-bottom-left-radius:1rem;border-bottom-right-radius:1rem}}.button-group.even-2 li{margin:0 -2px;display:inline-block;width:50%}.button-group.even-2 li>button,.button-group.even-2 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-2 li:first-child button,.button-group.even-2 li:first-child .button{border-left:0}.button-group.even-2 li button,.button-group.even-2 li .button{width:100%}.button-group.even-3 li{margin:0 -2px;display:inline-block;width:33.3333333333%}.button-group.even-3 li>button,.button-group.even-3 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-3 li:first-child button,.button-group.even-3 li:first-child .button{border-left:0}.button-group.even-3 li button,.button-group.even-3 li .button{width:100%}.button-group.even-4 li{margin:0 -2px;display:inline-block;width:25%}.button-group.even-4 li>button,.button-group.even-4 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-4 li:first-child button,.button-group.even-4 li:first-child .button{border-left:0}.button-group.even-4 li button,.button-group.even-4 li .button{width:100%}.button-group.even-5 li{margin:0 -2px;display:inline-block;width:20%}.button-group.even-5 li>button,.button-group.even-5 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-5 li:first-child button,.button-group.even-5 li:first-child .button{border-left:0}.button-group.even-5 li button,.button-group.even-5 li .button{width:100%}.button-group.even-6 li{margin:0 -2px;display:inline-block;width:16.6666666667%}.button-group.even-6 li>button,.button-group.even-6 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-6 li:first-child button,.button-group.even-6 li:first-child .button{border-left:0}.button-group.even-6 li button,.button-group.even-6 li .button{width:100%}.button-group.even-7 li{margin:0 -2px;display:inline-block;width:14.2857142857%}.button-group.even-7 li>button,.button-group.even-7 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-7 li:first-child button,.button-group.even-7 li:first-child .button{border-left:0}.button-group.even-7 li button,.button-group.even-7 li .button{width:100%}.button-group.even-8 li{margin:0 -2px;display:inline-block;width:12.5%}.button-group.even-8 li>button,.button-group.even-8 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-8 li:first-child button,.button-group.even-8 li:first-child .button{border-left:0}.button-group.even-8 li button,.button-group.even-8 li .button{width:100%}.button-bar:before,.button-bar:after{content:" ";display:table}.button-bar:after{clear:both}.button-bar .button-group{float:left;margin-right:.625rem}.button-bar .button-group div{overflow:hidden}.clearing-thumbs,[data-clearing]{margin-bottom:0;margin-left:0;list-style:none}.clearing-thumbs:before,.clearing-thumbs:after,[data-clearing]:before,[data-clearing]:after{content:" ";display:table}.clearing-thumbs:after,[data-clearing]:after{clear:both}.clearing-thumbs li,[data-clearing] li{float:left;margin-right:10px}.clearing-thumbs[class*=block-grid-] li,[data-clearing][class*=block-grid-] li{margin-right:0}.clearing-blackout{background:#333;position:fixed;width:100%;height:100%;top:0;left:0;z-index:998}.clearing-blackout .clearing-close{display:block}.clearing-container{position:relative;z-index:998;height:100%;overflow:hidden;margin:0}.clearing-touch-label{position:absolute;top:50%;left:50%;color:#aaa;font-size:.6em}.visible-img{height:95%;position:relative}.visible-img img{position:absolute;left:50%;top:50%;margin-left:-50%;max-height:100%;max-width:100%}.clearing-caption{color:#ccc;font-size:.875em;line-height:1.3;margin-bottom:0;text-align:center;bottom:0;background:#333;width:100%;padding:10px 30px 20px;position:absolute;left:0}.clearing-close{z-index:999;padding-left:20px;padding-top:10px;font-size:30px;line-height:1;color:#ccc;display:none}.clearing-close:hover,.clearing-close:focus{color:#ccc}.clearing-assembled .clearing-container{height:100%}.clearing-assembled .clearing-container .carousel>ul{display:none}.clearing-feature li{display:none}.clearing-feature li.clearing-featured-img{display:block}@media only screen and (min-width:40.063em){.clearing-main-prev,.clearing-main-next{position:absolute;height:100%;width:40px;top:0}.clearing-main-prev>span,.clearing-main-next>span{position:absolute;top:50%;display:block;width:0;height:0;border:solid 12px}.clearing-main-prev>span:hover,.clearing-main-next>span:hover{opacity:.8}.clearing-main-prev{left:0}.clearing-main-prev>span{left:5px;border-color:rgba(0,0,0,0);border-right-color:#ccc}.clearing-main-next{right:0}.clearing-main-next>span{border-color:rgba(0,0,0,0);border-left-color:#ccc}.clearing-main-prev.disabled,.clearing-main-next.disabled{opacity:.3}.clearing-assembled .clearing-container .carousel{background:rgba(51,51,51,.8);height:120px;margin-top:10px;text-align:center}.clearing-assembled .clearing-container .carousel>ul{display:inline-block;z-index:999;height:100%;position:relative;float:none}.clearing-assembled .clearing-container .carousel>ul li{display:block;width:120px;min-height:inherit;float:left;overflow:hidden;margin-right:0;padding:0;position:relative;cursor:pointer;opacity:.4;clear:none}.clearing-assembled .clearing-container .carousel>ul li.fix-height img{height:100%;max-width:none}.clearing-assembled .clearing-container .carousel>ul li a.th{border:none;box-shadow:none;display:block}.clearing-assembled .clearing-container .carousel>ul li img{cursor:pointer !important;width:100% !important}.clearing-assembled .clearing-container .carousel>ul li.visible{opacity:1}.clearing-assembled .clearing-container .carousel>ul li:hover{opacity:.8}.clearing-assembled .clearing-container .visible-img{background:#333;overflow:hidden;height:85%}.clearing-close{position:absolute;top:10px;right:20px;padding-left:0;padding-top:0}}.f-dropdown{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;width:100%;max-height:none;height:auto;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;margin-top:2px;max-width:200px}.f-dropdown>*:first-child{margin-top:0}.f-dropdown>*:last-child{margin-bottom:0}.f-dropdown:before{content:"";display:block;width:0;height:0;border:inset 6px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) #fff rgba(0,0,0,0);border-bottom-style:solid;position:absolute;top:-12px;left:10px;z-index:89}.f-dropdown:after{content:"";display:block;width:0;height:0;border:inset 7px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) #ccc rgba(0,0,0,0);border-bottom-style:solid;position:absolute;top:-14px;left:9px;z-index:88}.f-dropdown.right:before{left:auto;right:10px}.f-dropdown.right:after{left:auto;right:9px}.f-dropdown.drop-right{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;width:100%;max-height:none;height:auto;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;margin-top:0;margin-left:2px;max-width:200px}.f-dropdown.drop-right>*:first-child{margin-top:0}.f-dropdown.drop-right>*:last-child{margin-bottom:0}.f-dropdown.drop-right:before{content:"";display:block;width:0;height:0;border:inset 6px;border-color:rgba(0,0,0,0) #fff rgba(0,0,0,0) rgba(0,0,0,0);border-right-style:solid;position:absolute;top:10px;left:-12px;z-index:89}.f-dropdown.drop-right:after{content:"";display:block;width:0;height:0;border:inset 7px;border-color:rgba(0,0,0,0) #ccc rgba(0,0,0,0) rgba(0,0,0,0);border-right-style:solid;position:absolute;top:9px;left:-14px;z-index:88}.f-dropdown.drop-left{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;width:100%;max-height:none;height:auto;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;margin-top:0;margin-left:-2px;max-width:200px}.f-dropdown.drop-left>*:first-child{margin-top:0}.f-dropdown.drop-left>*:last-child{margin-bottom:0}.f-dropdown.drop-left:before{content:"";display:block;width:0;height:0;border:inset 6px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0) #fff;border-left-style:solid;position:absolute;top:10px;right:-12px;left:auto;z-index:89}.f-dropdown.drop-left:after{content:"";display:block;width:0;height:0;border:inset 7px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0) #ccc;border-left-style:solid;position:absolute;top:9px;right:-14px;left:auto;z-index:88}.f-dropdown.drop-top{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;width:100%;max-height:none;height:auto;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;margin-top:-2px;margin-left:0;max-width:200px}.f-dropdown.drop-top>*:first-child{margin-top:0}.f-dropdown.drop-top>*:last-child{margin-bottom:0}.f-dropdown.drop-top:before{content:"";display:block;width:0;height:0;border:inset 6px;border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0);border-top-style:solid;position:absolute;top:auto;bottom:-12px;left:10px;right:auto;z-index:89}.f-dropdown.drop-top:after{content:"";display:block;width:0;height:0;border:inset 7px;border-color:#ccc rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0);border-top-style:solid;position:absolute;top:auto;bottom:-14px;left:9px;right:auto;z-index:88}.f-dropdown li{font-size:.875rem;cursor:pointer;line-height:1.125rem;margin:0}.f-dropdown li:hover,.f-dropdown li:focus{background:#eee}.f-dropdown li.radius{border-radius:3px}.f-dropdown li a{display:block;padding:.5rem;color:#555}.f-dropdown.content{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;padding:1.25rem;width:100%;height:auto;max-height:none;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;max-width:200px}.f-dropdown.content>*:first-child{margin-top:0}.f-dropdown.content>*:last-child{margin-bottom:0}.f-dropdown.tiny{max-width:200px}.f-dropdown.small{max-width:300px}.f-dropdown.medium{max-width:500px}.f-dropdown.large{max-width:800px}.f-dropdown.mega{width:100% !important;max-width:100% !important}.f-dropdown.mega.open{left:0 !important}.dropdown.button,button.dropdown{position:relative;outline:none;padding-right:3.5625rem}.dropdown.button::after,button.dropdown::after{position:absolute;content:"";width:0;height:0;display:block;border-style:solid;border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0);top:50%}.dropdown.button::after,button.dropdown::after{border-width:.375rem;right:1.40625rem;margin-top:-0.15625rem}.dropdown.button::after,button.dropdown::after{border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.dropdown.button.tiny,button.dropdown.tiny{padding-right:2.625rem}.dropdown.button.tiny:after,button.dropdown.tiny:after{border-width:.375rem;right:1.125rem;margin-top:-0.125rem}.dropdown.button.tiny::after,button.dropdown.tiny::after{border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.dropdown.button.small,button.dropdown.small{padding-right:3.0625rem}.dropdown.button.small::after,button.dropdown.small::after{border-width:.4375rem;right:1.3125rem;margin-top:-0.15625rem}.dropdown.button.small::after,button.dropdown.small::after{border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.dropdown.button.large,button.dropdown.large{padding-right:3.625rem}.dropdown.button.large::after,button.dropdown.large::after{border-width:.3125rem;right:1.71875rem;margin-top:-0.15625rem}.dropdown.button.large::after,button.dropdown.large::after{border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.dropdown.button.secondary:after,button.dropdown.secondary:after{border-color:#333 rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.flex-video{position:relative;padding-top:1.5625rem;padding-bottom:67.5%;height:0;margin-bottom:1rem;overflow:hidden}.flex-video.widescreen{padding-bottom:56.34%}.flex-video.vimeo{padding-top:0}.flex-video iframe,.flex-video object,.flex-video embed,.flex-video video{position:absolute;top:0;left:0;width:100%;height:100%}.inline-list{margin:0 auto 1.0625rem auto;margin-left:-1.375rem;margin-right:0;padding:0;list-style:none;overflow:hidden}.inline-list>li{list-style:none;float:left;margin-left:1.375rem;display:block}.inline-list>li>*{display:block}.keystroke,kbd{background-color:#ededed;border-color:#ddd;color:#222;border-style:solid;border-width:1px;margin:0;font-family:"Consolas","Menlo","Courier",monospace;font-size:inherit;padding:.125rem .25rem 0;border-radius:3px}.panel{border-style:solid;border-width:1px;border-color:#cbcbcb;margin-bottom:1.25rem;padding:1.25rem;background:#e4e4e4;color:#333}.panel>:first-child{margin-top:0}.panel>:last-child{margin-bottom:0}.panel h1,.panel h2,.panel h3,.panel h4,.panel h5,.panel h6,.panel p,.panel li,.panel dl{color:#333}.panel h1,.panel h2,.panel h3,.panel h4,.panel h5,.panel h6{line-height:1;margin-bottom:.625rem}.panel h1.subheader,.panel h2.subheader,.panel h3.subheader,.panel h4.subheader,.panel h5.subheader,.panel h6.subheader{line-height:1.4}.panel.callout{border-style:solid;border-width:1px;border-color:#cedce4;margin-bottom:1.25rem;padding:1.25rem;background:#f1f5f7;color:#333}.panel.callout>:first-child{margin-top:0}.panel.callout>:last-child{margin-bottom:0}.panel.callout h1,.panel.callout h2,.panel.callout h3,.panel.callout h4,.panel.callout h5,.panel.callout h6,.panel.callout p,.panel.callout li,.panel.callout dl{color:#333}.panel.callout h1,.panel.callout h2,.panel.callout h3,.panel.callout h4,.panel.callout h5,.panel.callout h6{line-height:1;margin-bottom:.625rem}.panel.callout h1.subheader,.panel.callout h2.subheader,.panel.callout h3.subheader,.panel.callout h4.subheader,.panel.callout h5.subheader,.panel.callout h6.subheader{line-height:1.4}.panel.callout a:not(.button){color:#334d5c}.panel.callout a:not(.button):hover,.panel.callout a:not(.button):focus{color:#2c424f}.panel.radius{border-radius:3px}.reveal-modal-bg{position:absolute;top:0;bottom:0;left:0;right:0;background:#000;background:rgba(0,0,0,.45);z-index:1004;display:none;left:0}.reveal-modal,dialog{visibility:hidden;display:none;position:absolute;z-index:1005;width:100vw;top:0;border-radius:3px;left:0;background-color:#fff;padding:1.25rem;border:solid 1px #666;box-shadow:0 0 10px rgba(0,0,0,.4);padding:1.875rem}@media only screen and (max-width: 40em){.reveal-modal,dialog{min-height:100vh}}.reveal-modal .column,dialog .column,.reveal-modal .columns,dialog .columns{min-width:0}.reveal-modal>:first-child,dialog>:first-child{margin-top:0}.reveal-modal>:last-child,dialog>:last-child{margin-bottom:0}@media only screen and (min-width:40.063em){.reveal-modal,dialog{width:80%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal,dialog{top:15.625rem}}.reveal-modal.radius,dialog.radius{border-radius:3px}.reveal-modal.round,dialog.round{border-radius:1000px}.reveal-modal.collapse,dialog.collapse{padding:0}@media only screen and (min-width:40.063em){.reveal-modal.tiny,dialog.tiny{width:30%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal.small,dialog.small{width:40%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal.medium,dialog.medium{width:60%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal.large,dialog.large{width:70%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal.xlarge,dialog.xlarge{width:95%;max-width:93.75rem;left:0;right:0;margin:0 auto}}.reveal-modal.full,dialog.full{top:0;left:0;height:100%;height:100vh;min-height:100vh;max-width:none !important;margin-left:0 !important}@media only screen and (min-width:40.063em){.reveal-modal.full,dialog.full{width:100vw;max-width:93.75rem;left:0;right:0;margin:0 auto}}.reveal-modal .close-reveal-modal,dialog .close-reveal-modal{font-size:2.5rem;line-height:1;position:absolute;top:.625rem;right:1.375rem;color:#aaa;font-weight:bold;cursor:pointer}dialog{display:none}dialog::backdrop,dialog+.backdrop{position:absolute;top:0;bottom:0;left:0;right:0;background:#000;background:rgba(0,0,0,.45);z-index:auto;display:none;left:0}dialog[open]{display:block}@media print{dialog,.reveal-modal{display:none;background:#fff !important}}.side-nav{display:block;margin:0;padding:0 0 0 0;list-style-type:none;list-style-position:outside;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif}.side-nav li{margin:0 0 0 0;font-size:1rem;font-weight:normal}.side-nav li a:not(.button){display:block;color:#334d5c;margin:0;padding:.4375rem .875rem}.side-nav li a:not(.button):hover,.side-nav li a:not(.button):focus{background:rgba(0,0,0,.025);color:#1f2e37}.side-nav li.active>a:first-child:not(.button){color:#1f2e37;font-weight:normal;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif}.side-nav li.divider{border-top:1px solid;height:0;padding:0;list-style:none;border-top-color:#e4e4e4}.side-nav li.heading{color:#334d5c;font-size:1rem;font-weight:bold;text-transform:uppercase}.sub-nav{display:block;width:auto;overflow:hidden;margin:-0.25rem 0 1.125rem;padding-top:.25rem}.sub-nav dt{text-transform:uppercase}.sub-nav dt,.sub-nav dd,.sub-nav li{float:left;display:inline;margin-left:1rem;margin-bottom:0;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:normal;font-size:.875rem;color:#999}.sub-nav dt a,.sub-nav dd a,.sub-nav li a{text-decoration:none;color:#999;padding:.1875rem 1rem}.sub-nav dt a:hover,.sub-nav dd a:hover,.sub-nav li a:hover{color:#737373}.sub-nav dt.active a,.sub-nav dd.active a,.sub-nav li.active a{border-radius:3px;font-weight:normal;background:#334d5c;padding:.1875rem 1rem;cursor:default;color:#fff}.sub-nav dt.active a:hover,.sub-nav dd.active a:hover,.sub-nav li.active a:hover{background:#2c424f}table{background:#fff;margin-bottom:1.25rem;border:solid 1px #ddd;table-layout:auto}table caption{background:rgba(0,0,0,0);color:#222;font-size:1rem;font-weight:bold}table thead{background:#d7d7d7}table thead tr th,table thead tr td{padding:.5rem .625rem .625rem;font-size:.875rem;font-weight:bold;color:#222}table tfoot{background:#d7d7d7}table tfoot tr th,table tfoot tr td{padding:.5rem .625rem .625rem;font-size:.875rem;font-weight:bold;color:#222}table tr th,table tr td{padding:.5625rem .625rem;font-size:.875rem;color:#222;text-align:left}table tr.even,table tr.alt,table tr:nth-of-type(even){background:#e4e4e4}table thead tr th,table tfoot tr th,table tfoot tr td,table tbody tr th,table tbody tr td,table tr td{display:table-cell;line-height:1.125rem}.th{line-height:0;display:inline-block;border:solid 4px #fff;max-width:100%;box-shadow:0 0 0 1px rgba(0,0,0,.2);transition:all 200ms ease-out}.th:hover,.th:focus{box-shadow:0 0 6px 1px rgba(51,77,92,.5)}.th.radius{border-radius:3px}.text-left{text-align:left !important}.text-right{text-align:right !important}.text-center{text-align:center !important}.text-justify{text-align:justify !important}@media only screen and (max-width: 40em){.small-only-text-left{text-align:left !important}.small-only-text-right{text-align:right !important}.small-only-text-center{text-align:center !important}.small-only-text-justify{text-align:justify !important}}@media only screen{.small-text-left{text-align:left !important}.small-text-right{text-align:right !important}.small-text-center{text-align:center !important}.small-text-justify{text-align:justify !important}}@media only screen and (min-width:40.063em)and (max-width:64em){.medium-only-text-left{text-align:left !important}.medium-only-text-right{text-align:right !important}.medium-only-text-center{text-align:center !important}.medium-only-text-justify{text-align:justify !important}}@media only screen and (min-width:40.063em){.medium-text-left{text-align:left !important}.medium-text-right{text-align:right !important}.medium-text-center{text-align:center !important}.medium-text-justify{text-align:justify !important}}@media only screen and (min-width:64.063em)and (max-width:90em){.large-only-text-left{text-align:left !important}.large-only-text-right{text-align:right !important}.large-only-text-center{text-align:center !important}.large-only-text-justify{text-align:justify !important}}@media only screen and (min-width:64.063em){.large-text-left{text-align:left !important}.large-text-right{text-align:right !important}.large-text-center{text-align:center !important}.large-text-justify{text-align:justify !important}}@media only screen and (min-width:90.063em)and (max-width:120em){.xlarge-only-text-left{text-align:left !important}.xlarge-only-text-right{text-align:right !important}.xlarge-only-text-center{text-align:center !important}.xlarge-only-text-justify{text-align:justify !important}}@media only screen and (min-width:90.063em){.xlarge-text-left{text-align:left !important}.xlarge-text-right{text-align:right !important}.xlarge-text-center{text-align:center !important}.xlarge-text-justify{text-align:justify !important}}@media only screen and (min-width:120.063em)and (max-width:99999999em){.xxlarge-only-text-left{text-align:left !important}.xxlarge-only-text-right{text-align:right !important}.xxlarge-only-text-center{text-align:center !important}.xxlarge-only-text-justify{text-align:justify !important}}@media only screen and (min-width:120.063em){.xxlarge-text-left{text-align:left !important}.xxlarge-text-right{text-align:right !important}.xxlarge-text-center{text-align:center !important}.xxlarge-text-justify{text-align:justify !important}}div,dl,dt,dd,ul,ol,li,h1,h2,h3,h4,h5,h6,pre,form,p,blockquote,th,td{margin:0;padding:0}a{color:#334d5c;text-decoration:none;line-height:inherit}a:hover,a:focus{color:#2c424f}a img{border:none}p{font-family:inherit;font-weight:normal;font-size:1rem;line-height:1.6;margin-bottom:1.25rem;text-rendering:optimizeLegibility}p.lead{font-size:1.21875rem;line-height:1.6}p aside{font-size:.875rem;line-height:1.35;font-style:italic}h1,h2,h3,h4,h5,h6{font-family:"Volkhov",Georgia,Times,serif;font-weight:normal;font-style:normal;color:#222;text-rendering:optimizeLegibility;margin-top:.2rem;margin-bottom:.5rem;line-height:1.4}h1 small,h2 small,h3 small,h4 small,h5 small,h6 small{font-size:60%;color:#6f6f6f;line-height:0}h1{font-size:2.125rem}h2{font-size:1.6875rem}h3{font-size:1.375rem}h4{font-size:1.125rem}h5{font-size:1.125rem}h6{font-size:1rem}.subheader{line-height:1.4;color:#6f6f6f;font-weight:normal;margin-top:.2rem;margin-bottom:.5rem}hr{border:solid #cbcbcb;border-width:1px 0 0;clear:both;margin:1.25rem 0 1.1875rem;height:0}em,i{font-style:italic;line-height:inherit}strong,b{font-weight:bold;line-height:inherit}small{font-size:60%;line-height:inherit}code{font-family:"Lucida Console",Monaco,monospace;font-weight:normal;color:#333;background-color:#e3f1c7;border-width:0px;border-style:solid;border-color:#d1e8a4;padding:.125rem .3125rem .0625rem}ul,ol,dl{font-size:1rem;line-height:1.6;margin-bottom:1.25rem;list-style-position:outside;font-family:inherit}ul{margin-left:1.3rem}ul.no-bullet{margin-left:0}ul.no-bullet li ul,ul.no-bullet li ol{margin-left:1.25rem;margin-bottom:0;list-style:none}ul li ul,ul li ol{margin-left:1.25rem;margin-bottom:0}ul.square li ul,ul.circle li ul,ul.disc li ul{list-style:inherit}ul.square{list-style-type:square;margin-left:1.3rem}ul.circle{list-style-type:circle;margin-left:1.3rem}ul.disc{list-style-type:disc;margin-left:1.3rem}ul.no-bullet{list-style:none}ol{margin-left:1.4rem}ol li ul,ol li ol{margin-left:1.25rem;margin-bottom:0}dl dt{margin-bottom:.3rem;font-weight:bold}dl dd{margin-bottom:.75rem}abbr,acronym{text-transform:uppercase;font-size:90%;color:#111;cursor:help}abbr{text-transform:none}abbr[title]{border-bottom:1px dotted #ddd}blockquote{margin:0 0 1.25rem;padding:.5625rem 1.25rem 0 1.1875rem;border-left:1px solid #ddd}blockquote cite{display:block;font-size:.8125rem;color:#555}blockquote cite:before{content:"— "}blockquote cite a,blockquote cite a:visited{color:#555}blockquote,blockquote p{line-height:1.6;color:#6f6f6f}.vcard{display:inline-block;margin:0 0 1.25rem 0;border:1px solid #ddd;padding:.625rem .75rem}.vcard li{margin:0;display:block}.vcard .fn{font-weight:bold;font-size:.9375rem}.vevent .summary{font-weight:bold}.vevent abbr{cursor:default;text-decoration:none;font-weight:bold;border:none;padding:0 .0625rem}@media only screen and (min-width:40.063em){h1,h2,h3,h4,h5,h6{line-height:1.4}h1{font-size:2.75rem}h2{font-size:2.3125rem}h3{font-size:1.6875rem}h4{font-size:1.4375rem}h5{font-size:1.125rem}h6{font-size:1rem}}.print-only{display:none !important}@media print{*{background:rgba(0,0,0,0) !important;color:#000 !important;box-shadow:none !important;text-shadow:none !important}a,a:visited{text-decoration:underline}a[href]:after{content:" (" attr(href) ")"}abbr[title]:after{content:" (" attr(title) ")"}.ir a:after,a[href^="javascript:"]:after,a[href^="#"]:after{content:""}pre,blockquote{border:1px solid #999;page-break-inside:avoid}thead{display:table-header-group}tr,img{page-break-inside:avoid}img{max-width:100% !important}@page{margin:.5cm}p,h2,h3{orphans:3;widows:3}h2,h3{page-break-after:avoid}.hide-on-print{display:none !important}.print-only{display:block !important}.hide-for-print{display:none !important}.show-for-print{display:inherit !important}}@media only screen{.show-for-small-only,.show-for-small-up,.show-for-small,.show-for-small-down,.hide-for-medium-only,.hide-for-medium-up,.hide-for-medium,.show-for-medium-down,.hide-for-large-only,.hide-for-large-up,.hide-for-large,.show-for-large-down,.hide-for-xlarge-only,.hide-for-xlarge-up,.hide-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.hide-for-small-only,.hide-for-small-up,.hide-for-small,.hide-for-small-down,.show-for-medium-only,.show-for-medium-up,.show-for-medium,.hide-for-medium-down,.show-for-large-only,.show-for-large-up,.show-for-large,.hide-for-large-down,.show-for-xlarge-only,.show-for-xlarge-up,.show-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.visible-for-small-only,.visible-for-small-up,.visible-for-small,.visible-for-small-down,.hidden-for-medium-only,.hidden-for-medium-up,.hidden-for-medium,.visible-for-medium-down,.hidden-for-large-only,.hidden-for-large-up,.hidden-for-large,.visible-for-large-down,.hidden-for-xlarge-only,.hidden-for-xlarge-up,.hidden-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.hidden-for-small-only,.hidden-for-small-up,.hidden-for-small,.hidden-for-small-down,.visible-for-medium-only,.visible-for-medium-up,.visible-for-medium,.hidden-for-medium-down,.visible-for-large-only,.visible-for-large-up,.visible-for-large,.hidden-for-large-down,.visible-for-xlarge-only,.visible-for-xlarge-up,.visible-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.show-for-small-only,table.show-for-small-up,table.show-for-small,table.show-for-small-down,table.hide-for-medium-only,table.hide-for-medium-up,table.hide-for-medium,table.show-for-medium-down,table.hide-for-large-only,table.hide-for-large-up,table.hide-for-large,table.show-for-large-down,table.hide-for-xlarge-only,table.hide-for-xlarge-up,table.hide-for-xlarge,table.show-for-xlarge-down,table.hide-for-xxlarge-only,table.hide-for-xxlarge-up,table.hide-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.show-for-small-only,thead.show-for-small-up,thead.show-for-small,thead.show-for-small-down,thead.hide-for-medium-only,thead.hide-for-medium-up,thead.hide-for-medium,thead.show-for-medium-down,thead.hide-for-large-only,thead.hide-for-large-up,thead.hide-for-large,thead.show-for-large-down,thead.hide-for-xlarge-only,thead.hide-for-xlarge-up,thead.hide-for-xlarge,thead.show-for-xlarge-down,thead.hide-for-xxlarge-only,thead.hide-for-xxlarge-up,thead.hide-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.show-for-small-only,tbody.show-for-small-up,tbody.show-for-small,tbody.show-for-small-down,tbody.hide-for-medium-only,tbody.hide-for-medium-up,tbody.hide-for-medium,tbody.show-for-medium-down,tbody.hide-for-large-only,tbody.hide-for-large-up,tbody.hide-for-large,tbody.show-for-large-down,tbody.hide-for-xlarge-only,tbody.hide-for-xlarge-up,tbody.hide-for-xlarge,tbody.show-for-xlarge-down,tbody.hide-for-xxlarge-only,tbody.hide-for-xxlarge-up,tbody.hide-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.show-for-small-only,tr.show-for-small-up,tr.show-for-small,tr.show-for-small-down,tr.hide-for-medium-only,tr.hide-for-medium-up,tr.hide-for-medium,tr.show-for-medium-down,tr.hide-for-large-only,tr.hide-for-large-up,tr.hide-for-large,tr.show-for-large-down,tr.hide-for-xlarge-only,tr.hide-for-xlarge-up,tr.hide-for-xlarge,tr.show-for-xlarge-down,tr.hide-for-xxlarge-only,tr.hide-for-xxlarge-up,tr.hide-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.show-for-small-only,td.show-for-small-only,th.show-for-small-up,td.show-for-small-up,th.show-for-small,td.show-for-small,th.show-for-small-down,td.show-for-small-down,th.hide-for-medium-only,td.hide-for-medium-only,th.hide-for-medium-up,td.hide-for-medium-up,th.hide-for-medium,td.hide-for-medium,th.show-for-medium-down,td.show-for-medium-down,th.hide-for-large-only,td.hide-for-large-only,th.hide-for-large-up,td.hide-for-large-up,th.hide-for-large,td.hide-for-large,th.show-for-large-down,td.show-for-large-down,th.hide-for-xlarge-only,td.hide-for-xlarge-only,th.hide-for-xlarge-up,td.hide-for-xlarge-up,th.hide-for-xlarge,td.hide-for-xlarge,th.show-for-xlarge-down,td.show-for-xlarge-down,th.hide-for-xxlarge-only,td.hide-for-xxlarge-only,th.hide-for-xxlarge-up,td.hide-for-xxlarge-up,th.hide-for-xxlarge,td.hide-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}@media only screen and (min-width:40.063em){.hide-for-small-only,.show-for-small-up,.hide-for-small,.hide-for-small-down,.show-for-medium-only,.show-for-medium-up,.show-for-medium,.show-for-medium-down,.hide-for-large-only,.hide-for-large-up,.hide-for-large,.show-for-large-down,.hide-for-xlarge-only,.hide-for-xlarge-up,.hide-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.show-for-small-only,.hide-for-small-up,.show-for-small,.show-for-small-down,.hide-for-medium-only,.hide-for-medium-up,.hide-for-medium,.hide-for-medium-down,.show-for-large-only,.show-for-large-up,.show-for-large,.hide-for-large-down,.show-for-xlarge-only,.show-for-xlarge-up,.show-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.hidden-for-small-only,.visible-for-small-up,.hidden-for-small,.hidden-for-small-down,.visible-for-medium-only,.visible-for-medium-up,.visible-for-medium,.visible-for-medium-down,.hidden-for-large-only,.hidden-for-large-up,.hidden-for-large,.visible-for-large-down,.hidden-for-xlarge-only,.hidden-for-xlarge-up,.hidden-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.visible-for-small-only,.hidden-for-small-up,.visible-for-small,.visible-for-small-down,.hidden-for-medium-only,.hidden-for-medium-up,.hidden-for-medium,.hidden-for-medium-down,.visible-for-large-only,.visible-for-large-up,.visible-for-large,.hidden-for-large-down,.visible-for-xlarge-only,.visible-for-xlarge-up,.visible-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.hide-for-small-only,table.show-for-small-up,table.hide-for-small,table.hide-for-small-down,table.show-for-medium-only,table.show-for-medium-up,table.show-for-medium,table.show-for-medium-down,table.hide-for-large-only,table.hide-for-large-up,table.hide-for-large,table.show-for-large-down,table.hide-for-xlarge-only,table.hide-for-xlarge-up,table.hide-for-xlarge,table.show-for-xlarge-down,table.hide-for-xxlarge-only,table.hide-for-xxlarge-up,table.hide-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.hide-for-small-only,thead.show-for-small-up,thead.hide-for-small,thead.hide-for-small-down,thead.show-for-medium-only,thead.show-for-medium-up,thead.show-for-medium,thead.show-for-medium-down,thead.hide-for-large-only,thead.hide-for-large-up,thead.hide-for-large,thead.show-for-large-down,thead.hide-for-xlarge-only,thead.hide-for-xlarge-up,thead.hide-for-xlarge,thead.show-for-xlarge-down,thead.hide-for-xxlarge-only,thead.hide-for-xxlarge-up,thead.hide-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.hide-for-small-only,tbody.show-for-small-up,tbody.hide-for-small,tbody.hide-for-small-down,tbody.show-for-medium-only,tbody.show-for-medium-up,tbody.show-for-medium,tbody.show-for-medium-down,tbody.hide-for-large-only,tbody.hide-for-large-up,tbody.hide-for-large,tbody.show-for-large-down,tbody.hide-for-xlarge-only,tbody.hide-for-xlarge-up,tbody.hide-for-xlarge,tbody.show-for-xlarge-down,tbody.hide-for-xxlarge-only,tbody.hide-for-xxlarge-up,tbody.hide-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.hide-for-small-only,tr.show-for-small-up,tr.hide-for-small,tr.hide-for-small-down,tr.show-for-medium-only,tr.show-for-medium-up,tr.show-for-medium,tr.show-for-medium-down,tr.hide-for-large-only,tr.hide-for-large-up,tr.hide-for-large,tr.show-for-large-down,tr.hide-for-xlarge-only,tr.hide-for-xlarge-up,tr.hide-for-xlarge,tr.show-for-xlarge-down,tr.hide-for-xxlarge-only,tr.hide-for-xxlarge-up,tr.hide-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.hide-for-small-only,td.hide-for-small-only,th.show-for-small-up,td.show-for-small-up,th.hide-for-small,td.hide-for-small,th.hide-for-small-down,td.hide-for-small-down,th.show-for-medium-only,td.show-for-medium-only,th.show-for-medium-up,td.show-for-medium-up,th.show-for-medium,td.show-for-medium,th.show-for-medium-down,td.show-for-medium-down,th.hide-for-large-only,td.hide-for-large-only,th.hide-for-large-up,td.hide-for-large-up,th.hide-for-large,td.hide-for-large,th.show-for-large-down,td.show-for-large-down,th.hide-for-xlarge-only,td.hide-for-xlarge-only,th.hide-for-xlarge-up,td.hide-for-xlarge-up,th.hide-for-xlarge,td.hide-for-xlarge,th.show-for-xlarge-down,td.show-for-xlarge-down,th.hide-for-xxlarge-only,td.hide-for-xxlarge-only,th.hide-for-xxlarge-up,td.hide-for-xxlarge-up,th.hide-for-xxlarge,td.hide-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}@media only screen and (min-width:64.063em){.hide-for-small-only,.show-for-small-up,.hide-for-small,.hide-for-small-down,.hide-for-medium-only,.show-for-medium-up,.hide-for-medium,.hide-for-medium-down,.show-for-large-only,.show-for-large-up,.show-for-large,.show-for-large-down,.hide-for-xlarge-only,.hide-for-xlarge-up,.hide-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.show-for-small-only,.hide-for-small-up,.show-for-small,.show-for-small-down,.show-for-medium-only,.hide-for-medium-up,.show-for-medium,.show-for-medium-down,.hide-for-large-only,.hide-for-large-up,.hide-for-large,.hide-for-large-down,.show-for-xlarge-only,.show-for-xlarge-up,.show-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.hidden-for-small-only,.visible-for-small-up,.hidden-for-small,.hidden-for-small-down,.hidden-for-medium-only,.visible-for-medium-up,.hidden-for-medium,.hidden-for-medium-down,.visible-for-large-only,.visible-for-large-up,.visible-for-large,.visible-for-large-down,.hidden-for-xlarge-only,.hidden-for-xlarge-up,.hidden-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.visible-for-small-only,.hidden-for-small-up,.visible-for-small,.visible-for-small-down,.visible-for-medium-only,.hidden-for-medium-up,.visible-for-medium,.visible-for-medium-down,.hidden-for-large-only,.hidden-for-large-up,.hidden-for-large,.hidden-for-large-down,.visible-for-xlarge-only,.visible-for-xlarge-up,.visible-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.hide-for-small-only,table.show-for-small-up,table.hide-for-small,table.hide-for-small-down,table.hide-for-medium-only,table.show-for-medium-up,table.hide-for-medium,table.hide-for-medium-down,table.show-for-large-only,table.show-for-large-up,table.show-for-large,table.show-for-large-down,table.hide-for-xlarge-only,table.hide-for-xlarge-up,table.hide-for-xlarge,table.show-for-xlarge-down,table.hide-for-xxlarge-only,table.hide-for-xxlarge-up,table.hide-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.hide-for-small-only,thead.show-for-small-up,thead.hide-for-small,thead.hide-for-small-down,thead.hide-for-medium-only,thead.show-for-medium-up,thead.hide-for-medium,thead.hide-for-medium-down,thead.show-for-large-only,thead.show-for-large-up,thead.show-for-large,thead.show-for-large-down,thead.hide-for-xlarge-only,thead.hide-for-xlarge-up,thead.hide-for-xlarge,thead.show-for-xlarge-down,thead.hide-for-xxlarge-only,thead.hide-for-xxlarge-up,thead.hide-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.hide-for-small-only,tbody.show-for-small-up,tbody.hide-for-small,tbody.hide-for-small-down,tbody.hide-for-medium-only,tbody.show-for-medium-up,tbody.hide-for-medium,tbody.hide-for-medium-down,tbody.show-for-large-only,tbody.show-for-large-up,tbody.show-for-large,tbody.show-for-large-down,tbody.hide-for-xlarge-only,tbody.hide-for-xlarge-up,tbody.hide-for-xlarge,tbody.show-for-xlarge-down,tbody.hide-for-xxlarge-only,tbody.hide-for-xxlarge-up,tbody.hide-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.hide-for-small-only,tr.show-for-small-up,tr.hide-for-small,tr.hide-for-small-down,tr.hide-for-medium-only,tr.show-for-medium-up,tr.hide-for-medium,tr.hide-for-medium-down,tr.show-for-large-only,tr.show-for-large-up,tr.show-for-large,tr.show-for-large-down,tr.hide-for-xlarge-only,tr.hide-for-xlarge-up,tr.hide-for-xlarge,tr.show-for-xlarge-down,tr.hide-for-xxlarge-only,tr.hide-for-xxlarge-up,tr.hide-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.hide-for-small-only,td.hide-for-small-only,th.show-for-small-up,td.show-for-small-up,th.hide-for-small,td.hide-for-small,th.hide-for-small-down,td.hide-for-small-down,th.hide-for-medium-only,td.hide-for-medium-only,th.show-for-medium-up,td.show-for-medium-up,th.hide-for-medium,td.hide-for-medium,th.hide-for-medium-down,td.hide-for-medium-down,th.show-for-large-only,td.show-for-large-only,th.show-for-large-up,td.show-for-large-up,th.show-for-large,td.show-for-large,th.show-for-large-down,td.show-for-large-down,th.hide-for-xlarge-only,td.hide-for-xlarge-only,th.hide-for-xlarge-up,td.hide-for-xlarge-up,th.hide-for-xlarge,td.hide-for-xlarge,th.show-for-xlarge-down,td.show-for-xlarge-down,th.hide-for-xxlarge-only,td.hide-for-xxlarge-only,th.hide-for-xxlarge-up,td.hide-for-xxlarge-up,th.hide-for-xxlarge,td.hide-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}@media only screen and (min-width:90.063em){.hide-for-small-only,.show-for-small-up,.hide-for-small,.hide-for-small-down,.hide-for-medium-only,.show-for-medium-up,.hide-for-medium,.hide-for-medium-down,.hide-for-large-only,.show-for-large-up,.hide-for-large,.hide-for-large-down,.show-for-xlarge-only,.show-for-xlarge-up,.show-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.show-for-small-only,.hide-for-small-up,.show-for-small,.show-for-small-down,.show-for-medium-only,.hide-for-medium-up,.show-for-medium,.show-for-medium-down,.show-for-large-only,.hide-for-large-up,.show-for-large,.show-for-large-down,.hide-for-xlarge-only,.hide-for-xlarge-up,.hide-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.hidden-for-small-only,.visible-for-small-up,.hidden-for-small,.hidden-for-small-down,.hidden-for-medium-only,.visible-for-medium-up,.hidden-for-medium,.hidden-for-medium-down,.hidden-for-large-only,.visible-for-large-up,.hidden-for-large,.hidden-for-large-down,.visible-for-xlarge-only,.visible-for-xlarge-up,.visible-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.visible-for-small-only,.hidden-for-small-up,.visible-for-small,.visible-for-small-down,.visible-for-medium-only,.hidden-for-medium-up,.visible-for-medium,.visible-for-medium-down,.visible-for-large-only,.hidden-for-large-up,.visible-for-large,.visible-for-large-down,.hidden-for-xlarge-only,.hidden-for-xlarge-up,.hidden-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.hide-for-small-only,table.show-for-small-up,table.hide-for-small,table.hide-for-small-down,table.hide-for-medium-only,table.show-for-medium-up,table.hide-for-medium,table.hide-for-medium-down,table.hide-for-large-only,table.show-for-large-up,table.hide-for-large,table.hide-for-large-down,table.show-for-xlarge-only,table.show-for-xlarge-up,table.show-for-xlarge,table.show-for-xlarge-down,table.hide-for-xxlarge-only,table.hide-for-xxlarge-up,table.hide-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.hide-for-small-only,thead.show-for-small-up,thead.hide-for-small,thead.hide-for-small-down,thead.hide-for-medium-only,thead.show-for-medium-up,thead.hide-for-medium,thead.hide-for-medium-down,thead.hide-for-large-only,thead.show-for-large-up,thead.hide-for-large,thead.hide-for-large-down,thead.show-for-xlarge-only,thead.show-for-xlarge-up,thead.show-for-xlarge,thead.show-for-xlarge-down,thead.hide-for-xxlarge-only,thead.hide-for-xxlarge-up,thead.hide-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.hide-for-small-only,tbody.show-for-small-up,tbody.hide-for-small,tbody.hide-for-small-down,tbody.hide-for-medium-only,tbody.show-for-medium-up,tbody.hide-for-medium,tbody.hide-for-medium-down,tbody.hide-for-large-only,tbody.show-for-large-up,tbody.hide-for-large,tbody.hide-for-large-down,tbody.show-for-xlarge-only,tbody.show-for-xlarge-up,tbody.show-for-xlarge,tbody.show-for-xlarge-down,tbody.hide-for-xxlarge-only,tbody.hide-for-xxlarge-up,tbody.hide-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.hide-for-small-only,tr.show-for-small-up,tr.hide-for-small,tr.hide-for-small-down,tr.hide-for-medium-only,tr.show-for-medium-up,tr.hide-for-medium,tr.hide-for-medium-down,tr.hide-for-large-only,tr.show-for-large-up,tr.hide-for-large,tr.hide-for-large-down,tr.show-for-xlarge-only,tr.show-for-xlarge-up,tr.show-for-xlarge,tr.show-for-xlarge-down,tr.hide-for-xxlarge-only,tr.hide-for-xxlarge-up,tr.hide-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.hide-for-small-only,td.hide-for-small-only,th.show-for-small-up,td.show-for-small-up,th.hide-for-small,td.hide-for-small,th.hide-for-small-down,td.hide-for-small-down,th.hide-for-medium-only,td.hide-for-medium-only,th.show-for-medium-up,td.show-for-medium-up,th.hide-for-medium,td.hide-for-medium,th.hide-for-medium-down,td.hide-for-medium-down,th.hide-for-large-only,td.hide-for-large-only,th.show-for-large-up,td.show-for-large-up,th.hide-for-large,td.hide-for-large,th.hide-for-large-down,td.hide-for-large-down,th.show-for-xlarge-only,td.show-for-xlarge-only,th.show-for-xlarge-up,td.show-for-xlarge-up,th.show-for-xlarge,td.show-for-xlarge,th.show-for-xlarge-down,td.show-for-xlarge-down,th.hide-for-xxlarge-only,td.hide-for-xxlarge-only,th.hide-for-xxlarge-up,td.hide-for-xxlarge-up,th.hide-for-xxlarge,td.hide-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}@media only screen and (min-width:120.063em){.hide-for-small-only,.show-for-small-up,.hide-for-small,.hide-for-small-down,.hide-for-medium-only,.show-for-medium-up,.hide-for-medium,.hide-for-medium-down,.hide-for-large-only,.show-for-large-up,.hide-for-large,.hide-for-large-down,.hide-for-xlarge-only,.show-for-xlarge-up,.hide-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.show-for-small-only,.hide-for-small-up,.show-for-small,.show-for-small-down,.show-for-medium-only,.hide-for-medium-up,.show-for-medium,.show-for-medium-down,.show-for-large-only,.hide-for-large-up,.show-for-large,.show-for-large-down,.show-for-xlarge-only,.hide-for-xlarge-up,.show-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.hidden-for-small-only,.visible-for-small-up,.hidden-for-small,.hidden-for-small-down,.hidden-for-medium-only,.visible-for-medium-up,.hidden-for-medium,.hidden-for-medium-down,.hidden-for-large-only,.visible-for-large-up,.hidden-for-large,.hidden-for-large-down,.hidden-for-xlarge-only,.visible-for-xlarge-up,.hidden-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.visible-for-small-only,.hidden-for-small-up,.visible-for-small,.visible-for-small-down,.visible-for-medium-only,.hidden-for-medium-up,.visible-for-medium,.visible-for-medium-down,.visible-for-large-only,.hidden-for-large-up,.visible-for-large,.visible-for-large-down,.visible-for-xlarge-only,.hidden-for-xlarge-up,.visible-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.hide-for-small-only,table.show-for-small-up,table.hide-for-small,table.hide-for-small-down,table.hide-for-medium-only,table.show-for-medium-up,table.hide-for-medium,table.hide-for-medium-down,table.hide-for-large-only,table.show-for-large-up,table.hide-for-large,table.hide-for-large-down,table.hide-for-xlarge-only,table.show-for-xlarge-up,table.hide-for-xlarge,table.hide-for-xlarge-down,table.show-for-xxlarge-only,table.show-for-xxlarge-up,table.show-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.hide-for-small-only,thead.show-for-small-up,thead.hide-for-small,thead.hide-for-small-down,thead.hide-for-medium-only,thead.show-for-medium-up,thead.hide-for-medium,thead.hide-for-medium-down,thead.hide-for-large-only,thead.show-for-large-up,thead.hide-for-large,thead.hide-for-large-down,thead.hide-for-xlarge-only,thead.show-for-xlarge-up,thead.hide-for-xlarge,thead.hide-for-xlarge-down,thead.show-for-xxlarge-only,thead.show-for-xxlarge-up,thead.show-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.hide-for-small-only,tbody.show-for-small-up,tbody.hide-for-small,tbody.hide-for-small-down,tbody.hide-for-medium-only,tbody.show-for-medium-up,tbody.hide-for-medium,tbody.hide-for-medium-down,tbody.hide-for-large-only,tbody.show-for-large-up,tbody.hide-for-large,tbody.hide-for-large-down,tbody.hide-for-xlarge-only,tbody.show-for-xlarge-up,tbody.hide-for-xlarge,tbody.hide-for-xlarge-down,tbody.show-for-xxlarge-only,tbody.show-for-xxlarge-up,tbody.show-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.hide-for-small-only,tr.show-for-small-up,tr.hide-for-small,tr.hide-for-small-down,tr.hide-for-medium-only,tr.show-for-medium-up,tr.hide-for-medium,tr.hide-for-medium-down,tr.hide-for-large-only,tr.show-for-large-up,tr.hide-for-large,tr.hide-for-large-down,tr.hide-for-xlarge-only,tr.show-for-xlarge-up,tr.hide-for-xlarge,tr.hide-for-xlarge-down,tr.show-for-xxlarge-only,tr.show-for-xxlarge-up,tr.show-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.hide-for-small-only,td.hide-for-small-only,th.show-for-small-up,td.show-for-small-up,th.hide-for-small,td.hide-for-small,th.hide-for-small-down,td.hide-for-small-down,th.hide-for-medium-only,td.hide-for-medium-only,th.show-for-medium-up,td.show-for-medium-up,th.hide-for-medium,td.hide-for-medium,th.hide-for-medium-down,td.hide-for-medium-down,th.hide-for-large-only,td.hide-for-large-only,th.show-for-large-up,td.show-for-large-up,th.hide-for-large,td.hide-for-large,th.hide-for-large-down,td.hide-for-large-down,th.hide-for-xlarge-only,td.hide-for-xlarge-only,th.show-for-xlarge-up,td.show-for-xlarge-up,th.hide-for-xlarge,td.hide-for-xlarge,th.hide-for-xlarge-down,td.hide-for-xlarge-down,th.show-for-xxlarge-only,td.show-for-xxlarge-only,th.show-for-xxlarge-up,td.show-for-xxlarge-up,th.show-for-xxlarge,td.show-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}.show-for-landscape,.hide-for-portrait{display:inherit !important}.hide-for-landscape,.show-for-portrait{display:none !important}table.hide-for-landscape,table.show-for-portrait{display:table !important}thead.hide-for-landscape,thead.show-for-portrait{display:table-header-group !important}tbody.hide-for-landscape,tbody.show-for-portrait{display:table-row-group !important}tr.hide-for-landscape,tr.show-for-portrait{display:table-row !important}td.hide-for-landscape,td.show-for-portrait,th.hide-for-landscape,th.show-for-portrait{display:table-cell !important}@media only screen and (orientation: landscape){.show-for-landscape,.hide-for-portrait{display:inherit !important}.hide-for-landscape,.show-for-portrait{display:none !important}table.show-for-landscape,table.hide-for-portrait{display:table !important}thead.show-for-landscape,thead.hide-for-portrait{display:table-header-group !important}tbody.show-for-landscape,tbody.hide-for-portrait{display:table-row-group !important}tr.show-for-landscape,tr.hide-for-portrait{display:table-row !important}td.show-for-landscape,td.hide-for-portrait,th.show-for-landscape,th.hide-for-portrait{display:table-cell !important}}@media only screen and (orientation: portrait){.show-for-portrait,.hide-for-landscape{display:inherit !important}.hide-for-portrait,.show-for-landscape{display:none !important}table.show-for-portrait,table.hide-for-landscape{display:table !important}thead.show-for-portrait,thead.hide-for-landscape{display:table-header-group !important}tbody.show-for-portrait,tbody.hide-for-landscape{display:table-row-group !important}tr.show-for-portrait,tr.hide-for-landscape{display:table-row !important}td.show-for-portrait,td.hide-for-landscape,th.show-for-portrait,th.hide-for-landscape{display:table-cell !important}}.show-for-touch{display:none !important}.hide-for-touch{display:inherit !important}.touch .show-for-touch{display:inherit !important}.touch .hide-for-touch{display:none !important}table.hide-for-touch{display:table !important}.touch table.show-for-touch{display:table !important}thead.hide-for-touch{display:table-header-group !important}.touch thead.show-for-touch{display:table-header-group !important}tbody.hide-for-touch{display:table-row-group !important}.touch tbody.show-for-touch{display:table-row-group !important}tr.hide-for-touch{display:table-row !important}.touch tr.show-for-touch{display:table-row !important}td.hide-for-touch{display:table-cell !important}.touch td.show-for-touch{display:table-cell !important}th.hide-for-touch{display:table-cell !important}.touch th.show-for-touch{display:table-cell !important}@media print{.show-for-print{display:block}.hide-for-print{display:none}table.show-for-print{display:table !important}thead.show-for-print{display:table-header-group !important}tbody.show-for-print{display:table-row-group !important}tr.show-for-print{display:table-row !important}td.show-for-print{display:table-cell !important}th.show-for-print{display:table-cell !important}}a,a:link{transition:all .4s;color:#0921e2}a:visited{border-bottom:#d7d7d7;color:#071582}a:hover{color:#071ab1}a:focus{color:#596af8}a:active{color:#051380}p{-webkit-hyphens:auto;-moz-hyphens:auto;-ms-hyphens:auto;hyphens:auto;-ms-word-break:normal;word-break:normal}p a,article a{font-weight:bold;border-bottom:1px dotted}p a:hover,article a:hover{border-bottom:2px solid}p a.button,.button,.button:hover{border:0;color:#fff}p.button a{border:0;color:#fff;text-shadow:0 1px 3px rgba(0,0,0,.5)}h1,h2,h3,h4,h5,h6{font-family:"Volkhov",Georgia,Times,serif;font-weight:normal;padding:0}h1{font-size:2.441em;margin-top:0}h2{font-size:1.953em;margin:1.563em 0 0 0}.blog-index h2{margin-top:0}h3{font-size:1.563em;margin:1.152em 0 0 0}h4{font-size:1.25em;margin:1.152em 0 0 0}h5{font-size:1.152em;margin:1em 0 0 0}img{border-radius:3px}img.alignleft,img.left{float:left;margin:5px 15px 5px 0}img.alignright,img.right{float:right;margin:5px 0 5px 15px}img.aligncenter,img.center{display:block;margin:0 auto 10px}figure{margin:0 0 1.875rem 0}#masthead-with-background-color figure,#masthead-with-pattern figure{margin:0}figcaption,.masthead-caption{color:#575757;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-size:.8125rem;padding-top:.125rem}figcaption a,.masthead-caption a{border-bottom:1px dotted #bebebe;color:#575757}figcaption a:hover,.masthead-caption a:hover{border-bottom:2px solid #334d5c;color:#334d5c}.masthead-caption{padding-right:10px;text-align:right}td{vertical-align:top}pre{overflow:auto;margin-bottom:1.25rem;padding:5px;background-color:#e3f1c7;border-radius:3px}pre code{padding:.125rem .3125rem .0625rem 0;border:0}code{font-size:.875rem;line-height:1.5}ul,ol{margin-left:20px;padding:0}li{margin-left:0}.no-bullet{list-style:none;margin-left:0}li>ul,li>ol{margin-bottom:0}dt:first-child{padding-top:0px}dt{font-weight:bold;padding-top:30px}article dl dt{line-height:1.3}article dl dd{line-height:1.6;margin-bottom:.75rem;margin-left:1.5rem}blockquote{font-style:italic;position:relative;border:none;margin:0 30px 30px 30px;color:#4b4b4b}blockquote p{font-style:italic;color:#575757}blockquote:before{display:block;content:"»";font-size:80px;line-height:0;position:absolute;left:-25px;top:auto;color:#4b4b4b}blockquote:after{display:block;content:"«";font-size:80px;line-height:0;position:absolute;right:-10px;bottom:20px;color:#4b4b4b}blockquote cite:before{content:"— "}blockquote cite a,blockquote cite a:visited{color:#575757}cite{padding-top:5px}button,.button{letter-spacing:1px}mark{background-color:#f9c188}.subheadline{font-size:1rem;margin:0;text-transform:uppercase}.teaser{font-size:1.25rem}.big-teaser{font-style:italic;font-weight:300}.big-teaser a{font-style:italic;font-weight:400}@media only screen{.big-teaser{font-size:1.25rem}}@media only screen and (min-width: 40.063em){.big-teaser{font-size:1.8125rem}}.sans{font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif}.serif{font-family:"Volkhov",Georgia,Times,serif}.font-size-h1{font-size:2.441em}.font-size-h2{font-size:1.953em}.font-size-h3{font-size:1.563em}.font-size-h4{font-size:1.25em}.font-size-h5{font-size:1.152em}.font-size-p{font-size:16px}.footnotes:before{content:"";position:absolute;height:1px;width:60px;margin-top:-10px;border-bottom:1px solid #d7d7d7}.footnotes{margin-top:60px}.footnotes ol{font-size:.8em}.footnotes p{font-size:inherit;margin-bottom:0}@font-face{font-family:"iconfont";src:url("../fonts/iconfont.eot");src:url("../fonts/iconfont.eot?#iefix") format("embedded-opentype"),url("../fonts/iconfont.woff") format("woff"),url("../fonts/iconfont.ttf") format("truetype"),url("../fonts/iconfont.svg#svgFontName") format("svg")}.iconfont{font-family:iconfont}.iconfont-48{font-size:48px}[data-icon]:before{content:attr(data-icon)}[data-icon]:before,.icon-archive:before,.icon-browser:before,.icon-calendar:before,.icon-camera:before,.icon-chat:before,.icon-check:before,.icon-chevron-down:before,.icon-chevron-left:before,.icon-chevron-right:before,.icon-chevron-up:before,.icon-circle-with-cross:before,.icon-circle-with-minus:before,.icon-circle-with-plus:before,.icon-cloud:before,.icon-code:before,.icon-cog:before,.icon-dropbox:before,.icon-edit:before,.icon-export:before,.icon-eye:before,.icon-facebook:before,.icon-feather:before,.icon-github:before,.icon-globe:before,.icon-googleplus:before,.icon-heart:before,.icon-heart-outlined:before,.icon-home:before,.icon-instagram:before,.icon-lab-flask:before,.icon-leaf:before,.icon-linkedin:before,.icon-mail:before,.icon-message:before,.icon-mic:before,.icon-network:before,.icon-paper-plane:before,.icon-pinterest:before,.icon-price-tag:before,.icon-rocket:before,.icon-rss:before,.icon-soundcloud:before,.icon-star:before,.icon-star-outlined:before,.icon-thumbs-down:before,.icon-thumbs-up:before,.icon-tree:before,.icon-tumblr:before,.icon-twitter:before,.icon-upload-to-cloud:before,.icon-video:before,.icon-vimeo:before,.icon-warning:before,.icon-xing:before,.icon-youtube:before{display:inline-block;font-family:"iconfont";font-style:normal;font-weight:normal;font-variant:normal;line-height:1;text-decoration:inherit;text-rendering:optimizeLegibility;text-transform:none;-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-smoothing:antialiased}.icon-archive:before{content:""}.icon-browser:before{content:""}.icon-calendar:before{content:""}.icon-camera:before{content:""}.icon-chat:before{content:""}.icon-check:before{content:""}.icon-chevron-down:before{content:""}.icon-chevron-left:before{content:""}.icon-chevron-right:before{content:""}.icon-chevron-up:before{content:""}.icon-circle-with-cross:before{content:""}.icon-circle-with-minus:before{content:""}.icon-circle-with-plus:before{content:""}.icon-cloud:before{content:""}.icon-code:before{content:""}.icon-cog:before{content:""}.icon-dropbox:before{content:""}.icon-edit:before{content:""}.icon-export:before{content:""}.icon-eye:before{content:""}.icon-facebook:before{content:""}.icon-feather:before{content:""}.icon-github:before{content:""}.icon-globe:before{content:""}.icon-googleplus:before{content:""}.icon-heart:before{content:""}.icon-heart-outlined:before{content:""}.icon-home:before{content:""}.icon-instagram:before{content:""}.icon-lab-flask:before{content:""}.icon-leaf:before{content:""}.icon-linkedin:before{content:""}.icon-mail:before{content:""}.icon-message:before{content:""}.icon-mic:before{content:""}.icon-network:before{content:""}.icon-paper-plane:before{content:""}.icon-pinterest:before{content:""}.icon-price-tag:before{content:""}.icon-rocket:before{content:""}.icon-rss:before{content:""}.icon-soundcloud:before{content:""}.icon-star:before{content:""}.icon-star-outlined:before{content:""}.icon-thumbs-down:before{content:""}.icon-thumbs-up:before{content:""}.icon-tree:before{content:""}.icon-tumblr:before{content:""}.icon-twitter:before{content:""}.icon-upload-to-cloud:before{content:""}.icon-video:before{content:""}.icon-vimeo:before{content:""}.icon-warning:before{content:""}.icon-xing:before{content:""}.icon-youtube:before{content:""}body.video,body.video #masthead-no-image-header{background:#000}body.video #masthead-no-image-header{margin-bottom:60px}body.video h1,body.video h2,body.video h3,body.video h4,body.video h5,body.video h6,body.video p,body.video a,body.video blockquote:before,body.video blockquote:after,body.video cite a{color:#fff}body.video cite a:visited{color:#fff}body.video cite{color:#fff}#navigation{-webkit-box-shadow:0 2px 2px 0 rgba(0,0,0,.2);box-shadow:0 2px 3px 0 rgba(0,0,0,.2)}#navigation [class^=icon-]:before,#navigation [class*=" icon-"]:before{margin-right:.5rem}.no-js form#search{display:none}#masthead{background-color:#334d5c}#masthead-no-image-header{background-color:#334d5c}#masthead-with-text{text-align:center;font-size:3.375rem;font-family:"Volkhov",Georgia,Times,serif;color:#fff;text-transform:uppercase;text-shadow:0 2px 3px rgba(0,0,0,.4)}#masthead-no-image-header{height:100px;background-color:#3faf46}#masthead-no-image-header #logo img{margin-top:10px}@media only screen and (max-width: 40em){#logo img{margin-top:30px}#masthead{height:100px}#masthead-with-pattern{padding:15px 0}#masthead-with-background-color{padding:15px 0}#masthead-with-text{height:220px;padding:30px 0;font-size:2.25rem}#masthead-no-image-header #logo img{margin-top:35px}}@media only screen and (min-width:40.063em)and (max-width:64em){#logo img{margin-top:60px}#masthead{height:200px}#masthead-with-pattern{padding:20px 0}#masthead-with-background-color{padding:20px 0}#masthead-with-text{padding:60px 0;height:300px}#masthead-no-image-header #logo img{margin-top:20px}}@media only screen and (min-width:64.063em)and (max-width:90em){#logo img{margin-top:60px}#masthead{height:200px}#masthead-with-pattern{padding:30px 0}#masthead-with-background-color{padding:30px 0}#masthead-with-text{height:330px;padding:60px 0}}@media only screen and (min-width:90.063em){#logo img{margin-top:60px}#masthead{height:200px}#masthead-with-pattern{padding:45px 0}#masthead-with-background-color{padding:45px 0}#masthead-with-text{padding:95px 0;height:400px}}#title-image-small{height:240px}#title-image-large{height:520px}#title-image-index-small{height:120px}#title-image-index-large{height:260px}#breadcrumb{background:#f3f3f3;border-top:1px solid #f0f0f0;border-bottom:1px solid #f0f0f0}.breadcrumbs>.current{font-weight:bold}#page-meta,#page-meta a{color:#a4a4a4}#page-meta .button{background:#a4a4a4;border:0}#page-meta .button{color:#fff}#page-meta .button:hover{background:#334d5c}.meta-info p{font-size:.8125rem;color:#efefef}.meta-info a{text-decoration:underline;color:#efefef}.meta-info a:hover{text-decoration:none;color:#a1d044}#up-to-top{padding:30px 0 10px 0}#up-to-top a{font-size:24px;padding:5px;border-radius:3px}#up-to-top a:hover{background:#d7d7d7}#footer-content p,#footer-content li{font-size:.8125rem;font-weight:300}#footer{padding-top:30px;padding-bottom:20px;background:#7e7e7e;color:#fff}#footer a{color:#a1d044}#footer h4,#footer h5{letter-spacing:1px;color:#fff;text-transform:uppercase}#subfooter{background:#313131;color:#7e7e7e;padding-top:30px}#subfooter-left ul.inline-list{float:left}.credits a{color:#7e7e7e;border:0;text-transform:uppercase}.credits a:hover{color:#fff}.social-icons{margin-bottom:10px !important}.social-icons li{padding:0 0 20px 0}.social-icons a{font-size:1.4375rem;display:block;width:36px;border-radius:50%;color:#313131;background:#7e7e7e;text-align:center}.social-icons a:hover{background:#313131;color:#fff}.t10{margin-top:10px !important}.t15{margin-top:15px !important}.t20{margin-top:20px !important}.t30{margin-top:30px !important}.t50{margin-top:50px !important}.t60{margin-top:60px !important}.t70{margin-top:70px !important}.t80{margin-top:80px !important}.t90{margin-top:90px !important}.b15{margin-bottom:15px !important}.b20{margin-bottom:20px !important}.b30{margin-bottom:30px !important}.b60{margin-bottom:60px !important}.l15{margin-left:15px !important}.r15{margin-right:15px !important}.pl20{padding-left:20px !important}.pr5{padding-right:5px !important}.pr10{padding-right:10px !important}.pr20{padding-right:20px !important}#toc ul,#toc ul ul,#toc ul ul ul{list-style:none;margin-left:30px}#toc ul{margin-left:0;margin-top:30px}.border-dotted{border:1px dotted #a4a4a4;padding:1.25rem;border-radius:3px}.shadow-no{text-shadow:rgba(0,0,0,0) 0 0 0}.shadow-black{text-shadow:rgba(0,0,0,.498039) 0px 1px 2px}.shadow-white{text-shadow:rgba(255,255,255,.498039) 0px 1px 2px}.alert-box{font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;text-shadow:0px 1px 1px rgba(0,0,0,.9)}.alert-box p{margin-bottom:0}.alert-box a{text-shadow:1px 1px 0px #000;color:#fff;border-bottom:1px dotted #fff}.alert-box a:hover{border-bottom:1px solid #fff}.alert-box.terminal{background:#3e3e3e;color:#fff;border-color:#353535;font-family:"Lucida Console",Monaco,monospace}.alert-box.terminal::before{content:"$ ";color:#a1d044;float:left;margin:.25em .5em 0 0}.alert-box.text{background-color:#d7d7d7;text-shadow:0px 0px 0px rgba(0,0,0,.9);border-color:#b9b9b9;color:#3e3e3e}button,.button{letter-spacing:1px}button.grey,.button.grey{background:#575757}button.grey:hover,button.grey:focus,.button.grey:hover,.button.grey:focus{background-color:#0b0b0b}.side-nav li.title{text-transform:uppercase}.side-nav li{border-top:1px solid #cbcbcb}.side-nav li a:not(.button){border-bottom:0;padding:.4375rem 0rem}.side-nav li a:not(.button):hover,.side-nav li a:not(.button):focus{background:#e4e4e4}.homepage p{margin:0;padding:0;color:#575757}dl.accordion{border-top:1px solid #d7d7d7}.accordion dd{border-bottom:1px solid #d7d7d7}dd.accordion-navigation span{padding-right:12px}dd.accordion-navigation span:before{content:""}dd.accordion-navigation.active span:before{content:""}dd.accordion-navigation.active span:before{content:""}/*! Lazy Load XT v1.0.6 2014-11-19
+.font-size-h1{font-size:2.441em}.font-size-h2{font-size:1.953em}.font-size-h3{font-size:1.563em}.font-size-h4{font-size:1.25em}.font-size-h5{font-size:1.152em}meta.foundation-version{font-family:"/5.5.0/"}meta.foundation-mq-small{font-family:"/only screen/";width:0em}meta.foundation-mq-small-only{font-family:"/only screen and (max-width: 40em)/";width:0em}meta.foundation-mq-medium{font-family:"/only screen and (min-width:40.063em)/";width:40.063em}meta.foundation-mq-medium-only{font-family:"/only screen and (min-width:40.063em) and (max-width:64em)/";width:40.063em}meta.foundation-mq-large{font-family:"/only screen and (min-width:64.063em)/";width:64.063em}meta.foundation-mq-large-only{font-family:"/only screen and (min-width:64.063em) and (max-width:90em)/";width:64.063em}meta.foundation-mq-xlarge{font-family:"/only screen and (min-width:90.063em)/";width:90.063em}meta.foundation-mq-xlarge-only{font-family:"/only screen and (min-width:90.063em) and (max-width:120em)/";width:90.063em}meta.foundation-mq-xxlarge{font-family:"/only screen and (min-width:120.063em)/";width:120.063em}meta.foundation-data-attribute-namespace{font-family:false}html,body{height:100%}*,*:before,*:after{-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box}html,body{font-size:16px}body{background:#fdfdfd;color:#111;padding:0;margin:0;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:normal;font-style:normal;line-height:1.5;position:relative;cursor:auto}a:hover{cursor:pointer}img{max-width:100%;height:auto}img{-ms-interpolation-mode:bicubic}#map_canvas img,#map_canvas embed,#map_canvas object,.map_canvas img,.map_canvas embed,.map_canvas object{max-width:none !important}.left{float:left !important}.right{float:right !important}.clearfix:before,.clearfix:after{content:" ";display:table}.clearfix:after{clear:both}.hide{display:none !important;visibility:hidden}.invisible{visibility:hidden}.antialiased{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}img{display:inline-block;vertical-align:middle}textarea{height:auto;min-height:50px}select{width:100%}/*! normalize.css v3.0.2 | MIT License | git.io/normalize */html{font-family:sans-serif;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%}body{margin:0}article,aside,details,figcaption,figure,footer,header,hgroup,main,menu,nav,section,summary{display:block}audio,canvas,progress,video{display:inline-block;vertical-align:baseline}audio:not([controls]){display:none;height:0}[hidden],template{display:none}a{background-color:rgba(0,0,0,0)}a:active,a:hover{outline:0}abbr[title]{border-bottom:1px dotted}b,strong{font-weight:bold}dfn{font-style:italic}h1{font-size:2em;margin:.67em 0}mark{background:#ff0;color:#000}small{font-size:80%}sub,sup{font-size:75%;line-height:0;position:relative;vertical-align:baseline}sup{top:-0.5em}sub{bottom:-0.25em}img{border:0}svg:not(:root){overflow:hidden}figure{margin:1em 40px}hr{-moz-box-sizing:content-box;box-sizing:content-box;height:0}pre{overflow:auto}code,kbd,pre,samp{font-family:monospace,monospace;font-size:1em}button,input,optgroup,select,textarea{color:inherit;font:inherit;margin:0}button{overflow:visible}button,select{text-transform:none}button,html input[type=button],input[type=reset],input[type=submit]{-webkit-appearance:button;cursor:pointer}button[disabled],html input[disabled]{cursor:default}button::-moz-focus-inner,input::-moz-focus-inner{border:0;padding:0}input{line-height:normal}input[type=checkbox],input[type=radio]{box-sizing:border-box;padding:0}input[type=number]::-webkit-inner-spin-button,input[type=number]::-webkit-outer-spin-button{height:auto}input[type=search]{-webkit-appearance:textfield;-moz-box-sizing:content-box;-webkit-box-sizing:content-box;box-sizing:content-box}input[type=search]::-webkit-search-cancel-button,input[type=search]::-webkit-search-decoration{-webkit-appearance:none}fieldset{border:1px solid silver;margin:0 2px;padding:.35em .625em .75em}legend{border:0;padding:0}textarea{overflow:auto}optgroup{font-weight:bold}table{border-collapse:collapse;border-spacing:0}td,th{padding:0}.row{width:100%;margin-left:auto;margin-right:auto;margin-top:0;margin-bottom:0;max-width:93.75rem}.row:before,.row:after{content:" ";display:table}.row:after{clear:both}.row.collapse>.column,.row.collapse>.columns{padding-left:0;padding-right:0}.row.collapse .row{margin-left:0;margin-right:0}.row .row{width:auto;margin-left:-0.9375rem;margin-right:-0.9375rem;margin-top:0;margin-bottom:0;max-width:none}.row .row:before,.row .row:after{content:" ";display:table}.row .row:after{clear:both}.row .row.collapse{width:auto;margin:0;max-width:none}.row .row.collapse:before,.row .row.collapse:after{content:" ";display:table}.row .row.collapse:after{clear:both}.column,.columns{padding-left:.9375rem;padding-right:.9375rem;width:100%;float:left}[class*=column]+[class*=column]:last-child{float:right}[class*=column]+[class*=column].end{float:left}@media only screen{.small-push-0{position:relative;left:0%;right:auto}.small-pull-0{position:relative;right:0%;left:auto}.small-push-1{position:relative;left:8.3333333333%;right:auto}.small-pull-1{position:relative;right:8.3333333333%;left:auto}.small-push-2{position:relative;left:16.6666666667%;right:auto}.small-pull-2{position:relative;right:16.6666666667%;left:auto}.small-push-3{position:relative;left:25%;right:auto}.small-pull-3{position:relative;right:25%;left:auto}.small-push-4{position:relative;left:33.3333333333%;right:auto}.small-pull-4{position:relative;right:33.3333333333%;left:auto}.small-push-5{position:relative;left:41.6666666667%;right:auto}.small-pull-5{position:relative;right:41.6666666667%;left:auto}.small-push-6{position:relative;left:50%;right:auto}.small-pull-6{position:relative;right:50%;left:auto}.small-push-7{position:relative;left:58.3333333333%;right:auto}.small-pull-7{position:relative;right:58.3333333333%;left:auto}.small-push-8{position:relative;left:66.6666666667%;right:auto}.small-pull-8{position:relative;right:66.6666666667%;left:auto}.small-push-9{position:relative;left:75%;right:auto}.small-pull-9{position:relative;right:75%;left:auto}.small-push-10{position:relative;left:83.3333333333%;right:auto}.small-pull-10{position:relative;right:83.3333333333%;left:auto}.small-push-11{position:relative;left:91.6666666667%;right:auto}.small-pull-11{position:relative;right:91.6666666667%;left:auto}.column,.columns{position:relative;padding-left:.9375rem;padding-right:.9375rem;float:left}.small-1{width:8.3333333333%}.small-2{width:16.6666666667%}.small-3{width:25%}.small-4{width:33.3333333333%}.small-5{width:41.6666666667%}.small-6{width:50%}.small-7{width:58.3333333333%}.small-8{width:66.6666666667%}.small-9{width:75%}.small-10{width:83.3333333333%}.small-11{width:91.6666666667%}.small-12{width:100%}.small-offset-0{margin-left:0% !important}.small-offset-1{margin-left:8.3333333333% !important}.small-offset-2{margin-left:16.6666666667% !important}.small-offset-3{margin-left:25% !important}.small-offset-4{margin-left:33.3333333333% !important}.small-offset-5{margin-left:41.6666666667% !important}.small-offset-6{margin-left:50% !important}.small-offset-7{margin-left:58.3333333333% !important}.small-offset-8{margin-left:66.6666666667% !important}.small-offset-9{margin-left:75% !important}.small-offset-10{margin-left:83.3333333333% !important}.small-offset-11{margin-left:91.6666666667% !important}.small-reset-order{margin-left:0;margin-right:0;left:auto;right:auto;float:left}.column.small-centered,.columns.small-centered{margin-left:auto;margin-right:auto;float:none}.column.small-uncentered,.columns.small-uncentered{margin-left:0;margin-right:0;float:left}.column.small-centered:last-child,.columns.small-centered:last-child{float:none}.column.small-uncentered:last-child,.columns.small-uncentered:last-child{float:left}.column.small-uncentered.opposite,.columns.small-uncentered.opposite{float:right}.row.small-collapse>.column,.row.small-collapse>.columns{padding-left:0;padding-right:0}.row.small-collapse .row{margin-left:0;margin-right:0}.row.small-uncollapse>.column,.row.small-uncollapse>.columns{padding-left:.9375rem;padding-right:.9375rem;float:left}}@media only screen and (min-width:40.063em){.medium-push-0{position:relative;left:0%;right:auto}.medium-pull-0{position:relative;right:0%;left:auto}.medium-push-1{position:relative;left:8.3333333333%;right:auto}.medium-pull-1{position:relative;right:8.3333333333%;left:auto}.medium-push-2{position:relative;left:16.6666666667%;right:auto}.medium-pull-2{position:relative;right:16.6666666667%;left:auto}.medium-push-3{position:relative;left:25%;right:auto}.medium-pull-3{position:relative;right:25%;left:auto}.medium-push-4{position:relative;left:33.3333333333%;right:auto}.medium-pull-4{position:relative;right:33.3333333333%;left:auto}.medium-push-5{position:relative;left:41.6666666667%;right:auto}.medium-pull-5{position:relative;right:41.6666666667%;left:auto}.medium-push-6{position:relative;left:50%;right:auto}.medium-pull-6{position:relative;right:50%;left:auto}.medium-push-7{position:relative;left:58.3333333333%;right:auto}.medium-pull-7{position:relative;right:58.3333333333%;left:auto}.medium-push-8{position:relative;left:66.6666666667%;right:auto}.medium-pull-8{position:relative;right:66.6666666667%;left:auto}.medium-push-9{position:relative;left:75%;right:auto}.medium-pull-9{position:relative;right:75%;left:auto}.medium-push-10{position:relative;left:83.3333333333%;right:auto}.medium-pull-10{position:relative;right:83.3333333333%;left:auto}.medium-push-11{position:relative;left:91.6666666667%;right:auto}.medium-pull-11{position:relative;right:91.6666666667%;left:auto}.column,.columns{position:relative;padding-left:.9375rem;padding-right:.9375rem;float:left}.medium-1{width:8.3333333333%}.medium-2{width:16.6666666667%}.medium-3{width:25%}.medium-4{width:33.3333333333%}.medium-5{width:41.6666666667%}.medium-6{width:50%}.medium-7{width:58.3333333333%}.medium-8{width:66.6666666667%}.medium-9{width:75%}.medium-10{width:83.3333333333%}.medium-11{width:91.6666666667%}.medium-12{width:100%}.medium-offset-0{margin-left:0% !important}.medium-offset-1{margin-left:8.3333333333% !important}.medium-offset-2{margin-left:16.6666666667% !important}.medium-offset-3{margin-left:25% !important}.medium-offset-4{margin-left:33.3333333333% !important}.medium-offset-5{margin-left:41.6666666667% !important}.medium-offset-6{margin-left:50% !important}.medium-offset-7{margin-left:58.3333333333% !important}.medium-offset-8{margin-left:66.6666666667% !important}.medium-offset-9{margin-left:75% !important}.medium-offset-10{margin-left:83.3333333333% !important}.medium-offset-11{margin-left:91.6666666667% !important}.medium-reset-order{margin-left:0;margin-right:0;left:auto;right:auto;float:left}.column.medium-centered,.columns.medium-centered{margin-left:auto;margin-right:auto;float:none}.column.medium-uncentered,.columns.medium-uncentered{margin-left:0;margin-right:0;float:left}.column.medium-centered:last-child,.columns.medium-centered:last-child{float:none}.column.medium-uncentered:last-child,.columns.medium-uncentered:last-child{float:left}.column.medium-uncentered.opposite,.columns.medium-uncentered.opposite{float:right}.row.medium-collapse>.column,.row.medium-collapse>.columns{padding-left:0;padding-right:0}.row.medium-collapse .row{margin-left:0;margin-right:0}.row.medium-uncollapse>.column,.row.medium-uncollapse>.columns{padding-left:.9375rem;padding-right:.9375rem;float:left}.push-0{position:relative;left:0%;right:auto}.pull-0{position:relative;right:0%;left:auto}.push-1{position:relative;left:8.3333333333%;right:auto}.pull-1{position:relative;right:8.3333333333%;left:auto}.push-2{position:relative;left:16.6666666667%;right:auto}.pull-2{position:relative;right:16.6666666667%;left:auto}.push-3{position:relative;left:25%;right:auto}.pull-3{position:relative;right:25%;left:auto}.push-4{position:relative;left:33.3333333333%;right:auto}.pull-4{position:relative;right:33.3333333333%;left:auto}.push-5{position:relative;left:41.6666666667%;right:auto}.pull-5{position:relative;right:41.6666666667%;left:auto}.push-6{position:relative;left:50%;right:auto}.pull-6{position:relative;right:50%;left:auto}.push-7{position:relative;left:58.3333333333%;right:auto}.pull-7{position:relative;right:58.3333333333%;left:auto}.push-8{position:relative;left:66.6666666667%;right:auto}.pull-8{position:relative;right:66.6666666667%;left:auto}.push-9{position:relative;left:75%;right:auto}.pull-9{position:relative;right:75%;left:auto}.push-10{position:relative;left:83.3333333333%;right:auto}.pull-10{position:relative;right:83.3333333333%;left:auto}.push-11{position:relative;left:91.6666666667%;right:auto}.pull-11{position:relative;right:91.6666666667%;left:auto}}@media only screen and (min-width:64.063em){.large-push-0{position:relative;left:0%;right:auto}.large-pull-0{position:relative;right:0%;left:auto}.large-push-1{position:relative;left:8.3333333333%;right:auto}.large-pull-1{position:relative;right:8.3333333333%;left:auto}.large-push-2{position:relative;left:16.6666666667%;right:auto}.large-pull-2{position:relative;right:16.6666666667%;left:auto}.large-push-3{position:relative;left:25%;right:auto}.large-pull-3{position:relative;right:25%;left:auto}.large-push-4{position:relative;left:33.3333333333%;right:auto}.large-pull-4{position:relative;right:33.3333333333%;left:auto}.large-push-5{position:relative;left:41.6666666667%;right:auto}.large-pull-5{position:relative;right:41.6666666667%;left:auto}.large-push-6{position:relative;left:50%;right:auto}.large-pull-6{position:relative;right:50%;left:auto}.large-push-7{position:relative;left:58.3333333333%;right:auto}.large-pull-7{position:relative;right:58.3333333333%;left:auto}.large-push-8{position:relative;left:66.6666666667%;right:auto}.large-pull-8{position:relative;right:66.6666666667%;left:auto}.large-push-9{position:relative;left:75%;right:auto}.large-pull-9{position:relative;right:75%;left:auto}.large-push-10{position:relative;left:83.3333333333%;right:auto}.large-pull-10{position:relative;right:83.3333333333%;left:auto}.large-push-11{position:relative;left:91.6666666667%;right:auto}.large-pull-11{position:relative;right:91.6666666667%;left:auto}.column,.columns{position:relative;padding-left:.9375rem;padding-right:.9375rem;float:left}.large-1{width:8.3333333333%}.large-2{width:16.6666666667%}.large-3{width:25%}.large-4{width:33.3333333333%}.large-5{width:41.6666666667%}.large-6{width:50%}.large-7{width:58.3333333333%}.large-8{width:66.6666666667%}.large-9{width:75%}.large-10{width:83.3333333333%}.large-11{width:91.6666666667%}.large-12{width:100%}.large-offset-0{margin-left:0% !important}.large-offset-1{margin-left:8.3333333333% !important}.large-offset-2{margin-left:16.6666666667% !important}.large-offset-3{margin-left:25% !important}.large-offset-4{margin-left:33.3333333333% !important}.large-offset-5{margin-left:41.6666666667% !important}.large-offset-6{margin-left:50% !important}.large-offset-7{margin-left:58.3333333333% !important}.large-offset-8{margin-left:66.6666666667% !important}.large-offset-9{margin-left:75% !important}.large-offset-10{margin-left:83.3333333333% !important}.large-offset-11{margin-left:91.6666666667% !important}.large-reset-order{margin-left:0;margin-right:0;left:auto;right:auto;float:left}.column.large-centered,.columns.large-centered{margin-left:auto;margin-right:auto;float:none}.column.large-uncentered,.columns.large-uncentered{margin-left:0;margin-right:0;float:left}.column.large-centered:last-child,.columns.large-centered:last-child{float:none}.column.large-uncentered:last-child,.columns.large-uncentered:last-child{float:left}.column.large-uncentered.opposite,.columns.large-uncentered.opposite{float:right}.row.large-collapse>.column,.row.large-collapse>.columns{padding-left:0;padding-right:0}.row.large-collapse .row{margin-left:0;margin-right:0}.row.large-uncollapse>.column,.row.large-uncollapse>.columns{padding-left:.9375rem;padding-right:.9375rem;float:left}.push-0{position:relative;left:0%;right:auto}.pull-0{position:relative;right:0%;left:auto}.push-1{position:relative;left:8.3333333333%;right:auto}.pull-1{position:relative;right:8.3333333333%;left:auto}.push-2{position:relative;left:16.6666666667%;right:auto}.pull-2{position:relative;right:16.6666666667%;left:auto}.push-3{position:relative;left:25%;right:auto}.pull-3{position:relative;right:25%;left:auto}.push-4{position:relative;left:33.3333333333%;right:auto}.pull-4{position:relative;right:33.3333333333%;left:auto}.push-5{position:relative;left:41.6666666667%;right:auto}.pull-5{position:relative;right:41.6666666667%;left:auto}.push-6{position:relative;left:50%;right:auto}.pull-6{position:relative;right:50%;left:auto}.push-7{position:relative;left:58.3333333333%;right:auto}.pull-7{position:relative;right:58.3333333333%;left:auto}.push-8{position:relative;left:66.6666666667%;right:auto}.pull-8{position:relative;right:66.6666666667%;left:auto}.push-9{position:relative;left:75%;right:auto}.pull-9{position:relative;right:75%;left:auto}.push-10{position:relative;left:83.3333333333%;right:auto}.pull-10{position:relative;right:83.3333333333%;left:auto}.push-11{position:relative;left:91.6666666667%;right:auto}.pull-11{position:relative;right:91.6666666667%;left:auto}}button,.button{border-style:solid;border-width:0;cursor:pointer;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:normal;line-height:normal;margin:0 0 1.25rem;position:relative;text-decoration:none;text-align:center;-webkit-appearance:none;border-radius:0;display:inline-block;padding-top:1rem;padding-right:2rem;padding-bottom:1.0625rem;padding-left:2rem;font-size:1rem;background-color:#334d5c;border-color:#293e4a;color:#fff;transition:background-color 300ms ease-out}button:hover,button:focus,.button:hover,.button:focus{background-color:#293e4a}button:hover,button:focus,.button:hover,.button:focus{color:#fff}button.secondary,.button.secondary{background-color:#a1d044;border-color:#84b02c;color:#fff}button.secondary:hover,button.secondary:focus,.button.secondary:hover,.button.secondary:focus{background-color:#84b02c}button.secondary:hover,button.secondary:focus,.button.secondary:hover,.button.secondary:focus{color:#fff}button.success,.button.success{background-color:#a1d044;border-color:#84b02c;color:#fff}button.success:hover,button.success:focus,.button.success:hover,.button.success:focus{background-color:#84b02c}button.success:hover,button.success:focus,.button.success:hover,.button.success:focus{color:#fff}button.alert,.button.alert{background-color:#df4949;border-color:#c92323;color:#fff}button.alert:hover,button.alert:focus,.button.alert:hover,.button.alert:focus{background-color:#c92323}button.alert:hover,button.alert:focus,.button.alert:hover,.button.alert:focus{color:#fff}button.warning,.button.warning{background-color:#be6409;border-color:#985007;color:#fff}button.warning:hover,button.warning:focus,.button.warning:hover,.button.warning:focus{background-color:#985007}button.warning:hover,button.warning:focus,.button.warning:hover,.button.warning:focus{color:#fff}button.info,.button.info{background-color:#334d5c;border-color:#293e4a;color:#fff}button.info:hover,button.info:focus,.button.info:hover,.button.info:focus{background-color:#293e4a}button.info:hover,button.info:focus,.button.info:hover,.button.info:focus{color:#fff}button.large,.button.large{padding-top:1.125rem;padding-right:2.25rem;padding-bottom:1.1875rem;padding-left:2.25rem;font-size:1.25rem}button.small,.button.small{padding-top:.875rem;padding-right:1.75rem;padding-bottom:.9375rem;padding-left:1.75rem;font-size:.8125rem}button.tiny,.button.tiny{padding-top:.625rem;padding-right:1.25rem;padding-bottom:.6875rem;padding-left:1.25rem;font-size:.6875rem}button.expand,.button.expand{padding-right:0;padding-left:0;width:100%}button.left-align,.button.left-align{text-align:left;text-indent:.75rem}button.right-align,.button.right-align{text-align:right;padding-right:.75rem}button.radius,.button.radius{border-radius:3px}button.round,.button.round{border-radius:1000px}button.disabled,button[disabled],.button.disabled,.button[disabled]{background-color:#334d5c;border-color:#293e4a;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled:hover,button.disabled:focus,button[disabled]:hover,button[disabled]:focus,.button.disabled:hover,.button.disabled:focus,.button[disabled]:hover,.button[disabled]:focus{background-color:#293e4a}button.disabled:hover,button.disabled:focus,button[disabled]:hover,button[disabled]:focus,.button.disabled:hover,.button.disabled:focus,.button[disabled]:hover,.button[disabled]:focus{color:#fff}button.disabled:hover,button.disabled:focus,button[disabled]:hover,button[disabled]:focus,.button.disabled:hover,.button.disabled:focus,.button[disabled]:hover,.button[disabled]:focus{background-color:#334d5c}button.disabled.secondary,button[disabled].secondary,.button.disabled.secondary,.button[disabled].secondary{background-color:#a1d044;border-color:#84b02c;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.secondary:hover,button.disabled.secondary:focus,button[disabled].secondary:hover,button[disabled].secondary:focus,.button.disabled.secondary:hover,.button.disabled.secondary:focus,.button[disabled].secondary:hover,.button[disabled].secondary:focus{background-color:#84b02c}button.disabled.secondary:hover,button.disabled.secondary:focus,button[disabled].secondary:hover,button[disabled].secondary:focus,.button.disabled.secondary:hover,.button.disabled.secondary:focus,.button[disabled].secondary:hover,.button[disabled].secondary:focus{color:#fff}button.disabled.secondary:hover,button.disabled.secondary:focus,button[disabled].secondary:hover,button[disabled].secondary:focus,.button.disabled.secondary:hover,.button.disabled.secondary:focus,.button[disabled].secondary:hover,.button[disabled].secondary:focus{background-color:#a1d044}button.disabled.success,button[disabled].success,.button.disabled.success,.button[disabled].success{background-color:#a1d044;border-color:#84b02c;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.success:hover,button.disabled.success:focus,button[disabled].success:hover,button[disabled].success:focus,.button.disabled.success:hover,.button.disabled.success:focus,.button[disabled].success:hover,.button[disabled].success:focus{background-color:#84b02c}button.disabled.success:hover,button.disabled.success:focus,button[disabled].success:hover,button[disabled].success:focus,.button.disabled.success:hover,.button.disabled.success:focus,.button[disabled].success:hover,.button[disabled].success:focus{color:#fff}button.disabled.success:hover,button.disabled.success:focus,button[disabled].success:hover,button[disabled].success:focus,.button.disabled.success:hover,.button.disabled.success:focus,.button[disabled].success:hover,.button[disabled].success:focus{background-color:#a1d044}button.disabled.alert,button[disabled].alert,.button.disabled.alert,.button[disabled].alert{background-color:#df4949;border-color:#c92323;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.alert:hover,button.disabled.alert:focus,button[disabled].alert:hover,button[disabled].alert:focus,.button.disabled.alert:hover,.button.disabled.alert:focus,.button[disabled].alert:hover,.button[disabled].alert:focus{background-color:#c92323}button.disabled.alert:hover,button.disabled.alert:focus,button[disabled].alert:hover,button[disabled].alert:focus,.button.disabled.alert:hover,.button.disabled.alert:focus,.button[disabled].alert:hover,.button[disabled].alert:focus{color:#fff}button.disabled.alert:hover,button.disabled.alert:focus,button[disabled].alert:hover,button[disabled].alert:focus,.button.disabled.alert:hover,.button.disabled.alert:focus,.button[disabled].alert:hover,.button[disabled].alert:focus{background-color:#df4949}button.disabled.warning,button[disabled].warning,.button.disabled.warning,.button[disabled].warning{background-color:#be6409;border-color:#985007;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.warning:hover,button.disabled.warning:focus,button[disabled].warning:hover,button[disabled].warning:focus,.button.disabled.warning:hover,.button.disabled.warning:focus,.button[disabled].warning:hover,.button[disabled].warning:focus{background-color:#985007}button.disabled.warning:hover,button.disabled.warning:focus,button[disabled].warning:hover,button[disabled].warning:focus,.button.disabled.warning:hover,.button.disabled.warning:focus,.button[disabled].warning:hover,.button[disabled].warning:focus{color:#fff}button.disabled.warning:hover,button.disabled.warning:focus,button[disabled].warning:hover,button[disabled].warning:focus,.button.disabled.warning:hover,.button.disabled.warning:focus,.button[disabled].warning:hover,.button[disabled].warning:focus{background-color:#be6409}button.disabled.info,button[disabled].info,.button.disabled.info,.button[disabled].info{background-color:#334d5c;border-color:#293e4a;color:#fff;cursor:default;opacity:.7;box-shadow:none}button.disabled.info:hover,button.disabled.info:focus,button[disabled].info:hover,button[disabled].info:focus,.button.disabled.info:hover,.button.disabled.info:focus,.button[disabled].info:hover,.button[disabled].info:focus{background-color:#293e4a}button.disabled.info:hover,button.disabled.info:focus,button[disabled].info:hover,button[disabled].info:focus,.button.disabled.info:hover,.button.disabled.info:focus,.button[disabled].info:hover,.button[disabled].info:focus{color:#fff}button.disabled.info:hover,button.disabled.info:focus,button[disabled].info:hover,button[disabled].info:focus,.button.disabled.info:hover,.button.disabled.info:focus,.button[disabled].info:hover,.button[disabled].info:focus{background-color:#334d5c}button::-moz-focus-inner{border:0;padding:0}@media only screen and (min-width:40.063em){button,.button{display:inline-block}}form{margin:0 0 1rem}form .row .row{margin:0 -0.5rem}form .row .row .column,form .row .row .columns{padding:0 .5rem}form .row .row.collapse{margin:0}form .row .row.collapse .column,form .row .row.collapse .columns{padding:0}form .row .row.collapse input{-webkit-border-bottom-right-radius:0;-webkit-border-top-right-radius:0;border-bottom-right-radius:0;border-top-right-radius:0}form .row input.column,form .row input.columns,form .row textarea.column,form .row textarea.columns{padding-left:.5rem}label{font-size:.875rem;color:#4d4d4d;cursor:pointer;display:block;font-weight:normal;line-height:1.5;margin-bottom:0}label.right{float:none !important;text-align:right}label.inline{margin:0 0 1rem 0;padding:.5625rem 0}label small{text-transform:capitalize;color:#676767}.prefix,.postfix{display:block;position:relative;z-index:2;text-align:center;width:100%;padding-top:0;padding-bottom:0;border-style:solid;border-width:1px;overflow:hidden;font-size:.875rem;height:2.3125rem;line-height:2.3125rem}.postfix.button{padding-left:0;padding-right:0;padding-top:0;padding-bottom:0;text-align:center;border:none}.prefix.button{padding-left:0;padding-right:0;padding-top:0;padding-bottom:0;text-align:center;border:none}.prefix.button.radius{border-radius:0;-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}.postfix.button.radius{border-radius:0;-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}.prefix.button.round{border-radius:0;-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}.postfix.button.round{border-radius:0;-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}span.prefix,label.prefix{background:#f2f2f2;border-right:none;color:#333;border-color:#ccc}span.postfix,label.postfix{background:#f2f2f2;border-left:none;color:#333;border-color:#ccc}input[type=text],input[type=password],input[type=date],input[type=datetime],input[type=datetime-local],input[type=month],input[type=week],input[type=email],input[type=number],input[type=search],input[type=tel],input[type=time],input[type=url],input[type=color],textarea{-webkit-appearance:none;border-radius:0;background-color:#fff;font-family:inherit;border-style:solid;border-width:1px;border-color:#ccc;box-shadow:inset 0 1px 2px rgba(0,0,0,.1);color:rgba(0,0,0,.75);display:block;font-size:.875rem;margin:0 0 1rem 0;padding:.5rem;height:2.3125rem;width:100%;-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box;transition:box-shadow .45s,border-color .45s ease-in-out}input[type=text]:focus,input[type=password]:focus,input[type=date]:focus,input[type=datetime]:focus,input[type=datetime-local]:focus,input[type=month]:focus,input[type=week]:focus,input[type=email]:focus,input[type=number]:focus,input[type=search]:focus,input[type=tel]:focus,input[type=time]:focus,input[type=url]:focus,input[type=color]:focus,textarea:focus{box-shadow:0 0 5px #999;border-color:#999}input[type=text]:focus,input[type=password]:focus,input[type=date]:focus,input[type=datetime]:focus,input[type=datetime-local]:focus,input[type=month]:focus,input[type=week]:focus,input[type=email]:focus,input[type=number]:focus,input[type=search]:focus,input[type=tel]:focus,input[type=time]:focus,input[type=url]:focus,input[type=color]:focus,textarea:focus{background:#fafafa;border-color:#999;outline:none}input[type=text]:disabled,input[type=password]:disabled,input[type=date]:disabled,input[type=datetime]:disabled,input[type=datetime-local]:disabled,input[type=month]:disabled,input[type=week]:disabled,input[type=email]:disabled,input[type=number]:disabled,input[type=search]:disabled,input[type=tel]:disabled,input[type=time]:disabled,input[type=url]:disabled,input[type=color]:disabled,textarea:disabled{background-color:#ddd;cursor:default}input[type=text][disabled],input[type=text][readonly],fieldset[disabled] input[type=text],input[type=password][disabled],input[type=password][readonly],fieldset[disabled] input[type=password],input[type=date][disabled],input[type=date][readonly],fieldset[disabled] input[type=date],input[type=datetime][disabled],input[type=datetime][readonly],fieldset[disabled] input[type=datetime],input[type=datetime-local][disabled],input[type=datetime-local][readonly],fieldset[disabled] input[type=datetime-local],input[type=month][disabled],input[type=month][readonly],fieldset[disabled] input[type=month],input[type=week][disabled],input[type=week][readonly],fieldset[disabled] input[type=week],input[type=email][disabled],input[type=email][readonly],fieldset[disabled] input[type=email],input[type=number][disabled],input[type=number][readonly],fieldset[disabled] input[type=number],input[type=search][disabled],input[type=search][readonly],fieldset[disabled] input[type=search],input[type=tel][disabled],input[type=tel][readonly],fieldset[disabled] input[type=tel],input[type=time][disabled],input[type=time][readonly],fieldset[disabled] input[type=time],input[type=url][disabled],input[type=url][readonly],fieldset[disabled] input[type=url],input[type=color][disabled],input[type=color][readonly],fieldset[disabled] input[type=color],textarea[disabled],textarea[readonly],fieldset[disabled] textarea{background-color:#ddd;cursor:default}input[type=text].radius,input[type=password].radius,input[type=date].radius,input[type=datetime].radius,input[type=datetime-local].radius,input[type=month].radius,input[type=week].radius,input[type=email].radius,input[type=number].radius,input[type=search].radius,input[type=tel].radius,input[type=time].radius,input[type=url].radius,input[type=color].radius,textarea.radius{border-radius:3px}form .row .prefix-radius.row.collapse input,form .row .prefix-radius.row.collapse textarea,form .row .prefix-radius.row.collapse select{border-radius:0;-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}form .row .prefix-radius.row.collapse .prefix{border-radius:0;-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}form .row .postfix-radius.row.collapse input,form .row .postfix-radius.row.collapse textarea,form .row .postfix-radius.row.collapse select{border-radius:0;-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}form .row .postfix-radius.row.collapse .postfix{border-radius:0;-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}form .row .prefix-round.row.collapse input,form .row .prefix-round.row.collapse textarea,form .row .prefix-round.row.collapse select{border-radius:0;-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}form .row .prefix-round.row.collapse .prefix{border-radius:0;-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}form .row .postfix-round.row.collapse input,form .row .postfix-round.row.collapse textarea,form .row .postfix-round.row.collapse select{border-radius:0;-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}form .row .postfix-round.row.collapse .postfix{border-radius:0;-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}input[type=submit]{-webkit-appearance:none;border-radius:0}textarea[rows]{height:auto}textarea{max-width:100%}select{-webkit-appearance:none !important;border-radius:0;background-color:#fafafa;background-image:url(data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZlcnNpb249IjEuMSIgeD0iMTJweCIgeT0iMHB4IiB3aWR0aD0iMjRweCIgaGVpZ2h0PSIzcHgiIHZpZXdCb3g9IjAgMCA2IDMiIGVuYWJsZS1iYWNrZ3JvdW5kPSJuZXcgMCAwIDYgMyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI+PHBvbHlnb24gcG9pbnRzPSI1Ljk5MiwwIDIuOTkyLDMgLTAuMDA4LDAgIi8+PC9zdmc+);background-position:100% center;background-repeat:no-repeat;border-style:solid;border-width:1px;border-color:#ccc;padding:.5rem;font-size:.875rem;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;color:rgba(0,0,0,.75);line-height:normal;border-radius:0;height:2.3125rem}select::-ms-expand{display:none}select.radius{border-radius:3px}select:hover{background-color:#f3f3f3;border-color:#999}select:disabled{background-color:#ddd;cursor:default}input[type=file],input[type=checkbox],input[type=radio],select{margin:0 0 1rem 0}input[type=checkbox]+label,input[type=radio]+label{display:inline-block;margin-left:.5rem;margin-right:1rem;margin-bottom:0;vertical-align:baseline}input[type=file]{width:100%}fieldset{border:1px solid #ddd;padding:1.25rem;margin:1.125rem 0}fieldset legend{font-weight:bold;background:#fff;padding:0 .1875rem;margin:0;margin-left:-0.1875rem}[data-abide] .error small.error,[data-abide] .error span.error,[data-abide] span.error,[data-abide] small.error{display:block;padding:.375rem .5625rem .5625rem;margin-top:-1px;margin-bottom:1rem;font-size:.75rem;font-weight:normal;font-style:italic;background:#df4949;color:#fff}[data-abide] span.error,[data-abide] small.error{display:none}span.error,small.error{display:block;padding:.375rem .5625rem .5625rem;margin-top:-1px;margin-bottom:1rem;font-size:.75rem;font-weight:normal;font-style:italic;background:#df4949;color:#fff}.error input,.error textarea,.error select{margin-bottom:0}.error input[type=checkbox],.error input[type=radio]{margin-bottom:1rem}.error label,.error label.error{color:#df4949}.error small.error{display:block;padding:.375rem .5625rem .5625rem;margin-top:-1px;margin-bottom:1rem;font-size:.75rem;font-weight:normal;font-style:italic;background:#df4949;color:#fff}.error>label>small{color:#676767;background:rgba(0,0,0,0);padding:0;text-transform:capitalize;font-style:normal;font-size:60%;margin:0;display:inline}.error span.error-message{display:block}input.error,textarea.error,select.error{margin-bottom:0}label.error{color:#df4949}meta.foundation-mq-topbar{font-family:"/only screen and (min-width: 64.063em)/";width:64.063em}.contain-to-grid{width:100%;background:#fdfdfd}.contain-to-grid .top-bar{margin-bottom:0}.fixed{width:100%;left:0;position:fixed;top:0;z-index:99}.fixed.expanded:not(.top-bar){overflow-y:auto;height:auto;width:100%;max-height:100%}.fixed.expanded:not(.top-bar) .title-area{position:fixed;width:100%;z-index:99}.fixed.expanded:not(.top-bar) .top-bar-section{z-index:98;margin-top:3.125rem}.top-bar{overflow:hidden;height:3.125rem;line-height:3.125rem;position:relative;background:#fdfdfd;margin-bottom:0}.top-bar ul{margin-bottom:0;list-style:none}.top-bar .row{max-width:none}.top-bar form,.top-bar input{margin-bottom:0}.top-bar input{height:1.75rem;padding-top:.35rem;padding-bottom:.35rem;font-size:.75rem}.top-bar .button,.top-bar button{padding-top:.4125rem;padding-bottom:.4125rem;margin-bottom:0;font-size:.75rem}@media only screen and (max-width: 40em){.top-bar .button,.top-bar button{position:relative;top:-1px}}.top-bar .title-area{position:relative;margin:0}.top-bar .name{height:3.125rem;margin:0;font-size:16px}.top-bar .name h1,.top-bar .name h2,.top-bar .name h3,.top-bar .name h4,.top-bar .name p,.top-bar .name span{line-height:3.125rem;font-size:1.1875rem;margin:0}.top-bar .name h1 a,.top-bar .name h2 a,.top-bar .name h3 a,.top-bar .name h4 a,.top-bar .name p a,.top-bar .name span a{font-weight:bold;color:#000;width:75%;display:block;padding:0 1.0416666667rem}.top-bar .toggle-topbar{position:absolute;right:0;top:0}.top-bar .toggle-topbar a{color:#000;text-transform:uppercase;font-size:.8125rem;font-weight:bold;position:relative;display:block;padding:0 1.0416666667rem;height:3.125rem;line-height:3.125rem}.top-bar .toggle-topbar.menu-icon{top:50%;margin-top:-16px}.top-bar .toggle-topbar.menu-icon a{height:34px;line-height:33px;padding:0 2.6041666667rem 0 1.0416666667rem;color:#000;position:relative}.top-bar .toggle-topbar.menu-icon a span::after{content:"";position:absolute;display:block;height:0;top:50%;margin-top:-8px;right:1.0416666667rem;box-shadow:0 0 0 1px #000,0 7px 0 1px #000,0 14px 0 1px #000;width:16px}.top-bar .toggle-topbar.menu-icon a span:hover:after{box-shadow:0 0 0 1px "",0 7px 0 1px "",0 14px 0 1px ""}.top-bar.expanded{height:auto;background:rgba(0,0,0,0)}.top-bar.expanded .title-area{background:#fdfdfd}.top-bar.expanded .toggle-topbar a{color:#a1d044}.top-bar.expanded .toggle-topbar a span::after{box-shadow:0 0 0 1px #a1d044,0 7px 0 1px #a1d044,0 14px 0 1px #a1d044}.top-bar-section{left:0;position:relative;width:auto;transition:left 300ms ease-out}.top-bar-section ul{padding:0;width:100%;height:auto;display:block;font-size:16px;margin:0}.top-bar-section .divider,.top-bar-section [role=separator]{border-top:solid 0px #7f7f7f;clear:both;height:1px;width:100%}.top-bar-section ul li{background:#a1d044}.top-bar-section ul li>a{display:block;width:100%;color:#000;padding:12px 0 12px 0;padding-left:1.0416666667rem;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-size:.9375rem;font-weight:normal;text-transform:uppercase}.top-bar-section ul li>a.button{font-size:.9375rem;padding-right:1.0416666667rem;padding-left:1.0416666667rem;background-color:#334d5c;border-color:#293e4a;color:#fff}.top-bar-section ul li>a.button:hover,.top-bar-section ul li>a.button:focus{background-color:#293e4a}.top-bar-section ul li>a.button:hover,.top-bar-section ul li>a.button:focus{color:#fff}.top-bar-section ul li>a.button.secondary{background-color:#a1d044;border-color:#84b02c;color:#fff}.top-bar-section ul li>a.button.secondary:hover,.top-bar-section ul li>a.button.secondary:focus{background-color:#84b02c}.top-bar-section ul li>a.button.secondary:hover,.top-bar-section ul li>a.button.secondary:focus{color:#fff}.top-bar-section ul li>a.button.success{background-color:#a1d044;border-color:#84b02c;color:#fff}.top-bar-section ul li>a.button.success:hover,.top-bar-section ul li>a.button.success:focus{background-color:#84b02c}.top-bar-section ul li>a.button.success:hover,.top-bar-section ul li>a.button.success:focus{color:#fff}.top-bar-section ul li>a.button.alert{background-color:#df4949;border-color:#c92323;color:#fff}.top-bar-section ul li>a.button.alert:hover,.top-bar-section ul li>a.button.alert:focus{background-color:#c92323}.top-bar-section ul li>a.button.alert:hover,.top-bar-section ul li>a.button.alert:focus{color:#fff}.top-bar-section ul li>a.button.warning{background-color:#be6409;border-color:#985007;color:#fff}.top-bar-section ul li>a.button.warning:hover,.top-bar-section ul li>a.button.warning:focus{background-color:#985007}.top-bar-section ul li>a.button.warning:hover,.top-bar-section ul li>a.button.warning:focus{color:#fff}.top-bar-section ul li>button{font-size:.9375rem;padding-right:1.0416666667rem;padding-left:1.0416666667rem;background-color:#334d5c;border-color:#293e4a;color:#fff}.top-bar-section ul li>button:hover,.top-bar-section ul li>button:focus{background-color:#293e4a}.top-bar-section ul li>button:hover,.top-bar-section ul li>button:focus{color:#fff}.top-bar-section ul li>button.secondary{background-color:#a1d044;border-color:#84b02c;color:#fff}.top-bar-section ul li>button.secondary:hover,.top-bar-section ul li>button.secondary:focus{background-color:#84b02c}.top-bar-section ul li>button.secondary:hover,.top-bar-section ul li>button.secondary:focus{color:#fff}.top-bar-section ul li>button.success{background-color:#a1d044;border-color:#84b02c;color:#fff}.top-bar-section ul li>button.success:hover,.top-bar-section ul li>button.success:focus{background-color:#84b02c}.top-bar-section ul li>button.success:hover,.top-bar-section ul li>button.success:focus{color:#fff}.top-bar-section ul li>button.alert{background-color:#df4949;border-color:#c92323;color:#fff}.top-bar-section ul li>button.alert:hover,.top-bar-section ul li>button.alert:focus{background-color:#c92323}.top-bar-section ul li>button.alert:hover,.top-bar-section ul li>button.alert:focus{color:#fff}.top-bar-section ul li>button.warning{background-color:#be6409;border-color:#985007;color:#fff}.top-bar-section ul li>button.warning:hover,.top-bar-section ul li>button.warning:focus{background-color:#985007}.top-bar-section ul li>button.warning:hover,.top-bar-section ul li>button.warning:focus{color:#fff}.top-bar-section ul li:hover:not(.has-form)>a{background-color:#555;background:#a1d044;color:#000}.top-bar-section ul li.active>a{background:#a1d044;color:#000}.top-bar-section ul li.active>a:hover{background:#45b29d;color:#000}.top-bar-section .has-form{padding:1.0416666667rem}.top-bar-section .has-dropdown{position:relative}.top-bar-section .has-dropdown>a:after{content:"";display:block;width:0;height:0;border:inset 5px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0) rgba(51,77,92,.4);border-left-style:solid;margin-right:1.0416666667rem;margin-top:-4.5px;position:absolute;top:50%;right:0}.top-bar-section .has-dropdown.moved{position:static}.top-bar-section .has-dropdown.moved>.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important;width:100%}.top-bar-section .has-dropdown.moved>a:after{display:none}.top-bar-section .dropdown{padding:0;position:absolute;left:100%;top:0;z-index:99;display:block;position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}.top-bar-section .dropdown li{width:100%;height:auto}.top-bar-section .dropdown li a{font-weight:normal;padding:8px 1.0416666667rem}.top-bar-section .dropdown li a.parent-link{font-weight:normal}.top-bar-section .dropdown li.title h5,.top-bar-section .dropdown li.parent-link{margin-bottom:0;margin-top:0;font-size:1.125rem}.top-bar-section .dropdown li.title h5 a,.top-bar-section .dropdown li.parent-link a{color:#000;display:block}.top-bar-section .dropdown li.title h5 a:hover,.top-bar-section .dropdown li.parent-link a:hover{background:none}.top-bar-section .dropdown li.has-form{padding:8px 1.0416666667rem}.top-bar-section .dropdown li .button,.top-bar-section .dropdown li button{top:auto}.top-bar-section .dropdown label{padding:8px 1.0416666667rem 2px;margin-bottom:0;text-transform:uppercase;color:#45b29d;font-weight:bold;font-size:.625rem}.js-generated{display:block}@media only screen and (min-width: 64.063em){.top-bar{background:#fdfdfd;overflow:visible}.top-bar:before,.top-bar:after{content:" ";display:table}.top-bar:after{clear:both}.top-bar .toggle-topbar{display:none}.top-bar .title-area{float:left}.top-bar .name h1 a{width:auto}.top-bar input,.top-bar .button,.top-bar button{font-size:.875rem;position:relative;height:1.75rem;top:.6875rem}.top-bar.expanded{background:#fdfdfd}.contain-to-grid .top-bar{max-width:93.75rem;margin:0 auto;margin-bottom:0}.top-bar-section{transition:none 0 0;left:0 !important}.top-bar-section ul{width:auto;height:auto !important;display:inline}.top-bar-section ul li{float:left}.top-bar-section ul li .js-generated{display:none}.top-bar-section li.hover>a:not(.button){background-color:#555;background:#a1d044;color:#000}.top-bar-section li:not(.has-form) a:not(.button){padding:0 1.0416666667rem;line-height:3.125rem;background:#fdfdfd}.top-bar-section li:not(.has-form) a:not(.button):hover{background-color:#555;background:#a1d044}.top-bar-section li.active:not(.has-form) a:not(.button){padding:0 1.0416666667rem;line-height:3.125rem;color:#000;background:#a1d044}.top-bar-section li.active:not(.has-form) a:not(.button):hover{background:#45b29d;color:#000}.top-bar-section .has-dropdown>a{padding-right:2.2916666667rem !important}.top-bar-section .has-dropdown>a:after{content:"";display:block;width:0;height:0;border:inset 5px;border-color:rgba(51,77,92,.4) rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0);border-top-style:solid;margin-top:-2.5px;top:1.5625rem}.top-bar-section .has-dropdown.moved{position:relative}.top-bar-section .has-dropdown.moved>.dropdown{display:block;position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}.top-bar-section .has-dropdown.hover>.dropdown,.top-bar-section .has-dropdown.not-click:hover>.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important}.top-bar-section .has-dropdown>a:focus+.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important}.top-bar-section .has-dropdown .dropdown li.has-dropdown>a:after{border:none;content:"»";top:1rem;margin-top:-1px;right:5px;line-height:1.2}.top-bar-section .dropdown{left:0;top:auto;background:rgba(0,0,0,0);min-width:100%}.top-bar-section .dropdown li a{color:#000;line-height:3.125rem;white-space:nowrap;padding:12px 1.0416666667rem;background:#45b29d}.top-bar-section .dropdown li:not(.has-form):not(.active)>a:not(.button){color:#000;background:#45b29d}.top-bar-section .dropdown li:not(.has-form):not(.active):hover>a:not(.button){color:#000;background-color:#555;background:#a1d044}.top-bar-section .dropdown li label{white-space:nowrap;background:#333}.top-bar-section .dropdown li .dropdown{left:100%;top:0}.top-bar-section>ul>.divider,.top-bar-section>ul>[role=separator]{border-bottom:none;border-top:none;border-right:solid 0px #fdfdfd;clear:none;height:3.125rem;width:0}.top-bar-section .has-form{background:#fdfdfd;padding:0 1.0416666667rem;height:3.125rem}.top-bar-section .right li .dropdown{left:auto;right:0}.top-bar-section .right li .dropdown li .dropdown{right:100%}.top-bar-section .left li .dropdown{right:auto;left:0}.top-bar-section .left li .dropdown li .dropdown{left:100%}.no-js .top-bar-section ul li:hover>a{background-color:#555;background:#a1d044;color:#000}.no-js .top-bar-section ul li:active>a{background:#a1d044;color:#000}.no-js .top-bar-section .has-dropdown:hover>.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important}.no-js .top-bar-section .has-dropdown>a:focus+.dropdown{display:block;position:static !important;height:auto;width:auto;overflow:visible;clip:auto;position:absolute !important}}.accordion{margin-bottom:0}.accordion:before,.accordion:after{content:" ";display:table}.accordion:after{clear:both}.accordion .accordion-navigation,.accordion dd{display:block;margin-bottom:0 !important}.accordion .accordion-navigation.active>a,.accordion dd.active>a{background:#e8e8e8}.accordion .accordion-navigation>a,.accordion dd>a{background:#efefef;color:#222;padding:.75rem;display:block;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-size:1rem}.accordion .accordion-navigation>a:hover,.accordion dd>a:hover{background:#e3e3e3}.accordion .accordion-navigation>.content,.accordion dd>.content{display:none;padding:.9375rem}.accordion .accordion-navigation>.content.active,.accordion dd>.content.active{display:block;background:#fdfdfd}.alert-box{border-style:solid;border-width:1px;display:block;font-weight:normal;margin-bottom:1.25rem;position:relative;padding:.875rem 1.5rem .875rem .875rem;font-size:.9375rem;transition:opacity 300ms ease-out;background-color:#334d5c;border-color:#2c424f;color:#fff}.alert-box .close{font-size:1.375rem;padding:9px 6px 4px;line-height:0;position:absolute;top:50%;margin-top:-0.6875rem;right:.25rem;color:#333;opacity:.3;background:inherit}.alert-box .close:hover,.alert-box .close:focus{opacity:.5}.alert-box.radius{border-radius:3px}.alert-box.round{border-radius:1000px}.alert-box.success{background-color:#a1d044;border-color:#8ebe30;color:#fff}.alert-box.alert{background-color:#df4949;border-color:#d82626;color:#fff}.alert-box.secondary{background-color:#a1d044;border-color:#8ebe30;color:#fff}.alert-box.warning{background-color:#be6409;border-color:#a35608;color:#fff}.alert-box.info{background-color:#334d5c;border-color:#2c424f;color:#fff}.alert-box.alert-close{opacity:0}.breadcrumbs{display:block;padding:.5625rem .875rem .5625rem;overflow:hidden;margin-left:0;list-style:none;border-style:solid;border-width:0;background-color:#e4e4e4;border-color:#e4e4e4;border-radius:0}.breadcrumbs>*{margin:0;float:left;font-size:.6875rem;line-height:.6875rem;text-transform:uppercase;color:#334d5c}.breadcrumbs>*:hover a,.breadcrumbs>*:focus a{text-decoration:underline}.breadcrumbs>* a{color:#334d5c}.breadcrumbs>*.current{cursor:default;color:#333}.breadcrumbs>*.current a{cursor:default;color:#333}.breadcrumbs>*.current:hover,.breadcrumbs>*.current:hover a,.breadcrumbs>*.current:focus,.breadcrumbs>*.current:focus a{text-decoration:none}.breadcrumbs>*.unavailable{color:#999}.breadcrumbs>*.unavailable a{color:#999}.breadcrumbs>*.unavailable:hover,.breadcrumbs>*.unavailable:hover a,.breadcrumbs>*.unavailable:focus,.breadcrumbs>*.unavailable a:focus{text-decoration:none;color:#999;cursor:default}.breadcrumbs>*:before{content:"/";color:#aaa;margin:0 .75rem;position:relative;top:1px}.breadcrumbs>*:first-child:before{content:" ";margin:0}[aria-label=breadcrumbs] [aria-hidden=true]:after{content:"/"}[class*=block-grid-]{display:block;padding:0;margin:0 -0.625rem}[class*=block-grid-]:before,[class*=block-grid-]:after{content:" ";display:table}[class*=block-grid-]:after{clear:both}[class*=block-grid-]>li{display:block;height:auto;float:left;padding:0 .625rem 1.25rem}@media only screen{.small-block-grid-1>li{width:100%;list-style:none}.small-block-grid-1>li:nth-of-type(1n){clear:none}.small-block-grid-1>li:nth-of-type(1n+1){clear:both}.small-block-grid-2>li{width:50%;list-style:none}.small-block-grid-2>li:nth-of-type(1n){clear:none}.small-block-grid-2>li:nth-of-type(2n+1){clear:both}.small-block-grid-3>li{width:33.3333333333%;list-style:none}.small-block-grid-3>li:nth-of-type(1n){clear:none}.small-block-grid-3>li:nth-of-type(3n+1){clear:both}.small-block-grid-4>li{width:25%;list-style:none}.small-block-grid-4>li:nth-of-type(1n){clear:none}.small-block-grid-4>li:nth-of-type(4n+1){clear:both}.small-block-grid-5>li{width:20%;list-style:none}.small-block-grid-5>li:nth-of-type(1n){clear:none}.small-block-grid-5>li:nth-of-type(5n+1){clear:both}.small-block-grid-6>li{width:16.6666666667%;list-style:none}.small-block-grid-6>li:nth-of-type(1n){clear:none}.small-block-grid-6>li:nth-of-type(6n+1){clear:both}.small-block-grid-7>li{width:14.2857142857%;list-style:none}.small-block-grid-7>li:nth-of-type(1n){clear:none}.small-block-grid-7>li:nth-of-type(7n+1){clear:both}.small-block-grid-8>li{width:12.5%;list-style:none}.small-block-grid-8>li:nth-of-type(1n){clear:none}.small-block-grid-8>li:nth-of-type(8n+1){clear:both}.small-block-grid-9>li{width:11.1111111111%;list-style:none}.small-block-grid-9>li:nth-of-type(1n){clear:none}.small-block-grid-9>li:nth-of-type(9n+1){clear:both}.small-block-grid-10>li{width:10%;list-style:none}.small-block-grid-10>li:nth-of-type(1n){clear:none}.small-block-grid-10>li:nth-of-type(10n+1){clear:both}.small-block-grid-11>li{width:9.0909090909%;list-style:none}.small-block-grid-11>li:nth-of-type(1n){clear:none}.small-block-grid-11>li:nth-of-type(11n+1){clear:both}.small-block-grid-12>li{width:8.3333333333%;list-style:none}.small-block-grid-12>li:nth-of-type(1n){clear:none}.small-block-grid-12>li:nth-of-type(12n+1){clear:both}}@media only screen and (min-width:40.063em){.medium-block-grid-1>li{width:100%;list-style:none}.medium-block-grid-1>li:nth-of-type(1n){clear:none}.medium-block-grid-1>li:nth-of-type(1n+1){clear:both}.medium-block-grid-2>li{width:50%;list-style:none}.medium-block-grid-2>li:nth-of-type(1n){clear:none}.medium-block-grid-2>li:nth-of-type(2n+1){clear:both}.medium-block-grid-3>li{width:33.3333333333%;list-style:none}.medium-block-grid-3>li:nth-of-type(1n){clear:none}.medium-block-grid-3>li:nth-of-type(3n+1){clear:both}.medium-block-grid-4>li{width:25%;list-style:none}.medium-block-grid-4>li:nth-of-type(1n){clear:none}.medium-block-grid-4>li:nth-of-type(4n+1){clear:both}.medium-block-grid-5>li{width:20%;list-style:none}.medium-block-grid-5>li:nth-of-type(1n){clear:none}.medium-block-grid-5>li:nth-of-type(5n+1){clear:both}.medium-block-grid-6>li{width:16.6666666667%;list-style:none}.medium-block-grid-6>li:nth-of-type(1n){clear:none}.medium-block-grid-6>li:nth-of-type(6n+1){clear:both}.medium-block-grid-7>li{width:14.2857142857%;list-style:none}.medium-block-grid-7>li:nth-of-type(1n){clear:none}.medium-block-grid-7>li:nth-of-type(7n+1){clear:both}.medium-block-grid-8>li{width:12.5%;list-style:none}.medium-block-grid-8>li:nth-of-type(1n){clear:none}.medium-block-grid-8>li:nth-of-type(8n+1){clear:both}.medium-block-grid-9>li{width:11.1111111111%;list-style:none}.medium-block-grid-9>li:nth-of-type(1n){clear:none}.medium-block-grid-9>li:nth-of-type(9n+1){clear:both}.medium-block-grid-10>li{width:10%;list-style:none}.medium-block-grid-10>li:nth-of-type(1n){clear:none}.medium-block-grid-10>li:nth-of-type(10n+1){clear:both}.medium-block-grid-11>li{width:9.0909090909%;list-style:none}.medium-block-grid-11>li:nth-of-type(1n){clear:none}.medium-block-grid-11>li:nth-of-type(11n+1){clear:both}.medium-block-grid-12>li{width:8.3333333333%;list-style:none}.medium-block-grid-12>li:nth-of-type(1n){clear:none}.medium-block-grid-12>li:nth-of-type(12n+1){clear:both}}@media only screen and (min-width:64.063em){.large-block-grid-1>li{width:100%;list-style:none}.large-block-grid-1>li:nth-of-type(1n){clear:none}.large-block-grid-1>li:nth-of-type(1n+1){clear:both}.large-block-grid-2>li{width:50%;list-style:none}.large-block-grid-2>li:nth-of-type(1n){clear:none}.large-block-grid-2>li:nth-of-type(2n+1){clear:both}.large-block-grid-3>li{width:33.3333333333%;list-style:none}.large-block-grid-3>li:nth-of-type(1n){clear:none}.large-block-grid-3>li:nth-of-type(3n+1){clear:both}.large-block-grid-4>li{width:25%;list-style:none}.large-block-grid-4>li:nth-of-type(1n){clear:none}.large-block-grid-4>li:nth-of-type(4n+1){clear:both}.large-block-grid-5>li{width:20%;list-style:none}.large-block-grid-5>li:nth-of-type(1n){clear:none}.large-block-grid-5>li:nth-of-type(5n+1){clear:both}.large-block-grid-6>li{width:16.6666666667%;list-style:none}.large-block-grid-6>li:nth-of-type(1n){clear:none}.large-block-grid-6>li:nth-of-type(6n+1){clear:both}.large-block-grid-7>li{width:14.2857142857%;list-style:none}.large-block-grid-7>li:nth-of-type(1n){clear:none}.large-block-grid-7>li:nth-of-type(7n+1){clear:both}.large-block-grid-8>li{width:12.5%;list-style:none}.large-block-grid-8>li:nth-of-type(1n){clear:none}.large-block-grid-8>li:nth-of-type(8n+1){clear:both}.large-block-grid-9>li{width:11.1111111111%;list-style:none}.large-block-grid-9>li:nth-of-type(1n){clear:none}.large-block-grid-9>li:nth-of-type(9n+1){clear:both}.large-block-grid-10>li{width:10%;list-style:none}.large-block-grid-10>li:nth-of-type(1n){clear:none}.large-block-grid-10>li:nth-of-type(10n+1){clear:both}.large-block-grid-11>li{width:9.0909090909%;list-style:none}.large-block-grid-11>li:nth-of-type(1n){clear:none}.large-block-grid-11>li:nth-of-type(11n+1){clear:both}.large-block-grid-12>li{width:8.3333333333%;list-style:none}.large-block-grid-12>li:nth-of-type(1n){clear:none}.large-block-grid-12>li:nth-of-type(12n+1){clear:both}}.button-group{list-style:none;margin:0;left:0}.button-group:before,.button-group:after{content:" ";display:table}.button-group:after{clear:both}.button-group>li{margin:0 -2px;display:inline-block}.button-group>li>button,.button-group>li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group>li:first-child button,.button-group>li:first-child .button{border-left:0}.button-group.stack>li{margin:0 -2px;display:inline-block;display:block;margin:0;float:none}.button-group.stack>li>button,.button-group.stack>li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.stack>li:first-child button,.button-group.stack>li:first-child .button{border-left:0}.button-group.stack>li>button,.button-group.stack>li .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.stack>li:first-child button,.button-group.stack>li:first-child .button{border-top:0}.button-group.stack-for-small>li{margin:0 -2px;display:inline-block}.button-group.stack-for-small>li>button,.button-group.stack-for-small>li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.stack-for-small>li:first-child button,.button-group.stack-for-small>li:first-child .button{border-left:0}@media only screen and (max-width: 40em){.button-group.stack-for-small>li{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.stack-for-small>li>button,.button-group.stack-for-small>li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.stack-for-small>li:first-child button,.button-group.stack-for-small>li:first-child .button{border-left:0}.button-group.stack-for-small>li>button,.button-group.stack-for-small>li .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.stack-for-small>li:first-child button,.button-group.stack-for-small>li:first-child .button{border-top:0}}.button-group.radius>*{margin:0 -2px;display:inline-block}.button-group.radius>*>button,.button-group.radius>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.radius>*:first-child button,.button-group.radius>*:first-child .button{border-left:0}.button-group.radius>*,.button-group.radius>*>a,.button-group.radius>*>button,.button-group.radius>*>.button{border-radius:0}.button-group.radius>*:first-child,.button-group.radius>*:first-child>a,.button-group.radius>*:first-child>button,.button-group.radius>*:first-child>.button{-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}.button-group.radius>*:last-child,.button-group.radius>*:last-child>a,.button-group.radius>*:last-child>button,.button-group.radius>*:last-child>.button{-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}.button-group.radius.stack>*{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.radius.stack>*>button,.button-group.radius.stack>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.radius.stack>*:first-child button,.button-group.radius.stack>*:first-child .button{border-left:0}.button-group.radius.stack>*>button,.button-group.radius.stack>* .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.radius.stack>*:first-child button,.button-group.radius.stack>*:first-child .button{border-top:0}.button-group.radius.stack>*,.button-group.radius.stack>*>a,.button-group.radius.stack>*>button,.button-group.radius.stack>*>.button{border-radius:0}.button-group.radius.stack>*:first-child,.button-group.radius.stack>*:first-child>a,.button-group.radius.stack>*:first-child>button,.button-group.radius.stack>*:first-child>.button{-webkit-top-left-radius:3px;-webkit-top-right-radius:3px;border-top-left-radius:3px;border-top-right-radius:3px}.button-group.radius.stack>*:last-child,.button-group.radius.stack>*:last-child>a,.button-group.radius.stack>*:last-child>button,.button-group.radius.stack>*:last-child>.button{-webkit-bottom-left-radius:3px;-webkit-bottom-right-radius:3px;border-bottom-left-radius:3px;border-bottom-right-radius:3px}@media only screen and (min-width:40.063em){.button-group.radius.stack-for-small>*{margin:0 -2px;display:inline-block}.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.radius.stack-for-small>*:first-child button,.button-group.radius.stack-for-small>*:first-child .button{border-left:0}.button-group.radius.stack-for-small>*,.button-group.radius.stack-for-small>*>a,.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>*>.button{border-radius:0}.button-group.radius.stack-for-small>*:first-child,.button-group.radius.stack-for-small>*:first-child>a,.button-group.radius.stack-for-small>*:first-child>button,.button-group.radius.stack-for-small>*:first-child>.button{-webkit-border-bottom-left-radius:3px;-webkit-border-top-left-radius:3px;border-bottom-left-radius:3px;border-top-left-radius:3px}.button-group.radius.stack-for-small>*:last-child,.button-group.radius.stack-for-small>*:last-child>a,.button-group.radius.stack-for-small>*:last-child>button,.button-group.radius.stack-for-small>*:last-child>.button{-webkit-border-bottom-right-radius:3px;-webkit-border-top-right-radius:3px;border-bottom-right-radius:3px;border-top-right-radius:3px}}@media only screen and (max-width: 40em){.button-group.radius.stack-for-small>*{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.radius.stack-for-small>*:first-child button,.button-group.radius.stack-for-small>*:first-child .button{border-left:0}.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>* .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.radius.stack-for-small>*:first-child button,.button-group.radius.stack-for-small>*:first-child .button{border-top:0}.button-group.radius.stack-for-small>*,.button-group.radius.stack-for-small>*>a,.button-group.radius.stack-for-small>*>button,.button-group.radius.stack-for-small>*>.button{border-radius:0}.button-group.radius.stack-for-small>*:first-child,.button-group.radius.stack-for-small>*:first-child>a,.button-group.radius.stack-for-small>*:first-child>button,.button-group.radius.stack-for-small>*:first-child>.button{-webkit-top-left-radius:3px;-webkit-top-right-radius:3px;border-top-left-radius:3px;border-top-right-radius:3px}.button-group.radius.stack-for-small>*:last-child,.button-group.radius.stack-for-small>*:last-child>a,.button-group.radius.stack-for-small>*:last-child>button,.button-group.radius.stack-for-small>*:last-child>.button{-webkit-bottom-left-radius:3px;-webkit-bottom-right-radius:3px;border-bottom-left-radius:3px;border-bottom-right-radius:3px}}.button-group.round>*{margin:0 -2px;display:inline-block}.button-group.round>*>button,.button-group.round>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.round>*:first-child button,.button-group.round>*:first-child .button{border-left:0}.button-group.round>*,.button-group.round>*>a,.button-group.round>*>button,.button-group.round>*>.button{border-radius:0}.button-group.round>*:first-child,.button-group.round>*:first-child>a,.button-group.round>*:first-child>button,.button-group.round>*:first-child>.button{-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}.button-group.round>*:last-child,.button-group.round>*:last-child>a,.button-group.round>*:last-child>button,.button-group.round>*:last-child>.button{-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}.button-group.round.stack>*{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.round.stack>*>button,.button-group.round.stack>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.round.stack>*:first-child button,.button-group.round.stack>*:first-child .button{border-left:0}.button-group.round.stack>*>button,.button-group.round.stack>* .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.round.stack>*:first-child button,.button-group.round.stack>*:first-child .button{border-top:0}.button-group.round.stack>*,.button-group.round.stack>*>a,.button-group.round.stack>*>button,.button-group.round.stack>*>.button{border-radius:0}.button-group.round.stack>*:first-child,.button-group.round.stack>*:first-child>a,.button-group.round.stack>*:first-child>button,.button-group.round.stack>*:first-child>.button{-webkit-top-left-radius:1rem;-webkit-top-right-radius:1rem;border-top-left-radius:1rem;border-top-right-radius:1rem}.button-group.round.stack>*:last-child,.button-group.round.stack>*:last-child>a,.button-group.round.stack>*:last-child>button,.button-group.round.stack>*:last-child>.button{-webkit-bottom-left-radius:1rem;-webkit-bottom-right-radius:1rem;border-bottom-left-radius:1rem;border-bottom-right-radius:1rem}@media only screen and (min-width:40.063em){.button-group.round.stack-for-small>*{margin:0 -2px;display:inline-block}.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.round.stack-for-small>*:first-child button,.button-group.round.stack-for-small>*:first-child .button{border-left:0}.button-group.round.stack-for-small>*,.button-group.round.stack-for-small>*>a,.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>*>.button{border-radius:0}.button-group.round.stack-for-small>*:first-child,.button-group.round.stack-for-small>*:first-child>a,.button-group.round.stack-for-small>*:first-child>button,.button-group.round.stack-for-small>*:first-child>.button{-webkit-border-bottom-left-radius:1000px;-webkit-border-top-left-radius:1000px;border-bottom-left-radius:1000px;border-top-left-radius:1000px}.button-group.round.stack-for-small>*:last-child,.button-group.round.stack-for-small>*:last-child>a,.button-group.round.stack-for-small>*:last-child>button,.button-group.round.stack-for-small>*:last-child>.button{-webkit-border-bottom-right-radius:1000px;-webkit-border-top-right-radius:1000px;border-bottom-right-radius:1000px;border-top-right-radius:1000px}}@media only screen and (max-width: 40em){.button-group.round.stack-for-small>*{margin:0 -2px;display:inline-block;display:block;margin:0}.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>* .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.round.stack-for-small>*:first-child button,.button-group.round.stack-for-small>*:first-child .button{border-left:0}.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>* .button{border-top:1px solid;border-color:rgba(255,255,255,.5);border-left-width:0;margin:0;display:block}.button-group.round.stack-for-small>*:first-child button,.button-group.round.stack-for-small>*:first-child .button{border-top:0}.button-group.round.stack-for-small>*,.button-group.round.stack-for-small>*>a,.button-group.round.stack-for-small>*>button,.button-group.round.stack-for-small>*>.button{border-radius:0}.button-group.round.stack-for-small>*:first-child,.button-group.round.stack-for-small>*:first-child>a,.button-group.round.stack-for-small>*:first-child>button,.button-group.round.stack-for-small>*:first-child>.button{-webkit-top-left-radius:1rem;-webkit-top-right-radius:1rem;border-top-left-radius:1rem;border-top-right-radius:1rem}.button-group.round.stack-for-small>*:last-child,.button-group.round.stack-for-small>*:last-child>a,.button-group.round.stack-for-small>*:last-child>button,.button-group.round.stack-for-small>*:last-child>.button{-webkit-bottom-left-radius:1rem;-webkit-bottom-right-radius:1rem;border-bottom-left-radius:1rem;border-bottom-right-radius:1rem}}.button-group.even-2 li{margin:0 -2px;display:inline-block;width:50%}.button-group.even-2 li>button,.button-group.even-2 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-2 li:first-child button,.button-group.even-2 li:first-child .button{border-left:0}.button-group.even-2 li button,.button-group.even-2 li .button{width:100%}.button-group.even-3 li{margin:0 -2px;display:inline-block;width:33.3333333333%}.button-group.even-3 li>button,.button-group.even-3 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-3 li:first-child button,.button-group.even-3 li:first-child .button{border-left:0}.button-group.even-3 li button,.button-group.even-3 li .button{width:100%}.button-group.even-4 li{margin:0 -2px;display:inline-block;width:25%}.button-group.even-4 li>button,.button-group.even-4 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-4 li:first-child button,.button-group.even-4 li:first-child .button{border-left:0}.button-group.even-4 li button,.button-group.even-4 li .button{width:100%}.button-group.even-5 li{margin:0 -2px;display:inline-block;width:20%}.button-group.even-5 li>button,.button-group.even-5 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-5 li:first-child button,.button-group.even-5 li:first-child .button{border-left:0}.button-group.even-5 li button,.button-group.even-5 li .button{width:100%}.button-group.even-6 li{margin:0 -2px;display:inline-block;width:16.6666666667%}.button-group.even-6 li>button,.button-group.even-6 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-6 li:first-child button,.button-group.even-6 li:first-child .button{border-left:0}.button-group.even-6 li button,.button-group.even-6 li .button{width:100%}.button-group.even-7 li{margin:0 -2px;display:inline-block;width:14.2857142857%}.button-group.even-7 li>button,.button-group.even-7 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-7 li:first-child button,.button-group.even-7 li:first-child .button{border-left:0}.button-group.even-7 li button,.button-group.even-7 li .button{width:100%}.button-group.even-8 li{margin:0 -2px;display:inline-block;width:12.5%}.button-group.even-8 li>button,.button-group.even-8 li .button{border-left:1px solid;border-color:rgba(255,255,255,.5)}.button-group.even-8 li:first-child button,.button-group.even-8 li:first-child .button{border-left:0}.button-group.even-8 li button,.button-group.even-8 li .button{width:100%}.button-bar:before,.button-bar:after{content:" ";display:table}.button-bar:after{clear:both}.button-bar .button-group{float:left;margin-right:.625rem}.button-bar .button-group div{overflow:hidden}.clearing-thumbs,[data-clearing]{margin-bottom:0;margin-left:0;list-style:none}.clearing-thumbs:before,.clearing-thumbs:after,[data-clearing]:before,[data-clearing]:after{content:" ";display:table}.clearing-thumbs:after,[data-clearing]:after{clear:both}.clearing-thumbs li,[data-clearing] li{float:left;margin-right:10px}.clearing-thumbs[class*=block-grid-] li,[data-clearing][class*=block-grid-] li{margin-right:0}.clearing-blackout{background:#333;position:fixed;width:100%;height:100%;top:0;left:0;z-index:998}.clearing-blackout .clearing-close{display:block}.clearing-container{position:relative;z-index:998;height:100%;overflow:hidden;margin:0}.clearing-touch-label{position:absolute;top:50%;left:50%;color:#aaa;font-size:.6em}.visible-img{height:95%;position:relative}.visible-img img{position:absolute;left:50%;top:50%;margin-left:-50%;max-height:100%;max-width:100%}.clearing-caption{color:#ccc;font-size:.875em;line-height:1.3;margin-bottom:0;text-align:center;bottom:0;background:#333;width:100%;padding:10px 30px 20px;position:absolute;left:0}.clearing-close{z-index:999;padding-left:20px;padding-top:10px;font-size:30px;line-height:1;color:#ccc;display:none}.clearing-close:hover,.clearing-close:focus{color:#ccc}.clearing-assembled .clearing-container{height:100%}.clearing-assembled .clearing-container .carousel>ul{display:none}.clearing-feature li{display:none}.clearing-feature li.clearing-featured-img{display:block}@media only screen and (min-width:40.063em){.clearing-main-prev,.clearing-main-next{position:absolute;height:100%;width:40px;top:0}.clearing-main-prev>span,.clearing-main-next>span{position:absolute;top:50%;display:block;width:0;height:0;border:solid 12px}.clearing-main-prev>span:hover,.clearing-main-next>span:hover{opacity:.8}.clearing-main-prev{left:0}.clearing-main-prev>span{left:5px;border-color:rgba(0,0,0,0);border-right-color:#ccc}.clearing-main-next{right:0}.clearing-main-next>span{border-color:rgba(0,0,0,0);border-left-color:#ccc}.clearing-main-prev.disabled,.clearing-main-next.disabled{opacity:.3}.clearing-assembled .clearing-container .carousel{background:rgba(51,51,51,.8);height:120px;margin-top:10px;text-align:center}.clearing-assembled .clearing-container .carousel>ul{display:inline-block;z-index:999;height:100%;position:relative;float:none}.clearing-assembled .clearing-container .carousel>ul li{display:block;width:120px;min-height:inherit;float:left;overflow:hidden;margin-right:0;padding:0;position:relative;cursor:pointer;opacity:.4;clear:none}.clearing-assembled .clearing-container .carousel>ul li.fix-height img{height:100%;max-width:none}.clearing-assembled .clearing-container .carousel>ul li a.th{border:none;box-shadow:none;display:block}.clearing-assembled .clearing-container .carousel>ul li img{cursor:pointer !important;width:100% !important}.clearing-assembled .clearing-container .carousel>ul li.visible{opacity:1}.clearing-assembled .clearing-container .carousel>ul li:hover{opacity:.8}.clearing-assembled .clearing-container .visible-img{background:#333;overflow:hidden;height:85%}.clearing-close{position:absolute;top:10px;right:20px;padding-left:0;padding-top:0}}.f-dropdown{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;width:100%;max-height:none;height:auto;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;margin-top:2px;max-width:200px}.f-dropdown>*:first-child{margin-top:0}.f-dropdown>*:last-child{margin-bottom:0}.f-dropdown:before{content:"";display:block;width:0;height:0;border:inset 6px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) #fff rgba(0,0,0,0);border-bottom-style:solid;position:absolute;top:-12px;left:10px;z-index:89}.f-dropdown:after{content:"";display:block;width:0;height:0;border:inset 7px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) #ccc rgba(0,0,0,0);border-bottom-style:solid;position:absolute;top:-14px;left:9px;z-index:88}.f-dropdown.right:before{left:auto;right:10px}.f-dropdown.right:after{left:auto;right:9px}.f-dropdown.drop-right{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;width:100%;max-height:none;height:auto;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;margin-top:0;margin-left:2px;max-width:200px}.f-dropdown.drop-right>*:first-child{margin-top:0}.f-dropdown.drop-right>*:last-child{margin-bottom:0}.f-dropdown.drop-right:before{content:"";display:block;width:0;height:0;border:inset 6px;border-color:rgba(0,0,0,0) #fff rgba(0,0,0,0) rgba(0,0,0,0);border-right-style:solid;position:absolute;top:10px;left:-12px;z-index:89}.f-dropdown.drop-right:after{content:"";display:block;width:0;height:0;border:inset 7px;border-color:rgba(0,0,0,0) #ccc rgba(0,0,0,0) rgba(0,0,0,0);border-right-style:solid;position:absolute;top:9px;left:-14px;z-index:88}.f-dropdown.drop-left{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;width:100%;max-height:none;height:auto;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;margin-top:0;margin-left:-2px;max-width:200px}.f-dropdown.drop-left>*:first-child{margin-top:0}.f-dropdown.drop-left>*:last-child{margin-bottom:0}.f-dropdown.drop-left:before{content:"";display:block;width:0;height:0;border:inset 6px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0) #fff;border-left-style:solid;position:absolute;top:10px;right:-12px;left:auto;z-index:89}.f-dropdown.drop-left:after{content:"";display:block;width:0;height:0;border:inset 7px;border-color:rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0) #ccc;border-left-style:solid;position:absolute;top:9px;right:-14px;left:auto;z-index:88}.f-dropdown.drop-top{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;width:100%;max-height:none;height:auto;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;margin-top:-2px;margin-left:0;max-width:200px}.f-dropdown.drop-top>*:first-child{margin-top:0}.f-dropdown.drop-top>*:last-child{margin-bottom:0}.f-dropdown.drop-top:before{content:"";display:block;width:0;height:0;border:inset 6px;border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0);border-top-style:solid;position:absolute;top:auto;bottom:-12px;left:10px;right:auto;z-index:89}.f-dropdown.drop-top:after{content:"";display:block;width:0;height:0;border:inset 7px;border-color:#ccc rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0);border-top-style:solid;position:absolute;top:auto;bottom:-14px;left:9px;right:auto;z-index:88}.f-dropdown li{font-size:.875rem;cursor:pointer;line-height:1.125rem;margin:0}.f-dropdown li:hover,.f-dropdown li:focus{background:#eee}.f-dropdown li.radius{border-radius:3px}.f-dropdown li a{display:block;padding:.5rem;color:#555}.f-dropdown.content{position:absolute;left:-9999px;list-style:none;margin-left:0;outline:none;padding:1.25rem;width:100%;height:auto;max-height:none;background:#fff;border:solid 1px #ccc;font-size:.875rem;z-index:89;max-width:200px}.f-dropdown.content>*:first-child{margin-top:0}.f-dropdown.content>*:last-child{margin-bottom:0}.f-dropdown.tiny{max-width:200px}.f-dropdown.small{max-width:300px}.f-dropdown.medium{max-width:500px}.f-dropdown.large{max-width:800px}.f-dropdown.mega{width:100% !important;max-width:100% !important}.f-dropdown.mega.open{left:0 !important}.dropdown.button,button.dropdown{position:relative;outline:none;padding-right:3.5625rem}.dropdown.button::after,button.dropdown::after{position:absolute;content:"";width:0;height:0;display:block;border-style:solid;border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0);top:50%}.dropdown.button::after,button.dropdown::after{border-width:.375rem;right:1.40625rem;margin-top:-0.15625rem}.dropdown.button::after,button.dropdown::after{border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.dropdown.button.tiny,button.dropdown.tiny{padding-right:2.625rem}.dropdown.button.tiny:after,button.dropdown.tiny:after{border-width:.375rem;right:1.125rem;margin-top:-0.125rem}.dropdown.button.tiny::after,button.dropdown.tiny::after{border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.dropdown.button.small,button.dropdown.small{padding-right:3.0625rem}.dropdown.button.small::after,button.dropdown.small::after{border-width:.4375rem;right:1.3125rem;margin-top:-0.15625rem}.dropdown.button.small::after,button.dropdown.small::after{border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.dropdown.button.large,button.dropdown.large{padding-right:3.625rem}.dropdown.button.large::after,button.dropdown.large::after{border-width:.3125rem;right:1.71875rem;margin-top:-0.15625rem}.dropdown.button.large::after,button.dropdown.large::after{border-color:#fff rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.dropdown.button.secondary:after,button.dropdown.secondary:after{border-color:#333 rgba(0,0,0,0) rgba(0,0,0,0) rgba(0,0,0,0)}.flex-video{position:relative;padding-top:1.5625rem;padding-bottom:67.5%;height:0;margin-bottom:1rem;overflow:hidden}.flex-video.widescreen{padding-bottom:56.34%}.flex-video.vimeo{padding-top:0}.flex-video iframe,.flex-video object,.flex-video embed,.flex-video video{position:absolute;top:0;left:0;width:100%;height:100%}.inline-list{margin:0 auto 1.0625rem auto;margin-left:-1.375rem;margin-right:0;padding:0;list-style:none;overflow:hidden}.inline-list>li{list-style:none;float:left;margin-left:1.375rem;display:block}.inline-list>li>*{display:block}.keystroke,kbd{background-color:#ededed;border-color:#ddd;color:#222;border-style:solid;border-width:1px;margin:0;font-family:"Consolas","Menlo","Courier",monospace;font-size:inherit;padding:.125rem .25rem 0;border-radius:3px}.panel{border-style:solid;border-width:1px;border-color:#cbcbcb;margin-bottom:1.25rem;padding:1.25rem;background:#e4e4e4;color:#333}.panel>:first-child{margin-top:0}.panel>:last-child{margin-bottom:0}.panel h1,.panel h2,.panel h3,.panel h4,.panel h5,.panel h6,.panel p,.panel li,.panel dl{color:#333}.panel h1,.panel h2,.panel h3,.panel h4,.panel h5,.panel h6{line-height:1;margin-bottom:.625rem}.panel h1.subheader,.panel h2.subheader,.panel h3.subheader,.panel h4.subheader,.panel h5.subheader,.panel h6.subheader{line-height:1.4}.panel.callout{border-style:solid;border-width:1px;border-color:#cedce4;margin-bottom:1.25rem;padding:1.25rem;background:#f1f5f7;color:#333}.panel.callout>:first-child{margin-top:0}.panel.callout>:last-child{margin-bottom:0}.panel.callout h1,.panel.callout h2,.panel.callout h3,.panel.callout h4,.panel.callout h5,.panel.callout h6,.panel.callout p,.panel.callout li,.panel.callout dl{color:#333}.panel.callout h1,.panel.callout h2,.panel.callout h3,.panel.callout h4,.panel.callout h5,.panel.callout h6{line-height:1;margin-bottom:.625rem}.panel.callout h1.subheader,.panel.callout h2.subheader,.panel.callout h3.subheader,.panel.callout h4.subheader,.panel.callout h5.subheader,.panel.callout h6.subheader{line-height:1.4}.panel.callout a:not(.button){color:#334d5c}.panel.callout a:not(.button):hover,.panel.callout a:not(.button):focus{color:#2c424f}.panel.radius{border-radius:3px}.reveal-modal-bg{position:absolute;top:0;bottom:0;left:0;right:0;background:#000;background:rgba(0,0,0,.45);z-index:1004;display:none;left:0}.reveal-modal,dialog{visibility:hidden;display:none;position:absolute;z-index:1005;width:100vw;top:0;border-radius:3px;left:0;background-color:#fff;padding:1.25rem;border:solid 1px #666;box-shadow:0 0 10px rgba(0,0,0,.4);padding:1.875rem}@media only screen and (max-width: 40em){.reveal-modal,dialog{min-height:100vh}}.reveal-modal .column,dialog .column,.reveal-modal .columns,dialog .columns{min-width:0}.reveal-modal>:first-child,dialog>:first-child{margin-top:0}.reveal-modal>:last-child,dialog>:last-child{margin-bottom:0}@media only screen and (min-width:40.063em){.reveal-modal,dialog{width:80%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal,dialog{top:15.625rem}}.reveal-modal.radius,dialog.radius{border-radius:3px}.reveal-modal.round,dialog.round{border-radius:1000px}.reveal-modal.collapse,dialog.collapse{padding:0}@media only screen and (min-width:40.063em){.reveal-modal.tiny,dialog.tiny{width:30%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal.small,dialog.small{width:40%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal.medium,dialog.medium{width:60%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal.large,dialog.large{width:70%;max-width:93.75rem;left:0;right:0;margin:0 auto}}@media only screen and (min-width:40.063em){.reveal-modal.xlarge,dialog.xlarge{width:95%;max-width:93.75rem;left:0;right:0;margin:0 auto}}.reveal-modal.full,dialog.full{top:0;left:0;height:100%;height:100vh;min-height:100vh;max-width:none !important;margin-left:0 !important}@media only screen and (min-width:40.063em){.reveal-modal.full,dialog.full{width:100vw;max-width:93.75rem;left:0;right:0;margin:0 auto}}.reveal-modal .close-reveal-modal,dialog .close-reveal-modal{font-size:2.5rem;line-height:1;position:absolute;top:.625rem;right:1.375rem;color:#aaa;font-weight:bold;cursor:pointer}dialog{display:none}dialog::backdrop,dialog+.backdrop{position:absolute;top:0;bottom:0;left:0;right:0;background:#000;background:rgba(0,0,0,.45);z-index:auto;display:none;left:0}dialog[open]{display:block}@media print{dialog,.reveal-modal{display:none;background:#fff !important}}.side-nav{display:block;margin:0;padding:0 0 0 0;list-style-type:none;list-style-position:outside;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif}.side-nav li{margin:0 0 0 0;font-size:1rem;font-weight:normal}.side-nav li a:not(.button){display:block;color:#334d5c;margin:0;padding:.4375rem .875rem}.side-nav li a:not(.button):hover,.side-nav li a:not(.button):focus{background:rgba(0,0,0,.025);color:#1f2e37}.side-nav li.active>a:first-child:not(.button){color:#1f2e37;font-weight:normal;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif}.side-nav li.divider{border-top:1px solid;height:0;padding:0;list-style:none;border-top-color:#e4e4e4}.side-nav li.heading{color:#334d5c;font-size:1rem;font-weight:bold;text-transform:uppercase}.sub-nav{display:block;width:auto;overflow:hidden;margin:-0.25rem 0 1.125rem;padding-top:.25rem}.sub-nav dt{text-transform:uppercase}.sub-nav dt,.sub-nav dd,.sub-nav li{float:left;display:inline;margin-left:1rem;margin-bottom:0;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-weight:normal;font-size:.875rem;color:#999}.sub-nav dt a,.sub-nav dd a,.sub-nav li a{text-decoration:none;color:#999;padding:.1875rem 1rem}.sub-nav dt a:hover,.sub-nav dd a:hover,.sub-nav li a:hover{color:#737373}.sub-nav dt.active a,.sub-nav dd.active a,.sub-nav li.active a{border-radius:3px;font-weight:normal;background:#334d5c;padding:.1875rem 1rem;cursor:default;color:#fff}.sub-nav dt.active a:hover,.sub-nav dd.active a:hover,.sub-nav li.active a:hover{background:#2c424f}table{background:#fff;margin-bottom:1.25rem;border:solid 1px #ddd;table-layout:auto}table caption{background:rgba(0,0,0,0);color:#222;font-size:1rem;font-weight:bold}table thead{background:#d7d7d7}table thead tr th,table thead tr td{padding:.5rem .625rem .625rem;font-size:.875rem;font-weight:bold;color:#222}table tfoot{background:#d7d7d7}table tfoot tr th,table tfoot tr td{padding:.5rem .625rem .625rem;font-size:.875rem;font-weight:bold;color:#222}table tr th,table tr td{padding:.5625rem .625rem;font-size:.875rem;color:#222;text-align:left}table tr.even,table tr.alt,table tr:nth-of-type(even){background:#e4e4e4}table thead tr th,table tfoot tr th,table tfoot tr td,table tbody tr th,table tbody tr td,table tr td{display:table-cell;line-height:1.125rem}.th{line-height:0;display:inline-block;border:solid 4px #fff;max-width:100%;box-shadow:0 0 0 1px rgba(0,0,0,.2);transition:all 200ms ease-out}.th:hover,.th:focus{box-shadow:0 0 6px 1px rgba(51,77,92,.5)}.th.radius{border-radius:3px}.text-left{text-align:left !important}.text-right{text-align:right !important}.text-center{text-align:center !important}.text-justify{text-align:justify !important}@media only screen and (max-width: 40em){.small-only-text-left{text-align:left !important}.small-only-text-right{text-align:right !important}.small-only-text-center{text-align:center !important}.small-only-text-justify{text-align:justify !important}}@media only screen{.small-text-left{text-align:left !important}.small-text-right{text-align:right !important}.small-text-center{text-align:center !important}.small-text-justify{text-align:justify !important}}@media only screen and (min-width:40.063em)and (max-width:64em){.medium-only-text-left{text-align:left !important}.medium-only-text-right{text-align:right !important}.medium-only-text-center{text-align:center !important}.medium-only-text-justify{text-align:justify !important}}@media only screen and (min-width:40.063em){.medium-text-left{text-align:left !important}.medium-text-right{text-align:right !important}.medium-text-center{text-align:center !important}.medium-text-justify{text-align:justify !important}}@media only screen and (min-width:64.063em)and (max-width:90em){.large-only-text-left{text-align:left !important}.large-only-text-right{text-align:right !important}.large-only-text-center{text-align:center !important}.large-only-text-justify{text-align:justify !important}}@media only screen and (min-width:64.063em){.large-text-left{text-align:left !important}.large-text-right{text-align:right !important}.large-text-center{text-align:center !important}.large-text-justify{text-align:justify !important}}@media only screen and (min-width:90.063em)and (max-width:120em){.xlarge-only-text-left{text-align:left !important}.xlarge-only-text-right{text-align:right !important}.xlarge-only-text-center{text-align:center !important}.xlarge-only-text-justify{text-align:justify !important}}@media only screen and (min-width:90.063em){.xlarge-text-left{text-align:left !important}.xlarge-text-right{text-align:right !important}.xlarge-text-center{text-align:center !important}.xlarge-text-justify{text-align:justify !important}}@media only screen and (min-width:120.063em)and (max-width:99999999em){.xxlarge-only-text-left{text-align:left !important}.xxlarge-only-text-right{text-align:right !important}.xxlarge-only-text-center{text-align:center !important}.xxlarge-only-text-justify{text-align:justify !important}}@media only screen and (min-width:120.063em){.xxlarge-text-left{text-align:left !important}.xxlarge-text-right{text-align:right !important}.xxlarge-text-center{text-align:center !important}.xxlarge-text-justify{text-align:justify !important}}div,dl,dt,dd,ul,ol,li,h1,h2,h3,h4,h5,h6,pre,form,p,blockquote,th,td{margin:0;padding:0}a{color:#334d5c;text-decoration:none;line-height:inherit}a:hover,a:focus{color:#2c424f}a img{border:none}p{font-family:inherit;font-weight:normal;font-size:1rem;line-height:1.6;margin-bottom:1.25rem;text-rendering:optimizeLegibility}p.lead{font-size:1.21875rem;line-height:1.6}p aside{font-size:.875rem;line-height:1.35;font-style:italic}h1,h2,h3,h4,h5,h6{font-family:"Volkhov",Georgia,Times,serif;font-weight:normal;font-style:normal;color:#222;text-rendering:optimizeLegibility;margin-top:.2rem;margin-bottom:.5rem;line-height:1.4}h1 small,h2 small,h3 small,h4 small,h5 small,h6 small{font-size:60%;color:#6f6f6f;line-height:0}h1{font-size:2.125rem}h2{font-size:1.6875rem}h3{font-size:1.375rem}h4{font-size:1.125rem}h5{font-size:1.125rem}h6{font-size:1rem}.subheader{line-height:1.4;color:#6f6f6f;font-weight:normal;margin-top:.2rem;margin-bottom:.5rem}hr{border:solid #cbcbcb;border-width:1px 0 0;clear:both;margin:1.25rem 0 1.1875rem;height:0}em,i{font-style:italic;line-height:inherit}strong,b{font-weight:bold;line-height:inherit}small{font-size:60%;line-height:inherit}code{font-family:"Lucida Console",Monaco,monospace;font-weight:normal;color:#333;background-color:#e3f1c7;border-width:0px;border-style:solid;border-color:#d1e8a4;padding:.125rem .3125rem .0625rem}ul,ol,dl{font-size:1rem;line-height:1.6;margin-bottom:1.25rem;list-style-position:outside;font-family:inherit}ul{margin-left:1.3rem}ul.no-bullet{margin-left:0}ul.no-bullet li ul,ul.no-bullet li ol{margin-left:1.25rem;margin-bottom:0;list-style:none}ul li ul,ul li ol{margin-left:1.25rem;margin-bottom:0}ul.square li ul,ul.circle li ul,ul.disc li ul{list-style:inherit}ul.square{list-style-type:square;margin-left:1.3rem}ul.circle{list-style-type:circle;margin-left:1.3rem}ul.disc{list-style-type:disc;margin-left:1.3rem}ul.no-bullet{list-style:none}ol{margin-left:1.4rem}ol li ul,ol li ol{margin-left:1.25rem;margin-bottom:0}dl dt{margin-bottom:.3rem;font-weight:bold}dl dd{margin-bottom:.75rem}abbr,acronym{text-transform:uppercase;font-size:90%;color:#111;cursor:help}abbr{text-transform:none}abbr[title]{border-bottom:1px dotted #ddd}blockquote{margin:0 0 1.25rem;padding:.5625rem 1.25rem 0 1.1875rem;border-left:1px solid #ddd}blockquote cite{display:block;font-size:.8125rem;color:#555}blockquote cite:before{content:"— "}blockquote cite a,blockquote cite a:visited{color:#555}blockquote,blockquote p{line-height:1.6;color:#6f6f6f}.vcard{display:inline-block;margin:0 0 1.25rem 0;border:1px solid #ddd;padding:.625rem .75rem}.vcard li{margin:0;display:block}.vcard .fn{font-weight:bold;font-size:.9375rem}.vevent .summary{font-weight:bold}.vevent abbr{cursor:default;text-decoration:none;font-weight:bold;border:none;padding:0 .0625rem}@media only screen and (min-width:40.063em){h1,h2,h3,h4,h5,h6{line-height:1.4}h1{font-size:2.75rem}h2{font-size:2.3125rem}h3{font-size:1.6875rem}h4{font-size:1.4375rem}h5{font-size:1.125rem}h6{font-size:1rem}}.print-only{display:none !important}@media print{*{background:rgba(0,0,0,0) !important;color:#000 !important;box-shadow:none !important;text-shadow:none !important}a,a:visited{text-decoration:underline}a[href]:after{content:" (" attr(href) ")"}abbr[title]:after{content:" (" attr(title) ")"}.ir a:after,a[href^="javascript:"]:after,a[href^="#"]:after{content:""}pre,blockquote{border:1px solid #999;page-break-inside:avoid}thead{display:table-header-group}tr,img{page-break-inside:avoid}img{max-width:100% !important}@page{margin:.5cm}p,h2,h3{orphans:3;widows:3}h2,h3{page-break-after:avoid}.hide-on-print{display:none !important}.print-only{display:block !important}.hide-for-print{display:none !important}.show-for-print{display:inherit !important}}@media only screen{.show-for-small-only,.show-for-small-up,.show-for-small,.show-for-small-down,.hide-for-medium-only,.hide-for-medium-up,.hide-for-medium,.show-for-medium-down,.hide-for-large-only,.hide-for-large-up,.hide-for-large,.show-for-large-down,.hide-for-xlarge-only,.hide-for-xlarge-up,.hide-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.hide-for-small-only,.hide-for-small-up,.hide-for-small,.hide-for-small-down,.show-for-medium-only,.show-for-medium-up,.show-for-medium,.hide-for-medium-down,.show-for-large-only,.show-for-large-up,.show-for-large,.hide-for-large-down,.show-for-xlarge-only,.show-for-xlarge-up,.show-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.visible-for-small-only,.visible-for-small-up,.visible-for-small,.visible-for-small-down,.hidden-for-medium-only,.hidden-for-medium-up,.hidden-for-medium,.visible-for-medium-down,.hidden-for-large-only,.hidden-for-large-up,.hidden-for-large,.visible-for-large-down,.hidden-for-xlarge-only,.hidden-for-xlarge-up,.hidden-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.hidden-for-small-only,.hidden-for-small-up,.hidden-for-small,.hidden-for-small-down,.visible-for-medium-only,.visible-for-medium-up,.visible-for-medium,.hidden-for-medium-down,.visible-for-large-only,.visible-for-large-up,.visible-for-large,.hidden-for-large-down,.visible-for-xlarge-only,.visible-for-xlarge-up,.visible-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.show-for-small-only,table.show-for-small-up,table.show-for-small,table.show-for-small-down,table.hide-for-medium-only,table.hide-for-medium-up,table.hide-for-medium,table.show-for-medium-down,table.hide-for-large-only,table.hide-for-large-up,table.hide-for-large,table.show-for-large-down,table.hide-for-xlarge-only,table.hide-for-xlarge-up,table.hide-for-xlarge,table.show-for-xlarge-down,table.hide-for-xxlarge-only,table.hide-for-xxlarge-up,table.hide-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.show-for-small-only,thead.show-for-small-up,thead.show-for-small,thead.show-for-small-down,thead.hide-for-medium-only,thead.hide-for-medium-up,thead.hide-for-medium,thead.show-for-medium-down,thead.hide-for-large-only,thead.hide-for-large-up,thead.hide-for-large,thead.show-for-large-down,thead.hide-for-xlarge-only,thead.hide-for-xlarge-up,thead.hide-for-xlarge,thead.show-for-xlarge-down,thead.hide-for-xxlarge-only,thead.hide-for-xxlarge-up,thead.hide-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.show-for-small-only,tbody.show-for-small-up,tbody.show-for-small,tbody.show-for-small-down,tbody.hide-for-medium-only,tbody.hide-for-medium-up,tbody.hide-for-medium,tbody.show-for-medium-down,tbody.hide-for-large-only,tbody.hide-for-large-up,tbody.hide-for-large,tbody.show-for-large-down,tbody.hide-for-xlarge-only,tbody.hide-for-xlarge-up,tbody.hide-for-xlarge,tbody.show-for-xlarge-down,tbody.hide-for-xxlarge-only,tbody.hide-for-xxlarge-up,tbody.hide-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.show-for-small-only,tr.show-for-small-up,tr.show-for-small,tr.show-for-small-down,tr.hide-for-medium-only,tr.hide-for-medium-up,tr.hide-for-medium,tr.show-for-medium-down,tr.hide-for-large-only,tr.hide-for-large-up,tr.hide-for-large,tr.show-for-large-down,tr.hide-for-xlarge-only,tr.hide-for-xlarge-up,tr.hide-for-xlarge,tr.show-for-xlarge-down,tr.hide-for-xxlarge-only,tr.hide-for-xxlarge-up,tr.hide-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.show-for-small-only,td.show-for-small-only,th.show-for-small-up,td.show-for-small-up,th.show-for-small,td.show-for-small,th.show-for-small-down,td.show-for-small-down,th.hide-for-medium-only,td.hide-for-medium-only,th.hide-for-medium-up,td.hide-for-medium-up,th.hide-for-medium,td.hide-for-medium,th.show-for-medium-down,td.show-for-medium-down,th.hide-for-large-only,td.hide-for-large-only,th.hide-for-large-up,td.hide-for-large-up,th.hide-for-large,td.hide-for-large,th.show-for-large-down,td.show-for-large-down,th.hide-for-xlarge-only,td.hide-for-xlarge-only,th.hide-for-xlarge-up,td.hide-for-xlarge-up,th.hide-for-xlarge,td.hide-for-xlarge,th.show-for-xlarge-down,td.show-for-xlarge-down,th.hide-for-xxlarge-only,td.hide-for-xxlarge-only,th.hide-for-xxlarge-up,td.hide-for-xxlarge-up,th.hide-for-xxlarge,td.hide-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}@media only screen and (min-width:40.063em){.hide-for-small-only,.show-for-small-up,.hide-for-small,.hide-for-small-down,.show-for-medium-only,.show-for-medium-up,.show-for-medium,.show-for-medium-down,.hide-for-large-only,.hide-for-large-up,.hide-for-large,.show-for-large-down,.hide-for-xlarge-only,.hide-for-xlarge-up,.hide-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.show-for-small-only,.hide-for-small-up,.show-for-small,.show-for-small-down,.hide-for-medium-only,.hide-for-medium-up,.hide-for-medium,.hide-for-medium-down,.show-for-large-only,.show-for-large-up,.show-for-large,.hide-for-large-down,.show-for-xlarge-only,.show-for-xlarge-up,.show-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.hidden-for-small-only,.visible-for-small-up,.hidden-for-small,.hidden-for-small-down,.visible-for-medium-only,.visible-for-medium-up,.visible-for-medium,.visible-for-medium-down,.hidden-for-large-only,.hidden-for-large-up,.hidden-for-large,.visible-for-large-down,.hidden-for-xlarge-only,.hidden-for-xlarge-up,.hidden-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.visible-for-small-only,.hidden-for-small-up,.visible-for-small,.visible-for-small-down,.hidden-for-medium-only,.hidden-for-medium-up,.hidden-for-medium,.hidden-for-medium-down,.visible-for-large-only,.visible-for-large-up,.visible-for-large,.hidden-for-large-down,.visible-for-xlarge-only,.visible-for-xlarge-up,.visible-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.hide-for-small-only,table.show-for-small-up,table.hide-for-small,table.hide-for-small-down,table.show-for-medium-only,table.show-for-medium-up,table.show-for-medium,table.show-for-medium-down,table.hide-for-large-only,table.hide-for-large-up,table.hide-for-large,table.show-for-large-down,table.hide-for-xlarge-only,table.hide-for-xlarge-up,table.hide-for-xlarge,table.show-for-xlarge-down,table.hide-for-xxlarge-only,table.hide-for-xxlarge-up,table.hide-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.hide-for-small-only,thead.show-for-small-up,thead.hide-for-small,thead.hide-for-small-down,thead.show-for-medium-only,thead.show-for-medium-up,thead.show-for-medium,thead.show-for-medium-down,thead.hide-for-large-only,thead.hide-for-large-up,thead.hide-for-large,thead.show-for-large-down,thead.hide-for-xlarge-only,thead.hide-for-xlarge-up,thead.hide-for-xlarge,thead.show-for-xlarge-down,thead.hide-for-xxlarge-only,thead.hide-for-xxlarge-up,thead.hide-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.hide-for-small-only,tbody.show-for-small-up,tbody.hide-for-small,tbody.hide-for-small-down,tbody.show-for-medium-only,tbody.show-for-medium-up,tbody.show-for-medium,tbody.show-for-medium-down,tbody.hide-for-large-only,tbody.hide-for-large-up,tbody.hide-for-large,tbody.show-for-large-down,tbody.hide-for-xlarge-only,tbody.hide-for-xlarge-up,tbody.hide-for-xlarge,tbody.show-for-xlarge-down,tbody.hide-for-xxlarge-only,tbody.hide-for-xxlarge-up,tbody.hide-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.hide-for-small-only,tr.show-for-small-up,tr.hide-for-small,tr.hide-for-small-down,tr.show-for-medium-only,tr.show-for-medium-up,tr.show-for-medium,tr.show-for-medium-down,tr.hide-for-large-only,tr.hide-for-large-up,tr.hide-for-large,tr.show-for-large-down,tr.hide-for-xlarge-only,tr.hide-for-xlarge-up,tr.hide-for-xlarge,tr.show-for-xlarge-down,tr.hide-for-xxlarge-only,tr.hide-for-xxlarge-up,tr.hide-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.hide-for-small-only,td.hide-for-small-only,th.show-for-small-up,td.show-for-small-up,th.hide-for-small,td.hide-for-small,th.hide-for-small-down,td.hide-for-small-down,th.show-for-medium-only,td.show-for-medium-only,th.show-for-medium-up,td.show-for-medium-up,th.show-for-medium,td.show-for-medium,th.show-for-medium-down,td.show-for-medium-down,th.hide-for-large-only,td.hide-for-large-only,th.hide-for-large-up,td.hide-for-large-up,th.hide-for-large,td.hide-for-large,th.show-for-large-down,td.show-for-large-down,th.hide-for-xlarge-only,td.hide-for-xlarge-only,th.hide-for-xlarge-up,td.hide-for-xlarge-up,th.hide-for-xlarge,td.hide-for-xlarge,th.show-for-xlarge-down,td.show-for-xlarge-down,th.hide-for-xxlarge-only,td.hide-for-xxlarge-only,th.hide-for-xxlarge-up,td.hide-for-xxlarge-up,th.hide-for-xxlarge,td.hide-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}@media only screen and (min-width:64.063em){.hide-for-small-only,.show-for-small-up,.hide-for-small,.hide-for-small-down,.hide-for-medium-only,.show-for-medium-up,.hide-for-medium,.hide-for-medium-down,.show-for-large-only,.show-for-large-up,.show-for-large,.show-for-large-down,.hide-for-xlarge-only,.hide-for-xlarge-up,.hide-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.show-for-small-only,.hide-for-small-up,.show-for-small,.show-for-small-down,.show-for-medium-only,.hide-for-medium-up,.show-for-medium,.show-for-medium-down,.hide-for-large-only,.hide-for-large-up,.hide-for-large,.hide-for-large-down,.show-for-xlarge-only,.show-for-xlarge-up,.show-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.hidden-for-small-only,.visible-for-small-up,.hidden-for-small,.hidden-for-small-down,.hidden-for-medium-only,.visible-for-medium-up,.hidden-for-medium,.hidden-for-medium-down,.visible-for-large-only,.visible-for-large-up,.visible-for-large,.visible-for-large-down,.hidden-for-xlarge-only,.hidden-for-xlarge-up,.hidden-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.visible-for-small-only,.hidden-for-small-up,.visible-for-small,.visible-for-small-down,.visible-for-medium-only,.hidden-for-medium-up,.visible-for-medium,.visible-for-medium-down,.hidden-for-large-only,.hidden-for-large-up,.hidden-for-large,.hidden-for-large-down,.visible-for-xlarge-only,.visible-for-xlarge-up,.visible-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.hide-for-small-only,table.show-for-small-up,table.hide-for-small,table.hide-for-small-down,table.hide-for-medium-only,table.show-for-medium-up,table.hide-for-medium,table.hide-for-medium-down,table.show-for-large-only,table.show-for-large-up,table.show-for-large,table.show-for-large-down,table.hide-for-xlarge-only,table.hide-for-xlarge-up,table.hide-for-xlarge,table.show-for-xlarge-down,table.hide-for-xxlarge-only,table.hide-for-xxlarge-up,table.hide-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.hide-for-small-only,thead.show-for-small-up,thead.hide-for-small,thead.hide-for-small-down,thead.hide-for-medium-only,thead.show-for-medium-up,thead.hide-for-medium,thead.hide-for-medium-down,thead.show-for-large-only,thead.show-for-large-up,thead.show-for-large,thead.show-for-large-down,thead.hide-for-xlarge-only,thead.hide-for-xlarge-up,thead.hide-for-xlarge,thead.show-for-xlarge-down,thead.hide-for-xxlarge-only,thead.hide-for-xxlarge-up,thead.hide-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.hide-for-small-only,tbody.show-for-small-up,tbody.hide-for-small,tbody.hide-for-small-down,tbody.hide-for-medium-only,tbody.show-for-medium-up,tbody.hide-for-medium,tbody.hide-for-medium-down,tbody.show-for-large-only,tbody.show-for-large-up,tbody.show-for-large,tbody.show-for-large-down,tbody.hide-for-xlarge-only,tbody.hide-for-xlarge-up,tbody.hide-for-xlarge,tbody.show-for-xlarge-down,tbody.hide-for-xxlarge-only,tbody.hide-for-xxlarge-up,tbody.hide-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.hide-for-small-only,tr.show-for-small-up,tr.hide-for-small,tr.hide-for-small-down,tr.hide-for-medium-only,tr.show-for-medium-up,tr.hide-for-medium,tr.hide-for-medium-down,tr.show-for-large-only,tr.show-for-large-up,tr.show-for-large,tr.show-for-large-down,tr.hide-for-xlarge-only,tr.hide-for-xlarge-up,tr.hide-for-xlarge,tr.show-for-xlarge-down,tr.hide-for-xxlarge-only,tr.hide-for-xxlarge-up,tr.hide-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.hide-for-small-only,td.hide-for-small-only,th.show-for-small-up,td.show-for-small-up,th.hide-for-small,td.hide-for-small,th.hide-for-small-down,td.hide-for-small-down,th.hide-for-medium-only,td.hide-for-medium-only,th.show-for-medium-up,td.show-for-medium-up,th.hide-for-medium,td.hide-for-medium,th.hide-for-medium-down,td.hide-for-medium-down,th.show-for-large-only,td.show-for-large-only,th.show-for-large-up,td.show-for-large-up,th.show-for-large,td.show-for-large,th.show-for-large-down,td.show-for-large-down,th.hide-for-xlarge-only,td.hide-for-xlarge-only,th.hide-for-xlarge-up,td.hide-for-xlarge-up,th.hide-for-xlarge,td.hide-for-xlarge,th.show-for-xlarge-down,td.show-for-xlarge-down,th.hide-for-xxlarge-only,td.hide-for-xxlarge-only,th.hide-for-xxlarge-up,td.hide-for-xxlarge-up,th.hide-for-xxlarge,td.hide-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}@media only screen and (min-width:90.063em){.hide-for-small-only,.show-for-small-up,.hide-for-small,.hide-for-small-down,.hide-for-medium-only,.show-for-medium-up,.hide-for-medium,.hide-for-medium-down,.hide-for-large-only,.show-for-large-up,.hide-for-large,.hide-for-large-down,.show-for-xlarge-only,.show-for-xlarge-up,.show-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.show-for-small-only,.hide-for-small-up,.show-for-small,.show-for-small-down,.show-for-medium-only,.hide-for-medium-up,.show-for-medium,.show-for-medium-down,.show-for-large-only,.hide-for-large-up,.show-for-large,.show-for-large-down,.hide-for-xlarge-only,.hide-for-xlarge-up,.hide-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.hidden-for-small-only,.visible-for-small-up,.hidden-for-small,.hidden-for-small-down,.hidden-for-medium-only,.visible-for-medium-up,.hidden-for-medium,.hidden-for-medium-down,.hidden-for-large-only,.visible-for-large-up,.hidden-for-large,.hidden-for-large-down,.visible-for-xlarge-only,.visible-for-xlarge-up,.visible-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.visible-for-small-only,.hidden-for-small-up,.visible-for-small,.visible-for-small-down,.visible-for-medium-only,.hidden-for-medium-up,.visible-for-medium,.visible-for-medium-down,.visible-for-large-only,.hidden-for-large-up,.visible-for-large,.visible-for-large-down,.hidden-for-xlarge-only,.hidden-for-xlarge-up,.hidden-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.hide-for-small-only,table.show-for-small-up,table.hide-for-small,table.hide-for-small-down,table.hide-for-medium-only,table.show-for-medium-up,table.hide-for-medium,table.hide-for-medium-down,table.hide-for-large-only,table.show-for-large-up,table.hide-for-large,table.hide-for-large-down,table.show-for-xlarge-only,table.show-for-xlarge-up,table.show-for-xlarge,table.show-for-xlarge-down,table.hide-for-xxlarge-only,table.hide-for-xxlarge-up,table.hide-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.hide-for-small-only,thead.show-for-small-up,thead.hide-for-small,thead.hide-for-small-down,thead.hide-for-medium-only,thead.show-for-medium-up,thead.hide-for-medium,thead.hide-for-medium-down,thead.hide-for-large-only,thead.show-for-large-up,thead.hide-for-large,thead.hide-for-large-down,thead.show-for-xlarge-only,thead.show-for-xlarge-up,thead.show-for-xlarge,thead.show-for-xlarge-down,thead.hide-for-xxlarge-only,thead.hide-for-xxlarge-up,thead.hide-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.hide-for-small-only,tbody.show-for-small-up,tbody.hide-for-small,tbody.hide-for-small-down,tbody.hide-for-medium-only,tbody.show-for-medium-up,tbody.hide-for-medium,tbody.hide-for-medium-down,tbody.hide-for-large-only,tbody.show-for-large-up,tbody.hide-for-large,tbody.hide-for-large-down,tbody.show-for-xlarge-only,tbody.show-for-xlarge-up,tbody.show-for-xlarge,tbody.show-for-xlarge-down,tbody.hide-for-xxlarge-only,tbody.hide-for-xxlarge-up,tbody.hide-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.hide-for-small-only,tr.show-for-small-up,tr.hide-for-small,tr.hide-for-small-down,tr.hide-for-medium-only,tr.show-for-medium-up,tr.hide-for-medium,tr.hide-for-medium-down,tr.hide-for-large-only,tr.show-for-large-up,tr.hide-for-large,tr.hide-for-large-down,tr.show-for-xlarge-only,tr.show-for-xlarge-up,tr.show-for-xlarge,tr.show-for-xlarge-down,tr.hide-for-xxlarge-only,tr.hide-for-xxlarge-up,tr.hide-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.hide-for-small-only,td.hide-for-small-only,th.show-for-small-up,td.show-for-small-up,th.hide-for-small,td.hide-for-small,th.hide-for-small-down,td.hide-for-small-down,th.hide-for-medium-only,td.hide-for-medium-only,th.show-for-medium-up,td.show-for-medium-up,th.hide-for-medium,td.hide-for-medium,th.hide-for-medium-down,td.hide-for-medium-down,th.hide-for-large-only,td.hide-for-large-only,th.show-for-large-up,td.show-for-large-up,th.hide-for-large,td.hide-for-large,th.hide-for-large-down,td.hide-for-large-down,th.show-for-xlarge-only,td.show-for-xlarge-only,th.show-for-xlarge-up,td.show-for-xlarge-up,th.show-for-xlarge,td.show-for-xlarge,th.show-for-xlarge-down,td.show-for-xlarge-down,th.hide-for-xxlarge-only,td.hide-for-xxlarge-only,th.hide-for-xxlarge-up,td.hide-for-xxlarge-up,th.hide-for-xxlarge,td.hide-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}@media only screen and (min-width:120.063em){.hide-for-small-only,.show-for-small-up,.hide-for-small,.hide-for-small-down,.hide-for-medium-only,.show-for-medium-up,.hide-for-medium,.hide-for-medium-down,.hide-for-large-only,.show-for-large-up,.hide-for-large,.hide-for-large-down,.hide-for-xlarge-only,.show-for-xlarge-up,.hide-for-xlarge,.hide-for-xlarge-down,.show-for-xxlarge-only,.show-for-xxlarge-up,.show-for-xxlarge,.show-for-xxlarge-down{display:inherit !important}.show-for-small-only,.hide-for-small-up,.show-for-small,.show-for-small-down,.show-for-medium-only,.hide-for-medium-up,.show-for-medium,.show-for-medium-down,.show-for-large-only,.hide-for-large-up,.show-for-large,.show-for-large-down,.show-for-xlarge-only,.hide-for-xlarge-up,.show-for-xlarge,.show-for-xlarge-down,.hide-for-xxlarge-only,.hide-for-xxlarge-up,.hide-for-xxlarge,.hide-for-xxlarge-down{display:none !important}.hidden-for-small-only,.visible-for-small-up,.hidden-for-small,.hidden-for-small-down,.hidden-for-medium-only,.visible-for-medium-up,.hidden-for-medium,.hidden-for-medium-down,.hidden-for-large-only,.visible-for-large-up,.hidden-for-large,.hidden-for-large-down,.hidden-for-xlarge-only,.visible-for-xlarge-up,.hidden-for-xlarge,.hidden-for-xlarge-down,.visible-for-xxlarge-only,.visible-for-xxlarge-up,.visible-for-xxlarge,.visible-for-xxlarge-down{position:static !important;height:auto;width:auto;overflow:visible;clip:auto}.visible-for-small-only,.hidden-for-small-up,.visible-for-small,.visible-for-small-down,.visible-for-medium-only,.hidden-for-medium-up,.visible-for-medium,.visible-for-medium-down,.visible-for-large-only,.hidden-for-large-up,.visible-for-large,.visible-for-large-down,.visible-for-xlarge-only,.hidden-for-xlarge-up,.visible-for-xlarge,.visible-for-xlarge-down,.hidden-for-xxlarge-only,.hidden-for-xxlarge-up,.hidden-for-xxlarge,.hidden-for-xxlarge-down{position:absolute !important;height:1px;width:1px;overflow:hidden;clip:rect(1px, 1px, 1px, 1px)}table.hide-for-small-only,table.show-for-small-up,table.hide-for-small,table.hide-for-small-down,table.hide-for-medium-only,table.show-for-medium-up,table.hide-for-medium,table.hide-for-medium-down,table.hide-for-large-only,table.show-for-large-up,table.hide-for-large,table.hide-for-large-down,table.hide-for-xlarge-only,table.show-for-xlarge-up,table.hide-for-xlarge,table.hide-for-xlarge-down,table.show-for-xxlarge-only,table.show-for-xxlarge-up,table.show-for-xxlarge,table.show-for-xxlarge-down{display:table !important}thead.hide-for-small-only,thead.show-for-small-up,thead.hide-for-small,thead.hide-for-small-down,thead.hide-for-medium-only,thead.show-for-medium-up,thead.hide-for-medium,thead.hide-for-medium-down,thead.hide-for-large-only,thead.show-for-large-up,thead.hide-for-large,thead.hide-for-large-down,thead.hide-for-xlarge-only,thead.show-for-xlarge-up,thead.hide-for-xlarge,thead.hide-for-xlarge-down,thead.show-for-xxlarge-only,thead.show-for-xxlarge-up,thead.show-for-xxlarge,thead.show-for-xxlarge-down{display:table-header-group !important}tbody.hide-for-small-only,tbody.show-for-small-up,tbody.hide-for-small,tbody.hide-for-small-down,tbody.hide-for-medium-only,tbody.show-for-medium-up,tbody.hide-for-medium,tbody.hide-for-medium-down,tbody.hide-for-large-only,tbody.show-for-large-up,tbody.hide-for-large,tbody.hide-for-large-down,tbody.hide-for-xlarge-only,tbody.show-for-xlarge-up,tbody.hide-for-xlarge,tbody.hide-for-xlarge-down,tbody.show-for-xxlarge-only,tbody.show-for-xxlarge-up,tbody.show-for-xxlarge,tbody.show-for-xxlarge-down{display:table-row-group !important}tr.hide-for-small-only,tr.show-for-small-up,tr.hide-for-small,tr.hide-for-small-down,tr.hide-for-medium-only,tr.show-for-medium-up,tr.hide-for-medium,tr.hide-for-medium-down,tr.hide-for-large-only,tr.show-for-large-up,tr.hide-for-large,tr.hide-for-large-down,tr.hide-for-xlarge-only,tr.show-for-xlarge-up,tr.hide-for-xlarge,tr.hide-for-xlarge-down,tr.show-for-xxlarge-only,tr.show-for-xxlarge-up,tr.show-for-xxlarge,tr.show-for-xxlarge-down{display:table-row !important}th.hide-for-small-only,td.hide-for-small-only,th.show-for-small-up,td.show-for-small-up,th.hide-for-small,td.hide-for-small,th.hide-for-small-down,td.hide-for-small-down,th.hide-for-medium-only,td.hide-for-medium-only,th.show-for-medium-up,td.show-for-medium-up,th.hide-for-medium,td.hide-for-medium,th.hide-for-medium-down,td.hide-for-medium-down,th.hide-for-large-only,td.hide-for-large-only,th.show-for-large-up,td.show-for-large-up,th.hide-for-large,td.hide-for-large,th.hide-for-large-down,td.hide-for-large-down,th.hide-for-xlarge-only,td.hide-for-xlarge-only,th.show-for-xlarge-up,td.show-for-xlarge-up,th.hide-for-xlarge,td.hide-for-xlarge,th.hide-for-xlarge-down,td.hide-for-xlarge-down,th.show-for-xxlarge-only,td.show-for-xxlarge-only,th.show-for-xxlarge-up,td.show-for-xxlarge-up,th.show-for-xxlarge,td.show-for-xxlarge,th.show-for-xxlarge-down,td.show-for-xxlarge-down{display:table-cell !important}}.show-for-landscape,.hide-for-portrait{display:inherit !important}.hide-for-landscape,.show-for-portrait{display:none !important}table.hide-for-landscape,table.show-for-portrait{display:table !important}thead.hide-for-landscape,thead.show-for-portrait{display:table-header-group !important}tbody.hide-for-landscape,tbody.show-for-portrait{display:table-row-group !important}tr.hide-for-landscape,tr.show-for-portrait{display:table-row !important}td.hide-for-landscape,td.show-for-portrait,th.hide-for-landscape,th.show-for-portrait{display:table-cell !important}@media only screen and (orientation: landscape){.show-for-landscape,.hide-for-portrait{display:inherit !important}.hide-for-landscape,.show-for-portrait{display:none !important}table.show-for-landscape,table.hide-for-portrait{display:table !important}thead.show-for-landscape,thead.hide-for-portrait{display:table-header-group !important}tbody.show-for-landscape,tbody.hide-for-portrait{display:table-row-group !important}tr.show-for-landscape,tr.hide-for-portrait{display:table-row !important}td.show-for-landscape,td.hide-for-portrait,th.show-for-landscape,th.hide-for-portrait{display:table-cell !important}}@media only screen and (orientation: portrait){.show-for-portrait,.hide-for-landscape{display:inherit !important}.hide-for-portrait,.show-for-landscape{display:none !important}table.show-for-portrait,table.hide-for-landscape{display:table !important}thead.show-for-portrait,thead.hide-for-landscape{display:table-header-group !important}tbody.show-for-portrait,tbody.hide-for-landscape{display:table-row-group !important}tr.show-for-portrait,tr.hide-for-landscape{display:table-row !important}td.show-for-portrait,td.hide-for-landscape,th.show-for-portrait,th.hide-for-landscape{display:table-cell !important}}.show-for-touch{display:none !important}.hide-for-touch{display:inherit !important}.touch .show-for-touch{display:inherit !important}.touch .hide-for-touch{display:none !important}table.hide-for-touch{display:table !important}.touch table.show-for-touch{display:table !important}thead.hide-for-touch{display:table-header-group !important}.touch thead.show-for-touch{display:table-header-group !important}tbody.hide-for-touch{display:table-row-group !important}.touch tbody.show-for-touch{display:table-row-group !important}tr.hide-for-touch{display:table-row !important}.touch tr.show-for-touch{display:table-row !important}td.hide-for-touch{display:table-cell !important}.touch td.show-for-touch{display:table-cell !important}th.hide-for-touch{display:table-cell !important}.touch th.show-for-touch{display:table-cell !important}@media print{.show-for-print{display:block}.hide-for-print{display:none}table.show-for-print{display:table !important}thead.show-for-print{display:table-header-group !important}tbody.show-for-print{display:table-row-group !important}tr.show-for-print{display:table-row !important}td.show-for-print{display:table-cell !important}th.show-for-print{display:table-cell !important}}a,a:link{transition:all .4s;color:#0921e2}a:visited{border-bottom:#d7d7d7;color:#071582}a:hover{color:#071ab1}a:focus{color:#596af8}a:active{color:#051380}p{-webkit-hyphens:auto;-moz-hyphens:auto;-ms-hyphens:auto;hyphens:auto;-ms-word-break:normal;word-break:normal}p a,article a{font-weight:bold;border-bottom:1px dotted}p a:hover,article a:hover{border-bottom:2px solid}p a.button,.button,.button:hover{border:0;color:#fff}p.button a{border:0;color:#fff;text-shadow:0 1px 3px rgba(0,0,0,.5)}h1,h2,h3,h4,h5,h6{font-family:"Volkhov",Georgia,Times,serif;font-weight:normal;padding:0}h1{font-size:2.441em;margin-top:0}h2{font-size:1.953em;margin:1.563em 0 0 0}.blog-index h2{margin-top:0}h3{font-size:1.563em;margin:1.152em 0 0 0}h4{font-size:1.25em;margin:1.152em 0 0 0}h5{font-size:1.152em;margin:1em 0 0 0}img{border-radius:3px}img.alignleft,img.left{float:left;margin:5px 15px 5px 0}img.alignright,img.right{float:right;margin:5px 0 5px 15px}img.aligncenter,img.center{display:block;margin:0 auto 10px}figure{margin:0 0 1.875rem 0}#masthead-with-background-color figure,#masthead-with-pattern figure{margin:0}figcaption,.masthead-caption{color:#575757;font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;font-size:.8125rem;padding-top:.125rem}figcaption a,.masthead-caption a{border-bottom:1px dotted #bebebe;color:#575757}figcaption a:hover,.masthead-caption a:hover{border-bottom:2px solid #334d5c;color:#334d5c}.masthead-caption{padding-right:10px;text-align:right}td{vertical-align:top}pre{overflow:auto;margin-bottom:1.25rem;padding:5px;background-color:#e3f1c7;border-radius:3px}pre code{padding:.125rem .3125rem .0625rem 0;border:0}code{font-size:.875rem;line-height:1.5}ul,ol{margin-left:20px;padding:0}li{margin-left:0}.no-bullet{list-style:none;margin-left:0}li>ul,li>ol{margin-bottom:0}dt:first-child{padding-top:0px}dt{font-weight:bold;padding-top:30px}article dl dt{line-height:1.3}article dl dd{line-height:1.6;margin-bottom:.75rem;margin-left:1.5rem}blockquote{font-style:italic;position:relative;border:none;margin:0 30px 30px 30px;color:#4b4b4b}blockquote p{font-style:italic;color:#575757}blockquote:before{display:block;content:"»";font-size:80px;line-height:0;position:absolute;left:-25px;top:auto;color:#4b4b4b}blockquote:after{display:block;content:"«";font-size:80px;line-height:0;position:absolute;right:-10px;bottom:20px;color:#4b4b4b}blockquote cite:before{content:"— "}blockquote cite a,blockquote cite a:visited{color:#575757}cite{padding-top:5px}button,.button{letter-spacing:1px}mark{background-color:#f9c188}.subheadline{font-size:1rem;margin:0;text-transform:uppercase}.teaser{font-size:1.25rem}.big-teaser{font-style:italic;font-weight:300}.big-teaser a{font-style:italic;font-weight:400}@media only screen{.big-teaser{font-size:1.25rem}}@media only screen and (min-width: 40.063em){.big-teaser{font-size:1.8125rem}}.sans{font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif}.serif{font-family:"Volkhov",Georgia,Times,serif}.font-size-h1{font-size:2.441em}.font-size-h2{font-size:1.953em}.font-size-h3{font-size:1.563em}.font-size-h4{font-size:1.25em}.font-size-h5{font-size:1.152em}.font-size-p{font-size:16px}.footnotes:before{content:"";position:absolute;height:1px;width:60px;margin-top:-10px;border-bottom:1px solid #d7d7d7}.footnotes{margin-top:60px}.footnotes ol{font-size:.8em}.footnotes p{font-size:inherit;margin-bottom:0}@font-face{font-family:"iconfont";src:url("../fonts/iconfont.eot");src:url("../fonts/iconfont.eot?#iefix") format("embedded-opentype"),url("../fonts/iconfont.woff") format("woff"),url("../fonts/iconfont.ttf") format("truetype"),url("../fonts/iconfont.svg#svgFontName") format("svg")}.iconfont{font-family:iconfont}.iconfont-48{font-size:48px}[data-icon]:before{content:attr(data-icon)}[data-icon]:before,.icon-archive:before,.icon-browser:before,.icon-calendar:before,.icon-camera:before,.icon-chat:before,.icon-check:before,.icon-chevron-down:before,.icon-chevron-left:before,.icon-chevron-right:before,.icon-chevron-up:before,.icon-circle-with-cross:before,.icon-circle-with-minus:before,.icon-circle-with-plus:before,.icon-cloud:before,.icon-code:before,.icon-cog:before,.icon-dropbox:before,.icon-edit:before,.icon-export:before,.icon-eye:before,.icon-facebook:before,.icon-feather:before,.icon-github:before,.icon-globe:before,.icon-googleplus:before,.icon-heart:before,.icon-heart-outlined:before,.icon-home:before,.icon-instagram:before,.icon-lab-flask:before,.icon-leaf:before,.icon-linkedin:before,.icon-mail:before,.icon-message:before,.icon-mic:before,.icon-network:before,.icon-paper-plane:before,.icon-pinterest:before,.icon-price-tag:before,.icon-rocket:before,.icon-rss:before,.icon-soundcloud:before,.icon-star:before,.icon-star-outlined:before,.icon-thumbs-down:before,.icon-thumbs-up:before,.icon-tree:before,.icon-tumblr:before,.icon-twitter:before,.icon-upload-to-cloud:before,.icon-video:before,.icon-vimeo:before,.icon-warning:before,.icon-xing:before,.icon-youtube:before{display:inline-block;font-family:"iconfont";font-style:normal;font-weight:normal;font-variant:normal;line-height:1;text-decoration:inherit;text-rendering:optimizeLegibility;text-transform:none;-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-smoothing:antialiased}.icon-archive:before{content:""}.icon-browser:before{content:""}.icon-calendar:before{content:""}.icon-camera:before{content:""}.icon-chat:before{content:""}.icon-check:before{content:""}.icon-chevron-down:before{content:""}.icon-chevron-left:before{content:""}.icon-chevron-right:before{content:""}.icon-chevron-up:before{content:""}.icon-circle-with-cross:before{content:""}.icon-circle-with-minus:before{content:""}.icon-circle-with-plus:before{content:""}.icon-cloud:before{content:""}.icon-code:before{content:""}.icon-cog:before{content:""}.icon-dropbox:before{content:""}.icon-edit:before{content:""}.icon-export:before{content:""}.icon-eye:before{content:""}.icon-facebook:before{content:""}.icon-feather:before{content:""}.icon-github:before{content:""}.icon-globe:before{content:""}.icon-googleplus:before{content:""}.icon-heart:before{content:""}.icon-heart-outlined:before{content:""}.icon-home:before{content:""}.icon-instagram:before{content:""}.icon-lab-flask:before{content:""}.icon-leaf:before{content:""}.icon-linkedin:before{content:""}.icon-mail:before{content:""}.icon-message:before{content:""}.icon-mic:before{content:""}.icon-network:before{content:""}.icon-paper-plane:before{content:""}.icon-pinterest:before{content:""}.icon-price-tag:before{content:""}.icon-rocket:before{content:""}.icon-rss:before{content:""}.icon-soundcloud:before{content:""}.icon-star:before{content:""}.icon-star-outlined:before{content:""}.icon-thumbs-down:before{content:""}.icon-thumbs-up:before{content:""}.icon-tree:before{content:""}.icon-tumblr:before{content:""}.icon-twitter:before{content:""}.icon-upload-to-cloud:before{content:""}.icon-video:before{content:""}.icon-vimeo:before{content:""}.icon-warning:before{content:""}.icon-xing:before{content:""}.icon-youtube:before{content:""}body.video,body.video #masthead-no-image-header{background:#000}body.video #masthead-no-image-header{margin-bottom:60px}body.video h1,body.video h2,body.video h3,body.video h4,body.video h5,body.video h6,body.video p,body.video a,body.video blockquote:before,body.video blockquote:after,body.video cite a{color:#fff}body.video cite a:visited{color:#fff}body.video cite{color:#fff}#navigation{-webkit-box-shadow:0 2px 2px 0 rgba(0,0,0,.2);box-shadow:0 2px 3px 0 rgba(0,0,0,.2)}#navigation [class^=icon-]:before,#navigation [class*=" icon-"]:before{margin-right:.5rem}.no-js form#search{display:none}#masthead{background-color:#334d5c}#masthead-no-image-header{background-color:#334d5c}#masthead-with-text{text-align:center;font-size:3.375rem;font-family:"Volkhov",Georgia,Times,serif;color:#fff;text-transform:uppercase;text-shadow:0 2px 3px rgba(0,0,0,.4)}#masthead-no-image-header{height:100px;background-color:#3faf46}#masthead-no-image-header #logo img{margin-top:10px}@media only screen and (max-width: 40em){#logo img{margin-top:30px}#masthead{height:100px}#masthead-with-pattern{padding:15px 0}#masthead-with-background-color{padding:15px 0}#masthead-with-text{height:220px;padding:30px 0;font-size:2.25rem}#masthead-no-image-header #logo img{margin-top:35px}}@media only screen and (min-width:40.063em)and (max-width:64em){#logo img{margin-top:60px}#masthead{height:200px}#masthead-with-pattern{padding:20px 0}#masthead-with-background-color{padding:20px 0}#masthead-with-text{padding:60px 0;height:300px}#masthead-no-image-header #logo img{margin-top:20px}}@media only screen and (min-width:64.063em)and (max-width:90em){#logo img{margin-top:60px}#masthead{height:200px}#masthead-with-pattern{padding:30px 0}#masthead-with-background-color{padding:30px 0}#masthead-with-text{height:330px;padding:60px 0}}@media only screen and (min-width:90.063em){#logo img{margin-top:60px}#masthead{height:200px}#masthead-with-pattern{padding:45px 0}#masthead-with-background-color{padding:45px 0}#masthead-with-text{padding:95px 0;height:400px}}#title-image-small{height:240px}#title-image-large{height:520px}#title-image-index-small{height:120px}#title-image-index-large{height:260px}#breadcrumb{background:#f3f3f3;border-top:1px solid #f0f0f0;border-bottom:1px solid #f0f0f0}.breadcrumbs>.current{font-weight:bold}#page-meta,#page-meta a{color:#a4a4a4}#page-meta .button{background:#a4a4a4;border:0}#page-meta .button{color:#fff}#page-meta .button:hover{background:#334d5c}.meta-info p{font-size:.8125rem;color:#efefef}.meta-info a{text-decoration:underline;color:#efefef}.meta-info a:hover{text-decoration:none;color:#a1d044}#up-to-top{padding:30px 0 10px 0}#up-to-top a{font-size:24px;padding:5px;border-radius:3px}#up-to-top a:hover{background:#d7d7d7}#footer-content p,#footer-content li{font-size:.8125rem;font-weight:300}#footer{padding-top:30px;padding-bottom:20px;background:#7e7e7e;color:#fff}#footer a{color:#a1d044}#footer h4,#footer h5{letter-spacing:1px;color:#fff;text-transform:uppercase}#subfooter{background:#313131;color:#7e7e7e;padding-top:30px}#subfooter-left ul.inline-list{float:left}.credits a{color:#7e7e7e;border:0;text-transform:uppercase}.credits a:hover{color:#fff}.social-icons{margin-bottom:10px !important}.social-icons li{padding:0 0 20px 0}.social-icons a{font-size:1.4375rem;display:block;width:36px;border-radius:50%;color:#313131;background:#7e7e7e;text-align:center}.social-icons a:hover{background:#313131;color:#fff}.t10{margin-top:10px !important}.t15{margin-top:15px !important}.t20{margin-top:20px !important}.t30{margin-top:30px !important}.t50{margin-top:50px !important}.t60{margin-top:60px !important}.t70{margin-top:70px !important}.t80{margin-top:80px !important}.t90{margin-top:90px !important}.b15{margin-bottom:15px !important}.b20{margin-bottom:20px !important}.b30{margin-bottom:30px !important}.b60{margin-bottom:60px !important}.l15{margin-left:15px !important}.r15{margin-right:15px !important}.pl20{padding-left:20px !important}.pr5{padding-right:5px !important}.pr10{padding-right:10px !important}.pr20{padding-right:20px !important}#toc ul,#toc ul ul,#toc ul ul ul{list-style:none;margin-left:30px}#toc ul{margin-left:0;margin-top:30px}.border-dotted{border:1px dotted #a4a4a4;padding:1.25rem;border-radius:3px}.shadow-no{text-shadow:rgba(0,0,0,0) 0 0 0}.shadow-black{text-shadow:rgba(0,0,0,.498039) 0px 1px 2px}.shadow-white{text-shadow:rgba(255,255,255,.498039) 0px 1px 2px}.alert-box{font-family:"Lato","Helvetica Neue",Helvetica,Arial,sans-serif;text-shadow:0px 1px 1px rgba(0,0,0,.9)}.alert-box p{margin-bottom:0}.alert-box a{text-shadow:1px 1px 0px #000;color:#fff;border-bottom:1px dotted #fff}.alert-box a:hover{border-bottom:1px solid #fff}.alert-box.terminal{background:#3e3e3e;color:#fff;border-color:#353535;font-family:"Lucida Console",Monaco,monospace}.alert-box.terminal::before{content:"$ ";color:#a1d044;float:left;margin:.25em .5em 0 0}.alert-box.text{background-color:#d7d7d7;text-shadow:0px 0px 0px rgba(0,0,0,.9);border-color:#b9b9b9;color:#3e3e3e}.alert-box.windowsOS{background-color:#00008b;border-color:#000078;color:#fff}.alert-box.windowsOS::before{content:"Windows OS Information";color:#be6409}button,.button{letter-spacing:1px}button.grey,.button.grey{background:#575757}button.grey:hover,button.grey:focus,.button.grey:hover,.button.grey:focus{background-color:#0b0b0b}.side-nav li.title{text-transform:uppercase}.side-nav li{border-top:1px solid #cbcbcb}.side-nav li a:not(.button){border-bottom:0;padding:.4375rem 0rem}.side-nav li a:not(.button):hover,.side-nav li a:not(.button):focus{background:#e4e4e4}.homepage p{margin:0;padding:0;color:#575757}dl.accordion{border-top:1px solid #d7d7d7}.accordion dd{border-bottom:1px solid #d7d7d7}dd.accordion-navigation span{padding-right:12px}dd.accordion-navigation span:before{content:""}dd.accordion-navigation.active span:before{content:""}dd.accordion-navigation.active span:before{content:""}/*! Lazy Load XT v1.0.6 2014-11-19
  * http://ressio.github.io/lazy-load-xt
  * (C) 2014 RESS.io
  * Licensed under MIT */img.lazy{display:none}.lazy-hidden{opacity:0}.lazy-loaded{-webkit-transition:opacity .7s;-moz-transition:opacity .7s;-ms-transition:opacity .7s;-o-transition:opacity .7s;transition:opacity .7s;opacity:1}*:target:not([id^="fn:"]):not([id^="fnref:"])::before{content:" ";width:0;height:0;display:block;padding-top:50px;margin-top:-50px}.highlight{background:#fff}.highlight [data-lang]::before{content:attr(data-lang);display:block;text-align:right;margin-right:5px;text-transform:uppercase}.highlight .c{color:#998;font-style:italic}.highlight .err{color:#a61717;background-color:#e3d2d2}.highlight .k{font-weight:bold}.highlight .o{font-weight:bold}.highlight .cm{color:#998;font-style:italic}.highlight .cp{color:#999;font-weight:bold}.highlight .c1{color:#998;font-style:italic}.highlight .cs{color:#999;font-weight:bold;font-style:italic}.highlight .gd{color:#000;background-color:#fdd}.highlight .gd .x{color:#000;background-color:#faa}.highlight .ge{font-style:italic}.highlight .gr{color:#a00}.highlight .gh{color:#999}.highlight .gi{color:#000;background-color:#dfd}.highlight .gi .x{color:#000;background-color:#afa}.highlight .go{color:#888}.highlight .gp{color:#555}.highlight .gs{font-weight:bold}.highlight .gu{color:#aaa}.highlight .gt{color:#a00}.highlight .kc{font-weight:bold}.highlight .kd{font-weight:bold}.highlight .kp{font-weight:bold}.highlight .kr{font-weight:bold}.highlight .kt{color:#458;font-weight:bold}.highlight .m{color:#099}.highlight .s{color:#d14}.highlight .na{color:teal}.highlight .nb{color:#0086b3}.highlight .nc{color:#458;font-weight:bold}.highlight .no{color:teal}.highlight .ni{color:purple}.highlight .ne{color:#900;font-weight:bold}.highlight .nf{color:#900;font-weight:bold}.highlight .nn{color:#555}.highlight .nt{color:navy}.highlight .nv{color:teal}.highlight .ow{font-weight:bold}.highlight .w{color:#bbb}.highlight .mf{color:#099}.highlight .mh{color:#099}.highlight .mi{color:#099}.highlight .mo{color:#099}.highlight .sb{color:#d14}.highlight .sc{color:#d14}.highlight .sd{color:#d14}.highlight .s2{color:#d14}.highlight .se{color:#d14}.highlight .sh{color:#d14}.highlight .si{color:#d14}.highlight .sx{color:#d14}.highlight .sr{color:#009926}.highlight .s1{color:#d14}.highlight .ss{color:#990073}.highlight .bp{color:#999}.highlight .vc{color:teal}.highlight .vg{color:teal}.highlight .vi{color:teal}.highlight .il{color:#099}/*# sourceMappingURL=styles_feeling_responsive.css.map */
\ No newline at end of file
diff --git a/assets/css/styles_feeling_responsive.css.map b/assets/css/styles_feeling_responsive.css.map
index 68b9a065..ae202193 100644
--- a/assets/css/styles_feeling_responsive.css.map
+++ b/assets/css/styles_feeling_responsive.css.map
@@ -1 +1 @@
-{"version":3,"sourceRoot":"","sources":["../../_sass/_02_settings_typography.scss","../../_sass/_03_settings_mixins_media_queries.scss","../../_sass/_01_settings_colors.scss","../../_sass/_05_normalize.scss","../../_sass/foundation-components/_grid.scss","../../_sass/foundation-components/_global.scss","../../_sass/foundation-components/_buttons.scss","../../_sass/_04_settings_global.scss","../../_sass/foundation-components/_forms.scss","../../_sass/foundation-components/_top-bar.scss","../../_sass/foundation-components/_accordion.scss","../../_sass/foundation-components/_alert-boxes.scss","../../_sass/foundation-components/_breadcrumbs.scss","../../_sass/foundation-components/_block-grid.scss","../../_sass/foundation-components/_button-groups.scss","../../_sass/foundation-components/_clearing.scss","../../_sass/foundation-components/_dropdown.scss","../../_sass/foundation-components/_dropdown-buttons.scss","../../_sass/foundation-components/_flex-video.scss","../../_sass/foundation-components/_inline-lists.scss","../../_sass/foundation-components/_keystrokes.scss","../../_sass/foundation-components/_panels.scss","../../_sass/foundation-components/_reveal.scss","../../_sass/foundation-components/_side-nav.scss","../../_sass/foundation-components/_sub-nav.scss","../../_sass/foundation-components/_tables.scss","../../_sass/foundation-components/_thumbs.scss","../../_sass/foundation-components/_type.scss","../../_sass/foundation-components/_visibility.scss","../../_sass/_06_typography.scss","../../_sass/_07_layout.scss","../../_sass/_09_elements.scss","../../_sass/_11_syntax-highlighting.scss"],"names":[],"mappings":"CAuDA,wBAPoB,QAQpB,wBAPoB,QAQpB,wBAPoB,QAQpB,wBAPoB,OAQpB,wBAPoB,QC8RlB,wBACE,sBAGF,yBACE,4BACA,UAGF,8BACE,kDACA,UAGF,0BACE,qDACA,eAGF,+BACE,0EACA,eAGF,yBACE,qDACA,eAGF,8BACE,0EACA,eAGF,0BACE,qDACA,eAGF,+BACE,2EACA,eAGF,2BACE,sDACA,gBAGF,yCACE,kBAMA,UAEE,YAIF,mBA3TF,mBA8TwB,WA7TxB,gBA6TwB,WA5TxB,WA4TwB,WAGtB,UAEE,UDtYW,KC0Yb,KACE,WCzYgB,QD0YhB,MC5YgB,KD6YhB,UACA,SACA,YDzYmB,mDC0YnB,YDrYa,OCsYb,WDrYY,OCsYZ,YD/Ya,ICgZb,kBACA,OAlGc,KAqGhB,QACE,OAnGiB,QAuGnB,IACE,eACA,YAGF,IACE,+BAMA,0GAGE,0BAKJ,MACE,sBAGF,OACE,uBA/QJ,iCAEE,YACA,cAGF,gBACE,WAgRA,MACE,wBACA,kBAIF,WACE,kBAOF,aACE,mCACA,kCAIF,IACE,qBACA,sBAQF,SACE,YACA,gBAIF,OACE,WEnfN,4DAQA,KACE,uBACA,0BACA,8BAOF,KACE,SAaF,2FAaE,cAQF,4BAIE,qBACA,wBAQF,sBACE,aACA,SAQF,kBAEE,aAUF,EACE,+BAOF,iBAEE,UAUF,YACE,yBAOF,SAEE,iBAOF,IACE,kBAQF,GACE,cACA,eAOF,KACE,gBACA,WAOF,MACE,cAOF,QAEE,cACA,cACA,kBACA,wBAGF,IACE,WAGF,IACE,eAUF,IACE,SAOF,eACE,gBAUF,OACE,gBAOF,GACE,4BACA,uBACA,SAOF,IACE,cAOF,kBAIE,gCACA,cAkBF,sCAKE,cACA,aACA,SAOF,OACE,iBAUF,cAEE,oBAWF,oEAIE,0BACA,eAOF,sCAEE,eAOF,iDAEE,SACA,UAQF,MACE,mBAWF,uCAEE,sBACA,UASF,4FAEE,YASF,mBACE,6BACA,4BACA,+BACA,uBASF,+FAEE,wBAOF,SACE,wBACA,aACA,2BAQF,OACE,SACA,UAOF,SACE,cAQF,SACE,iBAUF,MACE,yBACA,iBAGF,MAEE,UChKE,KApMA,WACA,iBACA,kBACA,aACA,gBACA,UA/DQ,SC6KV,uBAEE,YACA,cAGF,WACE,WD+EI,6CAjKJ,eACA,gBAqKI,mBACE,cACA,eAIJ,UA5OF,WACA,uBACA,wBACA,aACA,gBACA,eCsIF,iCAEE,YACA,cAGF,gBACE,WD6FI,mBA9NJ,WACA,SACA,eCwHF,mDAEE,YACA,cAGF,yBACE,WDmGA,iBA9KA,sBACA,uBAKA,WAqBE,MCwJY,gDDCZ,YAGF,oCACE,MCLY,KDQd,mBAhIA,cAvEA,kBA4BA,QACA,WA8CA,cA3EA,kBAiCA,SACA,UAqCA,cAvEA,kBA4BA,mBACA,WA8CA,cA3EA,kBAiCA,oBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UA8CF,iBAhFE,kBAYA,sBACA,uBA0BE,MCwJY,KDxGd,SArEA,oBAqEA,SArEA,qBAqEA,SArEA,UAqEA,SArEA,qBAqEA,SArEA,qBAqEA,SArEA,UAqEA,SArEA,qBAqEA,SArEA,qBAqEA,SArEA,UAqEA,UArEA,qBAqEA,UArEA,qBAqEA,UArEA,WA2EA,gBAjCA,0BAiCA,gBAjCA,qCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,gBAjCA,sCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,gBAjCA,sCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,iBAjCA,sCAiCA,iBAjCA,sCAsCF,mBACE,cACA,eACA,UACA,WACA,MCwFc,KDrFhB,+CArDE,iBACA,kBACA,WAwDF,mDAEE,cACA,eACA,MC4Ec,KDxEhB,qEAEE,WAIF,yEAEE,MCgEc,KD7DhB,qEAEE,MC4DmB,MDtDjB,yDArIF,eACA,gBAyIE,yBACE,cACA,eAMF,6DA3IF,sBACA,uBA0BE,MCwJY,MDYd,4CApIA,eAvEA,kBA4BA,QACA,WA8CA,eA3EA,kBAiCA,SACA,UAqCA,eAvEA,kBA4BA,mBACA,WA8CA,eA3EA,kBAiCA,oBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,SACA,WA8CA,eA3EA,kBAiCA,UACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,SACA,WA8CA,eA3EA,kBAiCA,UACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,SACA,WA8CA,eA3EA,kBAiCA,UACA,UAqCA,gBAvEA,kBA4BA,oBACA,WA8CA,gBA3EA,kBAiCA,qBACA,UAqCA,gBAvEA,kBA4BA,oBACA,WA8CA,gBA3EA,kBAiCA,qBACA,UA8CF,iBAhFE,kBAYA,sBACA,uBA0BE,MCwJY,KDxGd,UArEA,oBAqEA,UArEA,qBAqEA,UArEA,UAqEA,UArEA,qBAqEA,UArEA,qBAqEA,UArEA,UAqEA,UArEA,qBAqEA,UArEA,qBAqEA,UArEA,UAqEA,WArEA,qBAqEA,WArEA,qBAqEA,WArEA,WA2EA,iBAjCA,0BAiCA,iBAjCA,qCAiCA,iBAjCA,sCAiCA,iBAjCA,2BAiCA,iBAjCA,sCAiCA,iBAjCA,sCAiCA,iBAjCA,2BAiCA,iBAjCA,sCAiCA,iBAjCA,sCAiCA,iBAjCA,2BAiCA,kBAjCA,sCAiCA,kBAjCA,sCAsCF,oBACE,cACA,eACA,UACA,WACA,MCwFc,KDrFhB,iDArDE,iBACA,kBACA,WAwDF,qDAEE,cACA,eACA,MC4Ec,KDxEhB,uEAEE,WAIF,2EAEE,MCgEc,KD7DhB,uEAEE,MC4DmB,MDtDjB,2DArIF,eACA,gBAyIE,0BACE,cACA,eAMF,+DA3IF,sBACA,uBA0BE,MCwJY,KDiBV,QAhNJ,kBA4BA,QACA,WAuLI,QApNJ,kBAiCA,SACA,UA8KI,QAhNJ,kBA4BA,mBACA,WAuLI,QApNJ,kBAiCA,oBACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,SACA,WAuLI,QApNJ,kBAiCA,UACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,SACA,WAuLI,QApNJ,kBAiCA,UACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,SACA,WAuLI,QApNJ,kBAiCA,UACA,UA8KI,SAhNJ,kBA4BA,oBACA,WAuLI,SApNJ,kBAiCA,qBACA,UA8KI,SAhNJ,kBA4BA,oBACA,WAuLI,SApNJ,kBAiCA,qBACA,WAwLA,4CAnJA,cAvEA,kBA4BA,QACA,WA8CA,cA3EA,kBAiCA,SACA,UAqCA,cAvEA,kBA4BA,mBACA,WA8CA,cA3EA,kBAiCA,oBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UA8CF,iBAhFE,kBAYA,sBACA,uBA0BE,MCwJY,KDxGd,SArEA,oBAqEA,SArEA,qBAqEA,SArEA,UAqEA,SArEA,qBAqEA,SArEA,qBAqEA,SArEA,UAqEA,SArEA,qBAqEA,SArEA,qBAqEA,SArEA,UAqEA,UArEA,qBAqEA,UArEA,qBAqEA,UArEA,WA2EA,gBAjCA,0BAiCA,gBAjCA,qCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,gBAjCA,sCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,gBAjCA,sCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,iBAjCA,sCAiCA,iBAjCA,sCAsCF,mBACE,cACA,eACA,UACA,WACA,MCwFc,KDrFhB,+CArDE,iBACA,kBACA,WAwDF,mDAEE,cACA,eACA,MC4Ec,KDxEhB,qEAEE,WAIF,yEAEE,MCgEc,KD7DhB,qEAEE,MC4DmB,MDtDjB,yDArIF,eACA,gBAyIE,yBACE,cACA,eAMF,6DA3IF,sBACA,uBA0BE,MCwJY,KD+BV,QA9NJ,kBA4BA,QACA,WAqMI,QAlOJ,kBAiCA,SACA,UA4LI,QA9NJ,kBA4BA,mBACA,WAqMI,QAlOJ,kBAiCA,oBACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,SACA,WAqMI,QAlOJ,kBAiCA,UACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,SACA,WAqMI,QAlOJ,kBAiCA,UACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,SACA,WAqMI,QAlOJ,kBAiCA,UACA,UA4LI,SA9NJ,kBA4BA,oBACA,WAqMI,SAlOJ,kBAiCA,qBACA,UA4LI,SA9NJ,kBA4BA,oBACA,WAqMI,SAlOJ,kBAiCA,qBACA,WE4EA,eAhJA,aAlCkB,MAmClB,aApCkB,EAqClB,OL8PmB,QK7PnB,YNlDqB,mDMmDrB,YNpCiB,OMqCjB,mBACA,mBACA,kBACA,qBACA,WAlDgB,OAmDhB,wBACA,gBAEa,QAlEA,aAiFb,YArFS,KAsFT,mBACA,yBACA,kBAGmC,UA9ErB,KAmId,iBJlIkB,QImIlB,aARiB,QAajB,WDrFF,2CCiFE,sDACU,iBAdG,QAmBb,sDAEE,WAsDA,mCAhEF,iBJ7HkB,QI8HlB,aAtHwB,QA2HxB,WAJA,8FACU,iBAxHc,QA6HxB,8FAEE,WAuDA,+BAjEF,iBJ7HkB,QI8HlB,aApHsB,QAyHtB,WAJA,sFACU,iBAtHY,QA2HtB,sFAEE,WAwDA,2BAlEF,iBJ9HkB,QI+HlB,aAlHoB,QAuHpB,WAJA,8EACU,iBApHU,QAyHpB,8EAEE,WAyDA,+BAnEF,iBJ/HkB,QIgIlB,aAhHsB,QAqHtB,WAJA,sFACU,iBAlHY,QAuHtB,sFAEE,WA0DA,yBApEF,iBJlIkB,QImIlB,aA9GmB,QAmHnB,WAJA,0EACU,iBAhHS,QAqHnB,0EAEE,WA4DA,2BAjIF,YApFS,SAqFT,sBACA,yBACA,qBAMmC,UAhFrB,QAyMZ,2BAlIF,YAtFS,QAuFT,sBACA,wBACA,qBAKmC,UAjFrB,SA4MZ,yBAnIF,YAvFS,QAwFT,sBACA,wBACA,qBAImC,UAjFrB,SA8MZ,6BA9GF,gBACA,eACA,WA8GE,wEACA,6EAEA,6BD1MF,cEqHY,IDsFV,2BD3MF,cAiRa,OCpEX,oEAjFF,iBJlIkB,QImIlB,aAxHc,QA6Hd,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wLACU,iBA1HI,QA+Hd,wLAEE,WASF,wLACU,iBJtJQ,QIoNd,4GAlFJ,iBJ7HkB,QI8HlB,aAtHwB,QA2HxB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wQACU,iBAxHc,QA6HxB,wQAEE,WASF,wQACU,iBJjJQ,QIgNd,oGAnFJ,iBJ7HkB,QI8HlB,aApHsB,QAyHtB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wPACU,iBAtHY,QA2HtB,wPAEE,WASF,wPACU,iBJjJQ,QIiNd,4FApFJ,iBJ9HkB,QI+HlB,aAlHoB,QAuHpB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wOACU,iBApHU,QAyHpB,wOAEE,WASF,wOACU,iBJlJQ,QImNd,oGArFJ,iBJ/HkB,QIgIlB,aAhHsB,QAqHtB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wPACU,iBAlHY,QAuHtB,wPAEE,WASF,wPACU,iBJnJQ,QIqNd,wFAtFJ,iBJlIkB,QImIlB,aA9GmB,QAmHnB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,gOACU,iBAhHS,QAqHnB,gOAEE,WASF,gOACU,iBJtJQ,QI6NlB,4CAEA,4CACE,eAxKW,QAyKmC,cEyKhD,KACE,gBAjVJ,eACE,iBAEA,+CAEE,gBAIF,wBACE,SAEA,iEAEE,UAGF,8BH3DF,mCG4D8C,EH3D9C,gCG2D8C,EH1D9C,2BG0D8C,EHzD9C,wBGyD8C,EAMhD,oGAIE,mBA8TA,MA/PA,UAhKmB,QAiKnB,MA9JoB,QA+JpB,OAnKiB,QAoKjB,cACA,YR9IiB,OQ+IjB,YAnKqB,IAoKrB,cAjKuB,EA6ZrB,YAvPF,sBACA,iBA0PE,aAtPF,kBACA,mBA0PE,YACE,eAxaqB,WAyarB,cAKJ,iBA3PF,cACA,kBACA,UACA,kBACA,WACA,cACA,iBACA,aAzJyB,MA0JzB,aA3JyB,IA4JzB,SA1JsB,OA2JtB,UAjMqB,QAkMrB,iBACA,sBAqPE,gBAjLA,eACA,gBACA,cACA,iBACA,kBACA,YAiLA,eA3NA,eACA,gBACA,cACA,iBACA,kBACA,YA2NA,sBHjbA,cGkbkB,EHxalB,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,ICiUZ,uBHtbA,cGubkB,EH7alB,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,ICsUZ,qBH3bA,cG4bkB,EHlblB,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OG+Kb,sBHhcA,cGickB,EHvblB,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,OGqLb,yBAvQA,WA9Kc,QA+Kd,kBAIE,MH6BC,KGpBH,aA3LwB,KAybxB,2BAvOA,WAnNc,QAoNd,iBAIE,MHRC,KGiBH,aAhOwB,KA+bxB,8QACE,wBACA,gBA3XJ,iBHyHO,KGxHP,YApGkB,QAuGhB,aAhGiB,MAiGjB,aAhGiB,IAiGjB,aApGiB,KAuGnB,WAhGiB,+BAiGjB,MA5GiB,gBA6GjB,cACA,UA7GgB,QA8GhB,kBACA,cACA,iBACA,WHpDA,mBGqDoB,WHpDpB,gBGoDoB,WHnDpB,WGmDoB,WHgEpB,yDAEA,wWACE,wBACA,aGlLuB,KAqHzB,wWACE,WAxHmB,QAyHnB,aAvHuB,KAwHvB,aAIF,qZACE,iBHgGS,KG/FT,OP2KmB,QOvKrB,m3CAGE,iBHwFS,KGvFT,OPmKmB,QOsLjB,uXH1dF,cEqHY,IC8WN,wIHneN,cGsewB,EH5dxB,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,ICqXN,8CH1eN,cG2ewB,EHjexB,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,IC6XN,2IHlfN,cGqfwB,EH3exB,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,ICoYN,gDHzfN,cG0fwB,EHhfxB,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,IC4YN,qIHjgBN,cGogBwB,EH1fxB,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,OGuPP,6CHxgBN,cGygBwB,EH/fxB,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OG+PP,wIHhhBN,cGmhBwB,EHzgBxB,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OGsQP,+CHvhBN,cGwhBwB,EH9gBxB,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,OG8Qb,mBACE,wBACA,gBAIF,eACE,YAIF,SACE,eAIF,OA5OF,mCACA,gBACA,iBHnHO,QG4HP,qVAGA,gCAEA,4BAGE,aA1ViB,MA2VjB,aA1ViB,IA2VjB,aA9ViB,KAiWnB,cACA,UArWgB,QAsWhB,YRvWuB,mDQwWvB,MAxWiB,gBAyWjB,mBH/VE,cGgWc,EAiNZ,iBAzOJ,mBACE,aAyBF,cHlWE,cEqHY,ICiPd,aACE,iBA3ToB,QA4TpB,aA7WuB,KAiXzB,gBACE,iBHrJS,KGsJT,OP1EmB,QOiRnB,+DAIE,kBAGF,mDAEE,qBACA,kBACA,aArlBS,KAslBT,gBACA,wBAIF,iBACE,WAcF,SAnVF,sBACA,QA3PiB,QA4PjB,OA3PgB,WA8PhB,gBACE,YRlQe,KQmQf,WHxDK,KGyDL,QA5Pa,WA6Pb,SACA,uBAiVE,gHAjTJ,cACA,QAhR4B,0BAiR5B,WAhRwB,KAiRxB,cApUa,KAqUb,UAjR8B,OAkR9B,YR5SmB,OQ6SnB,WAjR+B,OAqR/B,WNxToB,QM2TlB,MHxGK,KGmZH,iDAEE,aAIJ,uBA9TF,cACA,QAhR4B,0BAiR5B,WAhRwB,KAiRxB,cApUa,KAqUb,UAjR8B,OAkR9B,YR5SmB,OQ6SnB,WAjR+B,OAqR/B,WNxToB,QM2TlB,MHxGK,KGgaH,2CAGE,gBAGF,qDAEE,cA9oBO,KAipBT,gCAxVJ,MNtSoB,QMmoBhB,mBArVJ,cACA,QAhR4B,0BAiR5B,WAhRwB,KAiRxB,cApUa,KAqUb,UAjR8B,OAkR9B,YR5SmB,OQ6SnB,WAjR+B,OAqR/B,WNxToB,QM2TlB,MHxGK,KGqbD,mBACE,cACA,yBACA,UACA,eAvpBmB,WAwpBnB,kBACA,cACA,SACA,eAIJ,0BACE,cAIJ,wCAGE,gBAGF,YAzXF,MNtSoB,QO+ElB,0BACE,sDACA,MFuyCc,SEnyChB,iBACE,WACA,WPnGgB,QOqGhB,0BACE,cAtGe,EA2GnB,OACE,WACA,OACA,eACA,MACA,WAEA,8BACE,gBACA,YACA,WACA,gBAEA,0CACE,eACA,WACA,WAIF,+CACE,WACA,WF2sCM,SEtsCZ,SACE,gBACA,OFosCU,SEnsCV,YFmsCU,SElsCV,kBACA,WP3IgB,QO4IhB,cA5IiB,EA+IjB,YACE,gBACA,gBAGF,cACE,eAGF,6BAEE,gBAGF,eACE,OAlGc,QAmGd,mBACA,sBACA,UAzIkB,OA4IpB,iCAEE,qBACA,wBACA,gBACA,UAjJkB,OAsJlB,yCAVF,iCAWI,kBACA,UAKJ,qBACE,kBACA,SAGF,eACE,OFipCQ,SEhpCR,SACA,UFzIS,KE2IT,6GAME,YFuoCM,SEtoCN,UF2oCe,UE1oCf,SAEA,yHACE,YTtLO,KSuLP,MP/IU,KOgJV,UACA,cACA,0BAMN,wBACE,kBACA,QACA,MAEA,0BACE,MP9JY,KO+JZ,eF8pCmB,UE7pCnB,UA9KmB,SA+KnB,YTzMS,KS0MT,kBACA,cACA,0BACA,OF2mCM,SE1mCN,YF0mCM,SEtmCR,kCACE,QACA,iBAEA,oCAKE,YACA,iBACA,4CACA,MPnKa,KOoKb,kBJ9HV,gDACE,WACA,kBACA,cACA,SAsBE,QACA,gBACA,MI5HgB,gBJ+HlB,6DAGA,MI0G6B,KJvG/B,qDACE,WACE,4CI4GA,kBACE,YACA,yBAEA,8BACE,WP7QY,QOiRZ,mCACE,MPrQU,QOuQV,+CAGE,sEAUV,iBACE,OACA,kBACA,WJzOJ,+BI4OI,oBACE,UACA,WACA,YACA,cACA,UFxPS,KEyPT,SAGF,4DAEE,WFulCoB,kBEtlCpB,WACA,WACA,WAGF,uBACE,WP5Sc,QO8Sd,yBACE,cACA,WACA,MPlQY,KOmQZ,sBACA,aA3SY,gBA4SZ,YT7Te,mDS8Tf,UFgiCc,SE/hCd,YThTW,OSiTX,eFsiCmB,UEpiCnB,gCACE,UF2hCY,SE1hCZ,cAnTU,gBAoTV,aApTU,gBHqHlB,iBJlIkB,QImIlB,aARiB,QAajB,WAJA,4EACU,iBAdG,QAmBb,4EAEE,WGyLI,0CHnMN,iBJ7HkB,QI8HlB,aARiB,QAajB,WAJA,gGACU,iBAdG,QAmBb,gGAEE,WG6LI,wCHvMN,iBJ7HkB,QI8HlB,aARiB,QAajB,WAJA,4FACU,iBAdG,QAmBb,4FAEE,WGiMI,sCH3MN,iBJ9HkB,QI+HlB,aARiB,QAajB,WAJA,wFACU,iBAdG,QAmBb,wFAEE,WGqMI,wCH/MN,iBJ/HkB,QIgIlB,aARiB,QAajB,WAJA,4FACU,iBAdG,QAmBb,4FAEE,WG0ME,8BACE,UFmgCc,SElgCd,cA3UY,gBA4UZ,aA5UY,gBHqHlB,iBJlIkB,QImIlB,aARiB,QAajB,WAJA,wEACU,iBAdG,QAmBb,wEAEE,WGgNI,wCH1NN,iBJ7HkB,QI8HlB,aARiB,QAajB,WAJA,4FACU,iBAdG,QAmBb,4FAEE,WGoNI,sCH9NN,iBJ7HkB,QI8HlB,aARiB,QAajB,WAJA,wFACU,iBAdG,QAmBb,wFAEE,WGwNI,oCHlON,iBJ9HkB,QI+HlB,aARiB,QAajB,WAJA,oFACU,iBAdG,QAmBb,oFAEE,WG4NI,sCHtON,iBJ/HkB,QIgIlB,aARiB,QAajB,WAJA,wFACU,iBAdG,QAmBb,wFAEE,WGkOE,8CACE,iBJ1IE,KI6IA,WP7WU,QOgXZ,MPhUgB,KOoUlB,gCACE,WPrXY,QOsXZ,MPrUiB,KOuUjB,sCACE,WP7XU,QO8XV,MPxUqB,KO8U3B,2BACE,QAzXc,gBA6XhB,+BACE,kBAGE,uCJxUR,WACA,cACA,QACA,SACA,iBAaE,yEACA,wBI2TQ,aAtYU,gBAuYV,kBACA,kBACA,QACA,QAIJ,qCACE,gBAEA,+CAvVR,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,6BAuVU,WAGF,6CACE,aAMN,2BACE,UACA,kBACA,UACA,MACA,WA7WN,cJmIA,6BACA,WACA,UACA,gBACA,8BIyOM,8BACE,WACA,YAEA,gCACE,YT5aS,OS6aT,4BAEA,4CACE,YThbO,OSobX,iFAGE,gBACA,aACA,UAtbY,SAwbZ,qFACE,MPnZQ,KOqZR,cAEA,iGACE,gBAKN,uCACE,4BAGF,2EAEE,SAIJ,iCACE,gCACA,gBACA,eA/b6B,UAgc7B,MP9dY,QO+dZ,YTpdS,KSqdT,UAhcwB,QAqc9B,cACE,cAKF,6CACE,SACE,WPtfc,QOwfd,iBJnVN,+BAEE,YACA,cAGF,eACE,WI8UI,wBACE,aAGF,qBACE,MJ3OQ,KI8OV,oBACE,WAGF,gDAGE,kBACA,kBACA,OA/cY,QAgdZ,aAGF,kBACE,WPhhBY,QOohBhB,0BACE,UL7hBI,SK8hBJ,cACA,cAvhBe,EA0hBjB,iBJ/dJ,oBIieM,kBAEA,oBACE,WACA,uBACA,eAEA,uBACE,MJhRM,KIkRN,qCACE,aAOF,yCACE,iBJlUF,KIqUI,WPriBM,QOwiBR,MPxfY,KO6fd,kDACE,0BACA,YFgxBE,SE/wBF,WP7jBQ,QO+jBR,wDACE,iBJnVJ,KIsVM,WPtjBI,QO6jBV,yDACE,0BACA,YFgwBE,SE/vBF,MP/gBa,KOghBb,WPjkBQ,QOmkBR,+DACE,WPxkBM,QOykBN,MPnhBiB,KO2hBrB,iCACE,yCAEA,uCJ/gBZ,WACA,cACA,QACA,SACA,iBAGE,yEACA,uBIygBY,kBACA,cAKN,qCACE,kBAEA,+CA9hBV,cJmIA,6BACA,WACA,UACA,gBACA,8BI8ZU,wGAhiBV,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,6BAmiBQ,iDAriBR,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,6BA0iBc,iEACE,YACA,YACA,SACA,gBACA,UACA,gBAOV,2BACE,OACA,SACA,yBACA,eAGE,gCACE,MPtkBe,KOukBf,YF2rBE,SE1rBF,mBACA,6BACA,WP3oBQ,QO+oBR,yEACE,MP/kBa,KOglBb,WPjpBM,QOopBR,+EACE,MPjmBU,KOkmBV,iBJlbJ,KIqbM,WPrpBI,QO0pBV,oCACE,mBACA,WJ1bP,KI8bK,wCACE,UACA,MAKN,kEAEE,mBACA,gBACA,aFgtBqB,kBE/sBrB,WACA,OFkpBM,SEjpBN,QAGF,2BACE,WP/rBY,QOgsBZ,0BACA,OF2oBM,SEtoBN,qCACE,UACA,QAEA,kDACE,WAMJ,oCACE,WACA,OAEA,iDACE,UAYJ,sCACE,iBJtfA,KIyfE,WPztBQ,QO4tBV,MP5qBc,KOgrBhB,uCACE,WPjuBU,QOkuBV,MPjrBe,KOurBf,sDAtqBV,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,6BAyqBQ,wDA3qBR,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,8BC+CE,WAEE,gBLmCJ,mCAEE,YACA,cAGF,iBACE,WKxCE,+CAEE,cACA,2BAEA,iEACE,WA/I6B,QAkJ/B,mDACE,WLsFA,QKrFA,MLiGH,KKhGG,QHoKqB,OGnKrB,cACA,YV9Ie,mDU+If,UAtJuB,KAwJvB,+DACE,WA5J0B,QAgK9B,iEACE,aACA,QA5JkB,SA8JlB,+EACE,cACA,WRhKU,QSmGlB,WAjEF,aA3BmB,MA4BnB,aA3BmB,IA4BnB,cACA,YXlBmB,OWmBnB,cA5BoB,QA6BpB,kBACA,uCACA,UJmSgB,SFjRhB,kCMLA,iBT9CoB,QS+CpB,qBAQE,MNgKK,KMzHH,kBAhCJ,UAtDsB,SAuDtB,QApDoB,YAqDpB,cACA,kBACA,IA5DgB,IA6DhB,sBACA,MA7DqB,OA8DrB,MNkKK,KMjKL,QA7DoB,GA8DpB,WA3DuB,QA6DvB,gDAEE,QAjEwB,GAwFtB,kBN5FF,cEqHY,IIrBV,iBNhGF,cAiRa,OM7KX,mBA5DJ,iBTzCoB,QS0CpB,qBAQE,MNgKK,KMzGH,iBAhEJ,iBT1CoB,QS2CpB,qBAQE,MNgKK,KMrGH,qBApEJ,iBTzCoB,QS0CpB,qBAQE,MNgKK,KMjGH,mBAxEJ,iBT3CoB,QS4CpB,qBAQE,MNgKK,KM7FH,gBA5EJ,iBT9CoB,QS+CpB,qBAQE,MNgKK,KMzFH,uBACE,UCtCJ,aA1EF,cACA,QA7Bc,0BA8Bd,gBACA,cACA,gBACA,aA3BmB,MA4BnB,aLwWkB,EKrWlB,yBACA,aVDoB,QGlBlB,cE0XW,EKnST,eA7DJ,SACA,MP2OgB,KO1OhB,UApCgB,SAqChB,YArCgB,SAsChB,eAlCqB,UAmCrB,MVrCoB,QUuCpB,8DApCiB,UAsCjB,iBACE,MV1CkB,QU8CpB,uBACE,OX2PmB,QW1PnB,MPuLG,KOtLH,yBACE,OXwPiB,QWvPjB,MPoLC,KOjLH,wHACqB,qBAIvB,2BACE,MPqKQ,KOpKR,mCPoKQ,KOlKR,wIAIE,qBACA,MP6JM,KO5JN,OXqOiB,QWjOrB,sBACE,YACA,MPqJI,KOpJJ,gBACA,kBACA,QAGF,kCACE,YACA,SAkBJ,kDACE,YCVE,qBAhFA,cACA,UAOE,mBRyIJ,uDAEE,YACA,cAGF,2BACE,WQ3IA,wBACE,cACA,YACA,MRgPY,KQ7OV,0BAkEF,mBA5DF,uBACE,WAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,YAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,2CACE,WAdJ,wBACE,oBAMA,gBAEA,wCACE,WAGF,2CACE,WAdJ,wBACE,oBAMA,gBAEA,wCACE,WAGF,2CACE,YAkDF,4CAhEF,wBACE,WAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,qBAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,qBAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,qBAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,YAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,qBAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,yBACE,UAMA,gBAEA,yCACE,WAGF,4CACE,WAdJ,yBACE,oBAMA,gBAEA,yCACE,WAGF,4CACE,WAdJ,yBACE,oBAMA,gBAEA,yCACE,WAGF,4CACE,YAsDF,4CApEF,uBACE,WAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,YAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,2CACE,WAdJ,wBACE,oBAMA,gBAEA,wCACE,WAGF,2CACE,WAdJ,wBACE,oBAMA,gBAEA,wCACE,WAGF,2CACE,YCsGJ,cA9JA,gBACA,SACA,OTgKF,yCAEE,YACA,cAGF,oBACE,WSRE,iBAnHF,cACA,qBA5BF,iDAEE,sBACA,kCAKA,yEAEE,cAyIE,uBAxHJ,cACA,qBAIA,cACA,SAoHM,WArJR,6DAEE,sBACA,kCAKA,qFAEE,cAyBF,6DAEE,qBACA,kCACA,oBACA,SACA,cAKA,qFAEE,aA0GA,iCA/HJ,cACA,qBA5BF,iFAEE,sBACA,kCAKA,yGAEE,cAmJI,yCAHF,iCA/HJ,cACA,qBAIA,cACA,SAjCF,iFAEE,sBACA,kCAKA,yGAEE,cAyBF,iFAEE,qBACA,kCACA,oBACA,SACA,cAKA,yGAEE,cAmHF,uBAxIF,cACA,qBA5BF,6DAEE,sBACA,kCAKA,qFAEE,cAkFF,6GTpGA,cSwGkB,EAGlB,6JTjGA,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,IOGZ,yJT9GA,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,IO0DV,6BA5IF,cACA,qBAIA,cACA,SAjCF,yEAEE,sBACA,kCAKA,iGAEE,cAyBF,yEAEE,qBACA,kCACA,oBACA,SACA,cAKA,iGAEE,aA4CJ,qITpGA,cSwGkB,EAGlB,qLT1FA,wBEoGY,IFnGZ,yBEmGY,IFlGZ,uBEkGY,IFjGZ,wBEiGY,IOGZ,iLTvGA,2BEoGY,IFnGZ,4BEmGY,IFlGZ,0BEkGY,IFjGZ,2BEiGY,IO+DR,4CADF,uCAhJF,cACA,qBA5BF,6FAEE,sBACA,kCAKA,qHAEE,cAkFF,6KTpGA,cSwGkB,EAGlB,6NTjGA,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,IOGZ,yNT9GA,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,KOmER,yCALF,uCAhJF,cACA,qBAIA,cACA,SAjCF,6FAEE,sBACA,kCAKA,qHAEE,cAyBF,6FAEE,qBACA,kCACA,oBACA,SACA,cAKA,qHAEE,aA4CJ,6KTpGA,cSwGkB,EAGlB,6NT1FA,wBEoGY,IFnGZ,yBEmGY,IFlGZ,uBEkGY,IFjGZ,wBEiGY,IOGZ,yNTvGA,2BEoGY,IFnGZ,4BEmGY,IFlGZ,0BEkGY,IFjGZ,2BEiGY,KOwEV,sBA1JF,cACA,qBA5BF,2DAEE,sBACA,kCAKA,mFAEE,cAkFF,yGTpGA,cSwGkB,EAGlB,yJTjGA,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OSzJb,qJT9GA,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,OShFX,4BA9JF,cACA,qBAIA,cACA,SAjCF,uEAEE,sBACA,kCAKA,+FAEE,cAyBF,uEAEE,qBACA,kCACA,oBACA,SACA,cAKA,+FAEE,aA4CJ,iITpGA,cSwGkB,EAGlB,iLT1FA,wBCrCS,KDsCT,yBCtCS,KDuCT,uBCvCS,KDwCT,wBCxCS,KQ4IT,6KTvGA,2BCrCS,KDsCT,4BCtCS,KDuCT,0BCvCS,KDwCT,2BCxCS,KQ0NL,4CADF,sCAlKF,cACA,qBA5BF,2FAEE,sBACA,kCAKA,mHAEE,cAkFF,yKTpGA,cSwGkB,EAGlB,yNTjGA,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OSzJb,qNT9GA,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,QSvET,yCALF,sCAlKF,cACA,qBAIA,cACA,SAjCF,2FAEE,sBACA,kCAKA,mHAEE,cAyBF,2FAEE,qBACA,kCACA,oBACA,SACA,cAKA,mHAEE,aA4CJ,yKTpGA,cSwGkB,EAGlB,yNT1FA,wBCrCS,KDsCT,yBCtCS,KDuCT,uBCvCS,KDwCT,wBCxCS,KQ4IT,qNTvGA,2BCrCS,KDsCT,4BCtCS,KDuCT,0BCvCS,KDwCT,2BCxCS,MQoOL,wBA7KJ,cACA,qBAoGA,UAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,qBAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,UAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,UAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,qBAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,qBAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,YAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WTWJ,qCAEE,YACA,cAGF,kBACE,WS2DE,0BA7NF,WACA,aAlByB,QAoBzB,8BACE,gBCSF,iCAEE,gBACA,cACA,gBV0IJ,4FAEE,YACA,cAGF,6CACE,WU/IE,uCACE,MVsPU,KUrPV,kBAGF,+EACE,eAIJ,mBACE,WVuMC,KUtMD,eACA,WACA,YACA,MACA,OACA,YAEA,iDAGF,oBACE,kBACA,YACA,YACA,gBACA,SAGF,sBACE,kBACA,QACA,SACA,MVyKE,KUxKF,eAGF,aACE,WACA,kBAEA,iBACE,kBACA,SACA,QACA,iBACA,gBACA,eAIJ,kBACE,MVqJE,KUpJF,UA5EuB,OA6EvB,gBACA,gBACA,kBACA,SACA,WVuJC,KUtJD,WACA,QAlFqB,eAmFrB,kBACA,OAGF,gBACE,YACA,kBACA,iBACA,UApGgB,KAqGhB,cACA,MVkIE,KUjIF,aAEA,4CACU,MV8HR,KU3HJ,oDACE,kEAIF,qBACE,aACA,2CACE,cAKJ,4CACE,wCAEE,kBACA,YACA,WACA,MACA,kDACE,kBACA,QACA,cACA,QACA,SACA,kBACA,yEAGJ,oBACE,OACA,yBACE,SACA,2BACA,mBVwFF,KUrFF,oBACE,QACA,yBACE,2BACA,kBViFF,KU7EF,0DAC+B,WAI7B,kDACE,WAtKa,kBAuKb,OArJiB,MAsJjB,gBACA,kBAEA,qDACE,qBACA,YACA,YACA,kBACA,WAEA,wDACE,cACA,MAjKkB,MAkKlB,mBACA,MVoGI,KUnGJ,gBACA,eACA,UACA,kBACA,Od8HS,Qc7HT,WACA,WAGE,uEACE,YACA,eAIJ,6DACE,YACA,gBACA,cAGF,4DACA,0BACA,sBAGA,0EACA,yEAKN,qDACE,WV6BH,KU5BG,gBACA,OAzMmB,IA6MvB,gBACE,kBACA,SACA,WACA,eACA,eCjBJ,YA9JF,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAME,WACA,WA/DoB,KAgEpB,OAjEgB,KAkEhB,WXoKK,KWnKL,sBACA,UArCmB,QAsCnB,WAcA,WA/EoB,IA+KL,UApLI,MA4DrB,uCACA,yCAyBE,8BXCF,cACA,QACA,SACA,iBAQE,4DACA,0BWXE,kBACA,UACA,KA/D4B,KAgE5B,WAEF,kBXPF,WACA,cACA,QACA,SACA,iBAQE,4DACA,0BWJE,kBACA,UACA,SACA,WAGF,yBACE,UACA,MA5E4B,KA8E9B,wBACE,UACA,UA4GA,uBAjKJ,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAME,WACA,WA/DoB,KAgEpB,OAjEgB,KAkEhB,WXoKK,KWnKL,sBACA,UArCmB,QAsCnB,WA0CA,aACA,YA5GoB,IA+KL,UApLI,MA4DrB,kDACA,oDAsDE,8BX7BF,WACA,cACA,QACA,SACA,iBAkBE,4DACA,yBWQE,kBACA,IA3F4B,KA4F5B,WACA,WAEF,6BXpCF,WACA,cACA,QACA,SACA,iBAkBE,4DACA,yBWeE,kBACA,QACA,WACA,WA4FA,sBArKJ,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAME,WACA,WA/DoB,KAgEpB,OAjEgB,KAkEhB,WXoKK,KWnKL,sBACA,UArCmB,QAsCnB,WA+DA,aACA,iBA8Ce,UApLI,MA4DrB,iDACA,mDA2EE,6BXlDF,WACA,cACA,QACA,SACA,iBAaE,4DACA,wBWkCE,kBACA,IAhH4B,KAiH5B,YACA,UACA,WAEF,4BX1DF,WACA,cACA,QACA,SACA,iBAaE,4DACA,wBW0CE,kBACA,QACA,YACA,UACA,WAyEA,qBAzKJ,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAME,WACA,WA/DoB,KAgEpB,OAjEgB,KAkEhB,WXoKK,KWnKL,sBACA,UArCmB,QAsCnB,WAsFA,gBACA,cAuBe,UApLI,MA4DrB,gDACA,kDAkGE,4BXzEF,WACA,cACA,QACA,SACA,iBAGE,4DACA,uBWmEE,kBACA,SACA,aACA,KAzI4B,KA0I5B,WACA,WAEF,2BXlFF,WACA,cACA,QACA,SACA,iBAGE,4DACA,uBW4EE,kBACA,SACA,aACA,SACA,WACA,WAqDA,eAtCJ,UA9JqB,QA+JrB,Of4HqB,Qe1HrB,YA/JuB,SAgKvB,SAEA,0CACU,WXwCH,KWtCP,sBXjLE,cEqHY,IS8Dd,iBACE,cACA,QA1KsB,MA2KtB,MXyCQ,KWdN,oBAjLJ,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAeE,QAlCyB,QAmCzB,WACA,OA1EgB,KA2EhB,WA1EoB,KA2EpB,WX0JK,KWzJL,sBACA,UA/CmB,QAgDnB,WAoGe,UApLI,MA4DrB,+CACA,iDA6KI,iCACA,kCACA,mCACA,kCACA,iBACE,sBACA,0BAEA,sBACE,kBC9HN,iCAvEA,kBACA,aAuCA,cAjE0B,UA6B1B,+CACE,kBACA,WACA,QACA,SACA,cACA,mBACA,4DACA,QA8BF,+CACE,aAnEyB,QAoEzB,MAnE6B,WAoE7B,WAnEwB,YAoF1B,+CACE,4DAYA,2CAzDF,cAvD0B,SAyD1B,uDACE,aAhEW,QAiEX,MAzD6B,SA0D7B,WAzDwB,UAgG1B,yDACE,4DAgBA,6CAlDF,cA5D0B,UA8D1B,2DACE,aA1EW,SA2EX,MA9D6B,UA+D7B,WA9DwB,YA0F1B,2DACE,4DAoBA,6CAhCF,cAtE0B,SAwE1B,2DACE,aAxEyB,SAyEzB,MAxE6B,WAyE7B,WAxEwB,YA8E1B,2DACE,4DAwBA,iEACE,4DClGJ,YAxBF,kBACA,YAbuB,UAcvB,eAb0B,MAc1B,SACA,cAdyB,KAezB,gBAEA,sCAdqC,OAerC,gCAEA,0EAIE,kBACA,MACA,OACA,WACA,YCUA,aAlBF,6BACA,YApBiC,UAqBjC,aAvB4B,EAwB5B,QAnBoB,EAoBpB,gBACA,SAlBqB,OAoBrB,gBACE,gBACA,Md6Pc,Kc5Pd,YA5BoC,SA6BpC,QArBkB,MAsBlB,0BAnB2B,MC2B3B,eAjBF,iBAfa,QAgBb,kBAG0B,Mf2NrB,KexNL,aArBuB,MAsBvB,aArBuB,IAsBvB,SACA,YAnCe,uCAoCf,UAnCoB,QAoCpB,QA9BkB,iBfehB,cEqHY,Ic3BZ,OAhFA,aA/BiB,MAgCjB,aA/BgB,IAgChB,qBACA,cA1BkB,QA2BlB,QA1BY,QA4BZ,WnBEkB,QmBChB,MhB8MC,KgBtMH,oBACE,aAGF,mBACE,gBAQE,yFASE,MhBgLH,KgB5JD,4DAME,cACA,sBAEA,wHACE,gBAcJ,eAnFF,aA/BiB,MAgCjB,aA/BgB,IAgChB,qBACA,cA1BkB,QA2BlB,QA1BY,QA4BZ,WA8EmB,QA3EjB,MhB8MC,KgBtMH,4BACE,aAGF,2BACE,gBAQE,iKASE,MhBgLH,KgB5JD,4GAME,cACA,sBAEA,wKACE,gBAiBF,8BACE,MnBvGY,QmByGZ,wEAEE,MAzGqB,QA8G3B,chB1GF,cEqHY,IecZ,iBAjHF,kBACA,MACA,SACA,OACA,QACA,WjB4MO,KiB3MP,WA3CkB,gBA4ClB,aACA,aACA,OA0GE,qBAhGA,kBACA,aACA,kBACA,aACA,YACA,MACA,cf0EY,IezEZ,OAgDQ,iBjBqHH,KiBpHiB,QAxGH,QA0GP,sBAIZ,WA7GgB,wBAuGM,QAkDiB,SAjGvC,yCAuFA,qBAtFE,kBAIF,wFAGA,4DAEA,6DAIA,4CAyEA,qBAxEE,MA1EiB,IA2EjB,UlBpFM,SkBqFN,OACA,QACA,eA0CF,4CA0BA,qBAzBE,IA1HgB,WA+JhB,mCjBjJF,cEqHY,Ie6BV,iCjBlJF,cAiRa,OiB9HX,uCAtDoB,QAsD8B,EAvFpD,4CAwFE,+BAvFA,MAuF4C,IAtF5C,UlBpFM,SkBqFN,OACA,QACA,eALF,4CAyFE,iCAxFA,MAwF4C,IAvF5C,UlBpFM,SkBqFN,OACA,QACA,eALF,4CA0FE,mCAzFA,MAyF8C,IAxF9C,UlBpFM,SkBqFN,OACA,QACA,eALF,4CA2FE,iCA1FA,MA0F4C,IAzF5C,UlBpFM,SkBqFN,OACA,QACA,eALF,4CA4FE,mCA3FA,MA2F6C,IA1F7C,UlBpFM,SkBqFN,OACA,QACA,eAwFA,+BAEE,MACA,OACA,YACA,aACA,iBACA,0BACA,yBArGJ,4CA6FE,+BA5FA,MA6FoC,MA5FpC,UlBpFM,SkBqFN,OACA,QACA,eAmGA,6DA/CJ,UA5HuB,OA6HvB,cACA,kBACA,IA9HiB,QA+HjB,MA9HkB,SA+HlB,MjBgGM,KiB/FN,YtBrHiB,KsBsHjB,OrByKqB,QqB9HnB,OAEE,aAEA,kCAzJJ,kBACA,MACA,SACA,OACA,QACA,WjB4MO,KiB3MP,WA3CkB,gBA4ClB,aACA,aACA,OAoJI,aACE,cAKJ,aACE,qBACE,aACA,4BCvGJ,UAtDF,cACA,SACA,QhB8iCiB,QgB7iCjB,gBAhDmB,KAiDnB,oBAhDuB,QAiDvB,YvB1CuB,mDuB4CvB,aACE,OhB6iCmB,QgB5iCnB,UhBkjCiB,KgBjjCjB,YvBhCiB,OuBkCjB,4BACE,cACA,MrB/CgB,QqBgDhB,OAnDiB,EAoDjB,QAnDkB,iBAqDlB,oEAEE,WAzDiB,iBA0DjB,MhBqiCoB,QgBjiCxB,+CACE,MhB+hCuB,QgB9hCvB,YvBjDe,OuBkDf,YvBjEmB,mDuBoErB,qBACE,qBACA,SACA,UACA,gBACA,iBrB7CgB,QqBgDlB,qBACE,MrBzEgB,QqB4Ed,UhBghCa,KgB/gCb,YArEuB,KAwEzB,eAvE4B,UCmF9B,SA5DF,cACA,WACA,gBACA,OA7CoB,oBA8CpB,YA7CyB,OA+CzB,YACE,yBAGF,oCAGE,MnB+Nc,KmB9Nd,eACA,iBACA,gBACA,YxBrDqB,mDwBsDrB,YxBvCiB,OwBwCjB,UAxDgB,QAyDhB,MnB6KQ,KmB3KR,0CACE,gBAzDoB,KA0DpB,MnByKM,KmBxKN,QA1DY,cA2DZ,4DACE,MA1DmB,QA8DvB,+DnBzDA,cmBNoB,IAiElB,YxBtDe,OwBuDf,WtBlEgB,QsBmEhB,QApEY,cAqEZ,OAzDkB,QA0DlB,MnBkJG,KmBjJH,iFACE,WA/DkB,QC8FtB,MAnEF,WpBoLO,KoBnLP,cAToB,QAUpB,sBACA,aAba,KAeb,cACE,WA5Be,cA6Bf,MpB8LG,KoB5LD,UA7BoB,KA8BpB,YA7BsB,KAiC1B,YACE,WvBzBkB,QuB4BhB,oCAEE,QApDa,sBAqDb,UAxDe,QAyDf,YzB7CW,KyB8CX,MpB8KD,KoBzKL,YACE,WvBvCkB,QuB0ChB,oCAEE,QAlEa,sBAmEb,UAtEe,QAuEf,YzB3DW,KyB4DX,MpBgKD,KoB1JH,wBAEE,QA7Dc,iBA8Dd,UA7DgB,QA8DhB,MpBsJC,KoBrJD,WpByLY,KoBtLd,sDAEsB,WvBhEJ,QuBmEpB,sGAKQ,QAtEM,WAsEmB,YA1Ef,SCQhB,IAjBF,cACA,qBACA,sBACA,eACA,WAxBiB,yBrB0DjB,8BqBhCA,oBAEE,WA3BqB,8BAwCnB,WrB5BF,cEqHY,IoBGd,sCACA,wCACA,0CACA,4CAGE,yCACE,iDACA,mDACA,qDACA,wDAJF,mBACE,4CACA,8CACA,gDACA,mDAJF,gEACE,kDACA,oDACA,sDACA,yDAJF,4CACE,6CACA,+CACA,iDACA,oDAJF,gEACE,iDACA,mDACA,qDACA,wDAJF,4CACE,4CACA,8CACA,gDACA,mDAJF,iEACE,kDACA,oDACA,sDACA,yDAJF,4CACE,6CACA,+CACA,iDACA,oDAJF,uEACE,mDACA,qDACA,uDACA,0DAJF,6CACE,8CACA,gDACA,kDACA,qDA4BF,oEAmBE,SACA,UAIF,EACE,MzB7LgB,QyB8LhB,gBAvJmB,KAwJnB,oBAEA,gBAEE,MAzJkB,QA+JpB,kBAIF,EACE,YA5LkB,QA6LlB,Y3BpMe,O2BqMf,UA5LgB,KA6LhB,YA5LkB,IA6LlB,cA5LoB,QA6LpB,eAzLqB,mBA2LrB,OAlEJ,qBACA,gBAmEI,QACE,UAjMoB,QAkMpB,YAjMsB,KAkMtB,WAjMqB,OAsMzB,kBACE,Y3BnOc,8B2BoOd,Y3BtNe,O2BuNf,W3BvNe,O2BwNf,MtBKC,KsBJD,eAhPkB,mBAiPlB,WAnPc,MAoPd,cAnPiB,MAoPjB,YAtPe,IAwPf,sDACE,UA5NU,IA6NV,MA5NW,QA6NX,cAIJ,sBACA,uBACA,sBACA,sBACA,sBACA,kBAEA,WA/FF,YAjJsB,IAkJtB,MAjJqB,QAkJrB,Y3B/ImB,O2BgJnB,WAjJqB,MAkJrB,cAjJwB,MA8OtB,GACE,qBACA,qBACA,WACA,2BACA,SAIF,KAEE,kBACA,oBAGF,SAEE,Y3B9Pa,K2B+Pb,oBAGF,MACE,UAjQY,IAkQZ,oBAGF,KACE,Y3BtRkB,kC2BuRlB,Y3B1Qe,O2B2Qf,MtB/CC,KsBgDD,iBzBxLkB,QyByLlB,aAvPa,IAwPb,aAvPc,MAwPd,aAvPc,QAwPd,QAvPS,0BA2PX,SAGE,UA9QgB,KA+QhB,YA9QkB,IA+QlB,cA9QoB,QA+QpB,oBA9OgB,QA+OhB,YApRkB,QAuRpB,GACE,YpB7Ca,OoB8Cb,aACE,YAlPqB,EAoPnB,sCAEE,YArPS,QAsPT,gBACA,gBASJ,kBAEE,YAlQW,QAmQX,gBAMF,iEAGF,6CpB1Ea,OoB2Eb,6CpB3Ea,OoB4Eb,yCpB5Ea,OoB6Eb,6BAIF,GACE,YAtRqB,OAwRnB,kBAEE,YAxRW,QAyRX,gBAOJ,MACE,cA/R+B,MAgS/B,Y3BjVW,K2BmVb,oBAjS0B,OAqS5B,aAEE,yBACA,cACA,MzBjXgB,KyBkXhB,O1B5Dc,K0B8DhB,KACE,oBACA,YACE,cApSY,gBAyShB,WACE,mBACA,QAlTe,6BAmTf,YAlTc,eAoTd,gBACE,cACA,UArToB,SAsTpB,MArTqB,KAsTrB,uBACE,aAGF,4CAEE,MA5TmB,KAgUzB,wBAEE,YAlXkB,IAmXlB,MAvUkB,QA2UpB,OACE,qBACA,OAjUe,cAkUf,sBACA,QApUgB,eAsUhB,UACE,SACA,cAEF,WACE,Y3B3YW,K2B4YX,UAlUyB,SAuU3B,6B3BjZa,K2BmZb,aACE,O1BtHe,Q0BuHf,gBAjU2B,KAkU3B,Y3BtZW,K2BuZX,YACA,QAxUmB,WA6UvB,4CACE,8BAzbe,IA0bf,aApbS,QAqbT,aApbS,UAqbT,aApbS,UAqbT,aApbS,UAqbT,aApbS,SAqbT,aApbS,MA+bT,oCACA,aACE,EACE,oCACA,sBACA,2BACA,4BAGF,YACY,0BACZ,0CAEA,+CAGA,4DAEqB,WAErB,eAEE,sBACA,wBAGF,iCAEA,OACM,wBAEN,8BAEA,kBAEA,QAGE,UACA,SAGF,MACK,uBAEL,uCACA,qCACA,wCACA,4CCrRJ,mBACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BA7BN,4CACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BA7BN,4CACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BA7BN,4CACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BA7BN,6CACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BAaR,uCACqB,2BACrB,uCACqB,wBAInB,iDACsB,yBAGtB,iDACsB,sCAGtB,iDACsB,mCAGtB,2CACsB,6BAItB,sFACsB,8BAGxB,gDACE,uCACqB,2BACrB,uCACqB,wBAInB,iDACsB,yBAGtB,iDACsB,sCAGtB,iDACsB,mCAGtB,2CACsB,6BAItB,sFACsB,+BAI1B,+CACE,uCACsB,2BACtB,uCACsB,wBAIpB,iDACuB,yBAGvB,iDACuB,sCAGvB,iDACuB,mCAGvB,2CACuB,6BAIvB,sFACuB,+BAK3B,wCACA,2CACA,kDACA,+CAGA,8CACA,qDACA,2DACA,kEACA,wDACA,+DACA,+CACA,sDACA,gDACA,uDACA,gDACA,uDAIA,aACE,8BACA,6BAEA,8CACA,2DACA,wDACA,+CACA,gDACA,iDCzXJ,SAEI,mBACA,M3BgIa,Q2B7HjB,UACI,c3BoBkB,Q2BnBlB,M3B4HW,Q2BzHf,QACI,M3ByHS,Q2BtHb,QACI,M3BsHS,Q2BnHb,SACI,M3BmHU,Q2B3Gd,EACI,qBACA,kBACA,iBACA,aACA,sBAEA,kBAEJ,cAEI,iBACA,yBAEJ,0BAEI,wBAEJ,iCAGI,SACA,WAEJ,WACI,SACA,WACA,qCAWJ,kBACI,Y7BpEgB,8B6BqEhB,mBACA,UAEJ,GACI,U7BlDgB,Q6BmDhB,aAEJ,GACI,U7BrDgB,Q6BsDhB,qBAEA,eACI,aAER,GACI,U7B3DgB,Q6B4DhB,qBAEJ,GACI,U7B9DgB,O6B+DhB,qBAEJ,GACI,U7BjEgB,Q6BkEhB,iBAQJ,kBtByBgB,IsBxBZ,uBACkB,iCAClB,yBACkB,kCAClB,2BACkB,iCAEtB,OACI,sBAEJ,qEAEI,SAEJ,6BAEI,M3BlFkB,Q2BmFlB,Y7BxHqB,mD6ByHrB,mBACA,oBAEJ,iCAEI,iCACA,M3B1FkB,Q2B4FtB,6CAEI,gCACA,M3BhIkB,Q2BkItB,kBACI,mBACA,iBAQJ,GACI,mBAQJ,IACI,cACA,sBACA,YACA,iB3B1DoB,Q2B2DpB,ctB/BY,IsBiChB,SACI,oCACA,SAGJ,KACI,kBACA,gBAQJ,MACI,iBACA,UAEJ,GACI,cAGJ,WACI,gBACA,cAIA,YAEK,gBAOT,eACI,gBAEJ,GACI,iBACA,iBAIJ,8BACA,sEAOA,WACI,kBACA,kBACA,YACA,wBACA,M3BtLkB,Q2ByLlB,qC3B1LkB,Q2B4LlB,kBACI,0BACA,eACA,cACA,kBACA,WACA,SACA,M3BlMc,Q2BoMlB,iBACI,cACA,YACA,eACA,cACA,kBACA,YACA,YACA,M3B5Mc,Q2B8MlB,uBACI,aAEJ,4CACI,M3BnNc,Q2BqNtB,KACI,gBAGJ,eACI,mBAGJ,KACI,yBAQJ,aACI,eACA,SACA,yBAEJ,QACI,kBAEJ,YACI,kCAEJ,cACI,kCAIJ,mBACI,YACI,mBAGR,6CACI,YACI,qBASR,kB7B3SyB,mD6B4SzB,mB7B3SoB,8B6B6SpB,wB7BtRoB,Q6BuRpB,wB7BtRoB,Q6BuRpB,wB7BtRoB,Q6BuRpB,wB7BtRoB,O6BuRpB,wB7BtRoB,Q6BuRpB,uB7BzTiB,K6BgUjB,kBACI,WACA,kBACA,WACA,WACA,iBACA,gCAEJ,WACI,gBAEJ,cACI,U7BzSgB,K6B2SpB,aACI,kBACA,gBAUJ,WACE,uBACA,iCACA,wNAMF,+BACA,4BAGA,2CAEA,0rCAwDE,qBACF,uBACA,kBACA,mBACA,oBACA,cACA,wBACA,kCACA,oBACA,kCACA,mCACA,2BAGA,iCACA,iCACA,kCACA,gCACA,8BACA,+BACA,sCACA,sCACA,uCACA,oCACA,2CACA,2CACA,0CACA,+BACA,8BACA,6BACA,iCACA,8BACA,gCACA,6BACA,kCACA,iCACA,gCACA,+BACA,oCACA,+BACA,wCACA,8BACA,mCACA,mCACA,8BACA,kCACA,8BACA,iCACA,6BACA,iCACA,qCACA,mCACA,mCACA,gCACA,6BACA,oCACA,8BACA,uCACA,qCACA,mCACA,8BACA,gCACA,iCACA,yCACA,+BACA,+BACA,iCACA,8BACA,iCC9dA,gDACuC,gBACvC,wDACA,yLAUqB,WACrB,qCACA,2BAOA,YACI,8CACA,sCAEA,uEACI,mBASR,mBACE,aAQF,UACI,iB5B3CkB,Q4B6CtB,0BACI,iB5B9CkB,Q4BgDtB,oBACI,kBACA,mBACA,Y9BtDgB,8B8BuDhB,WACA,yBACA,qCAEJ,0BACI,aACA,yBAEJ,oCACI,gBASJ,yCAII,UACI,gBAEJ,UACI,aAEJ,uBACI,eAEJ,gCACI,eAEJ,oBACI,aACA,eACA,kBAKJ,oCACI,iBAQR,gEACI,UACI,gBAEJ,UACI,aAEJ,uBACI,eAEJ,gCACI,eAEJ,oBACI,eACA,aAEJ,oCACI,iBAQR,gEACI,UACI,gBAEJ,UACI,aAEJ,uBACI,eAEJ,gCACI,eAEJ,oBACI,aACA,gBAQR,4CACI,UACI,gBAEJ,UACI,aAEJ,uBACI,eAEJ,gCACI,eAEJ,oBACI,eACA,cAKR,mBACI,aAEJ,mBACI,aAEJ,yBACI,aAEJ,yBACI,aAQJ,YACI,mBACA,6BACA,gCAEJ,sBACE,iBAOF,wBACI,M5BhLkB,Q4BmLtB,mBACI,W5BpLkB,Q4BqLlB,SAEJ,mBACI,WAEJ,yBACI,W5BvNkB,Q4ByNtB,aACE,mBACA,cAEA,aACE,0BACA,cAEF,mBACE,qBACA,M5B9NkB,Q4BsOtB,WACI,sBAEJ,aACI,eACA,YACA,kBAEJ,mBACI,W5B3NkB,Q4BmOtB,qCAEI,mBACA,gBAGJ,QACI,iBACA,oBACA,W5BtOkB,Q4BuOlB,M5BpLkB,K4BuLlB,UACI,M5BrQc,Q4BuQlB,sBAEI,mBACA,WACA,yBAQR,WACI,W5BrPkB,Q4BsPlB,M5B3PkB,Q4B4PlB,iBAGJ,+BACI,WAGJ,WACI,M5BpQkB,Q4BqQlB,SACA,yBACA,iBACI,WAIR,cACI,8BAGF,iBACE,mBAEF,gBACE,oBACA,cACA,WACA,kBACA,M5BnRkB,Q4BoRlB,W5BzRkB,Q4B0RlB,kBACA,sBACE,W5BvRgB,Q4BwRhB,WAUN,gCACA,gCACA,gCACA,gCACA,gCACA,gCACA,gCACA,gCACA,gCAEA,mCACA,mCACA,mCACA,mCAEA,iCACA,kCAEA,mCACA,kCACA,oCACA,oCClWA,iCAGI,gBACA,iBAEJ,QACI,cACA,WxB3BW,KwBmCf,eACE,0BACA,gBACA,cxB+Gc,IwBvGhB,2CACA,0DACA,gEAOA,WACE,Y/BlCuB,mD+BmCvB,uCAEA,aACE,gBAEF,aACE,6BACA,WACA,8BAEF,mBACE,6BAEF,oBACE,W7BVkB,Q6BWlB,WACA,qBACA,Y/BlDoB,kC+BoDtB,4BACE,aACA,M7B/CkB,Q6BgDlB,WACA,sBAEF,gBACE,iB7BhCkB,Q6BiClB,uCACA,qBACA,M7BzBkB,Q6BiCtB,kCACE,oC7BpCoB,Q6BqCpB,0EAG0B,iB7BlCN,Q6ByCtB,4CACA,0CACA,kEACA,+E7B3DsB,Q6B6DtB,qC7BpDsB,Q6B2DtB,0CACA,8CACA,gDACA,gDACA,uDACA,uDAOA;AAAA;AAAA;AAAA,wBAIA,SACE,aAEF,aACI,UAEJ,aACI,+BACA,4BACA,2BACA,0BACA,uBACA,UAIF,sDACE,YACA,QACA,SAEA,cACA,iBACA,iBC3JJ,WACI,gBACA,+BACA,wBACA,cACA,iBACA,iBACA,yBAEA,2CACA,uDACA,+BACA,+BACA,4CACA,2CACA,4CACA,6DACA,gDACA,mDACA,iCACA,0BACA,0BACA,gDACA,mDACA,0BACA,0BACA,gCACA,0BACA,0BACA,gCACA,gCACA,gCACA,gCACA,2CACA,yBACA,yBACA,0BACA,6BACA,2CACA,0BACA,4BACA,2CACA,2CACA,0BACA,0BACA,0BACA,gCACA,yBACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,6BACA,0BACA,6BACA,0BACA,0BACA,0BACA,0BACA","sourcesContent":["@charset \"utf-8\";\n/* TOC – Typography variables\n\nModular Scale › http://www.modularscale.com//?16,36&px&1.25&web&table\n\n- Fonts\n- Font Weight\n- Font Size Variables\n\n*/\n\n@import \"functions\"; // Allows the use of rem-calc() or lower-bound() in your settings\n\n\n\n/* Fonts\n------------------------------------------------------------------- */\n\n$base-font-size: 16px;\n$rem-base: $base-font-size;\n// $base-line-height is 24px while $base-font-size is 16px\n$base-line-height: 1.5 !default;\n\n\n$font-family-sans-serif: \"Lato\", \"Helvetica Neue\", Helvetica, Arial, sans-serif;\n$font-family-serif: \"Volkhov\", Georgia, Times, serif;\n$font-family-monospace: \"Lucida Console\", Monaco, monospace;\n\n$body-font-family: $font-family-sans-serif;\n$body-font-weight: normal;\n$body-font-style: normal;\n\n$header-font-family: $font-family-serif;\n\n\n\n/* Font Weight\n------------------------------------------------------------------- */\n\n$font-weight-normal: normal;\n$font-weight-bold: bold;\n\n\n\n/* Font Size Variables\n------------------------------------------------------------------- */\n\n$font-size-p:    \t$base-font-size;\n$font-size-h1:      2.441em;\n$font-size-h2:      1.953em;\n$font-size-h3:      1.563em;\n$font-size-h4:      1.25em;\n$font-size-h5:      1.152em;\n$font-size-small:   0.8em;\n\n.font-size-h1   { font-size: $font-size-h1; }\n.font-size-h2   { font-size: $font-size-h2; }\n.font-size-h3   { font-size: $font-size-h3; }\n.font-size-h4   { font-size: $font-size-h4; }\n.font-size-h5   { font-size: $font-size-h5; }\n","@charset \"utf-8\";\n// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n//\n// Foundation Variables\n//\n\n// Data attribute namespace\n// styles get applied to [data-mysite-plugin], etc\n$namespace: false !default;\n\n// The default font-size is set to 100% of the browser style sheet (usually 16px)\n// for compatibility with browser-based text zoom or user-set defaults.\n\n// Since the typical default browser font-size is 16px, that makes the calculation for grid size.\n// If you want your base font-size to be different and not have it affect the grid breakpoints,\n// set $rem-base to $base-font-size and make sure $base-font-size is a px value.\n$base-font-size: 100% !default;\n\n\n\n//\n// Global Foundation Mixins\n//\n\n// @mixins\n//\n// We use this to control border radius.\n// $radius - Default: $global-radius || 4px\n@mixin radius($radius: $global-radius) {\n  @if $radius {\n    border-radius: $radius;\n  }\n}\n\n// @mixins\n//\n// We use this to create equal side border radius on elements.\n// $side - Options: left, right, top, bottom\n@mixin side-radius($side, $radius: $global-radius) {\n  @if ($side ==left or $side ==right) {\n    -webkit-border-bottom-#{$side}-radius: $radius;\n    -webkit-border-top-#{$side}-radius: $radius;\n    border-bottom-#{$side}-radius: $radius;\n    border-top-#{$side}-radius: $radius;\n  }\n\n  @else {\n    -webkit-#{$side}-left-radius: $radius;\n    -webkit-#{$side}-right-radius: $radius;\n    border-#{$side}-left-radius: $radius;\n    border-#{$side}-right-radius: $radius;\n  }\n}\n\n// @mixins\n//\n// We can control whether or not we have inset shadows edges.\n// $active - Default: true, Options: false\n@mixin inset-shadow($active: true) {\n  box-shadow: $shiny-edge-size $shiny-edge-color inset;\n\n  @if $active {\n    &:active {\n      box-shadow: $shiny-edge-size $shiny-edge-active-color inset;\n    }\n  }\n}\n\n// @mixins\n//\n// We use this to add transitions to elements\n// $property - Default: all, Options: http://www.w3.org/TR/css3-transitions/#animatable-properties\n// $speed - Default: 300ms\n// $ease - Default:ease-out, Options: http://css-tricks.com/almanac/properties/t/transition-timing-function/\n@mixin single-transition($property: all, $speed: 300ms, $ease: ease-out) {\n  transition: $property $speed $ease;\n}\n\n// @mixins\n//\n// We use this to add box-sizing across browser prefixes\n@mixin box-sizing($type: border-box) {\n  -webkit-box-sizing: $type; // Android < 2.3, iOS < 4\n  -moz-box-sizing: $type; // Firefox < 29\n  box-sizing: $type; // Chrome, IE 8+, Opera, Safari 5.1\n}\n\n// @mixins\n//\n// We use this to create isosceles triangles\n// $triangle-size - Used to set border-size. No default, set a px or em size.\n// $triangle-color - Used to set border-color which makes up triangle. No default\n// $triangle-direction - Used to determine which direction triangle points. Options: top, bottom, left, right\n@mixin css-triangle($triangle-size, $triangle-color, $triangle-direction) {\n  content: \"\";\n  display: block;\n  width: 0;\n  height: 0;\n  border: inset $triangle-size;\n\n  @if ($triangle-direction ==top) {\n    border-color: $triangle-color transparent transparent transparent;\n    border-top-style: solid;\n  }\n\n  @if ($triangle-direction ==bottom) {\n    border-color: transparent transparent $triangle-color transparent;\n    border-bottom-style: solid;\n  }\n\n  @if ($triangle-direction ==left) {\n    border-color: transparent transparent transparent $triangle-color;\n    border-left-style: solid;\n  }\n\n  @if ($triangle-direction ==right) {\n    border-color: transparent $triangle-color transparent transparent;\n    border-right-style: solid;\n  }\n}\n\n// @mixins\n//\n// We use this to create the icon with three lines aka the hamburger icon, the menu-icon or the navicon\n// $width - Width of hamburger icon in rem\n// $left - If false, icon will be centered horizontally || explicitly set value in rem\n// $top - If false, icon will be centered vertically || explicitly set value in rem\n// $thickness - thickness of lines in hamburger icon, set value in px\n// $gap - spacing between the lines in hamburger icon, set value in px\n// $color - icon color\n// $hover-color - icon color during hover\n// $offcanvas - Set to true of @include in offcanvas\n@mixin hamburger($width, $left, $top, $thickness, $gap, $color, $hover-color, $offcanvas) {\n  span::after {\n    content: \"\";\n    position: absolute;\n    display: block;\n    height: 0;\n\n    @if $offcanvas {\n      @if $top {\n        top: $top;\n      }\n\n      @else {\n        top: 50%;\n        margin-top: (-$width/2);\n      }\n\n      @if $left {\n        left: $left;\n      }\n\n      @else {\n        left: ($tabbar-menu-icon-width - $width)/2;\n      }\n    }\n\n    @else {\n      top: 50%;\n      margin-top: -($width/2);\n      #{$opposite-direction}: $topbar-link-padding;\n    }\n\n    box-shadow: 0 0 0 $thickness $color,\n    0 ($gap + $thickness) 0 $thickness $color,\n    0 (2 * $gap + 2*$thickness) 0 $thickness $color;\n    width: $width;\n  }\n\n  span:hover:after {\n    box-shadow:\n      0 0 0 $thickness $hover-color,\n      0 $gap + $thickness 0 $thickness $hover-color,\n      0 (2 * $gap + 2*$thickness) 0 $thickness $hover-color;\n  }\n}\n\n// We use this to do clear floats\n@mixin clearfix {\n\n  &:before,\n  &:after {\n    content: \" \";\n    display: table;\n  }\n\n  &:after {\n    clear: both;\n  }\n}\n\n// @mixins\n//\n// We use this to add a glowing effect to block elements\n// $selector - Used for selector state. Default: focus, Options: hover, active, visited\n// $fade-time - Default: 300ms\n// $glowing-effect-color - Default: fade-out($primary-color, .25)\n@mixin block-glowing-effect($selector: focus, $fade-time: 300ms, $glowing-effect-color: fade-out($primary-color, .25)) {\n  transition: box-shadow $fade-time, border-color $fade-time ease-in-out;\n\n  &:#{$selector} {\n    box-shadow: 0 0 5px $glowing-effect-color;\n    border-color: $glowing-effect-color;\n  }\n}\n\n// @mixins\n//\n// We use this to translate elements in 2D\n// $horizontal: Default: 0\n// $vertical: Default: 0\n@mixin translate2d($horizontal: 0, $vertical: 0) {\n  transform: translate($horizontal, $vertical)\n}\n\n// @mixins\n//\n// Makes an element visually hidden, but accessible.\n// @see http://snook.ca/archives/html_and_css/hiding-content-for-accessibility\n@mixin element-invisible {\n  position: absolute !important;\n  height: 1px;\n  width: 1px;\n  overflow: hidden;\n  clip: rect(1px, 1px, 1px, 1px);\n}\n\n// @mixins\n//\n// Turns off the element-invisible effect.\n@mixin element-invisible-off {\n  position: static !important;\n  height: auto;\n  width: auto;\n  overflow: visible;\n  clip: auto;\n}\n\n\n// We use these to control text direction settings\n$text-direction: ltr !default;\n$default-float: left !default;\n$opposite-direction: right !default;\n\n@if $text-direction ==ltr {\n  $default-float: left;\n  $opposite-direction: right;\n}\n\n@else {\n  $default-float: right;\n  $opposite-direction: left;\n}\n\n// We use these to control inset shadow shiny edges and depressions.\n$shiny-edge-size: 0 1px 0 !default;\n$shiny-edge-color: rgba(#fff, .5) !default;\n$shiny-edge-active-color: rgba(#000, .2) !default;\n\n// We use this to control whether or not CSS classes come through in the gem files.\n$include-html-classes: true !default;\n$include-print-styles: true !default;\n$include-html-global-classes: $include-html-classes !default;\n\n$column-gutter: rem-calc(30) !default;\n\n\n\n\n// d. Media Query Ranges\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n$small-range: (\n  0em,\n  40em\n);\n$medium-range: (\n  40.063em,\n  64em\n);\n$large-range: (\n  64.063em,\n  90em\n);\n$xlarge-range: (\n  90.063em,\n  120em\n);\n$xxlarge-range: (\n  120.063em,\n  99999999em\n);\n\n\n$screen: \"only screen\" !default;\n\n$landscape: \"#{$screen} and (orientation: landscape)\" !default;\n$portrait: \"#{$screen} and (orientation: portrait)\" !default;\n\n$small-up: $screen !default;\n$small-only: \"#{$screen} and (max-width: #{upper-bound($small-range)})\";\n\n$medium-up: \"#{$screen} and (min-width:#{lower-bound($medium-range)})\" !default;\n$medium-only: \"#{$screen} and (min-width:#{lower-bound($medium-range)}) and (max-width:#{upper-bound($medium-range)})\" !default;\n\n$large-up: \"#{$screen} and (min-width:#{lower-bound($large-range)})\" !default;\n$large-only: \"#{$screen} and (min-width:#{lower-bound($large-range)}) and (max-width:#{upper-bound($large-range)})\" !default;\n\n$xlarge-up: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)})\" !default;\n$xlarge-only: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)}) and (max-width:#{upper-bound($xlarge-range)})\" !default;\n\n$xxlarge-up: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)})\" !default;\n$xxlarge-only: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)}) and (max-width:#{upper-bound($xxlarge-range)})\" !default;\n\n// Legacy\n$small: $medium-up;\n$medium: $medium-up;\n$large: $large-up;\n\n//We use this as cursors values for enabling the option of having custom cursors in the whole site's stylesheet\n$cursor-auto-value: auto !default;\n$cursor-crosshair-value: crosshair !default;\n$cursor-default-value: default !default;\n$cursor-pointer-value: pointer !default;\n$cursor-help-value: help !default;\n$cursor-text-value: text !default;\n\n\n@include exports(\"global\") {\n\n  // Meta styles are included in all builds, as they are a dependency of the Javascript.\n  // Used to provide media query values for javascript components.\n  // Forward slash placed around everything to convince PhantomJS to read the value.\n\n  meta.foundation-version {\n    font-family: \"/5.5.0/\";\n  }\n\n  meta.foundation-mq-small {\n    font-family: \"/\" + unquote($small-up) + \"/\";\n    width: lower-bound($small-range);\n  }\n\n  meta.foundation-mq-small-only {\n    font-family: \"/\" + unquote($small-only) + \"/\";\n    width: lower-bound($small-range);\n  }\n\n  meta.foundation-mq-medium {\n    font-family: \"/\" + unquote($medium-up) + \"/\";\n    width: lower-bound($medium-range);\n  }\n\n  meta.foundation-mq-medium-only {\n    font-family: \"/\" + unquote($medium-only) + \"/\";\n    width: lower-bound($medium-range);\n  }\n\n  meta.foundation-mq-large {\n    font-family: \"/\" + unquote($large-up) + \"/\";\n    width: lower-bound($large-range);\n  }\n\n  meta.foundation-mq-large-only {\n    font-family: \"/\" + unquote($large-only) + \"/\";\n    width: lower-bound($large-range);\n  }\n\n  meta.foundation-mq-xlarge {\n    font-family: \"/\" + unquote($xlarge-up) + \"/\";\n    width: lower-bound($xlarge-range);\n  }\n\n  meta.foundation-mq-xlarge-only {\n    font-family: \"/\" + unquote($xlarge-only) + \"/\";\n    width: lower-bound($xlarge-range);\n  }\n\n  meta.foundation-mq-xxlarge {\n    font-family: \"/\" + unquote($xxlarge-up) + \"/\";\n    width: lower-bound($xxlarge-range);\n  }\n\n  meta.foundation-data-attribute-namespace {\n    font-family: #{$namespace};\n  }\n\n  @if $include-html-global-classes {\n\n    // Must be 100% for off canvas to work\n    html,\n    body {\n      height: 100%;\n    }\n\n    // Set box-sizing globally to handle padding and border widths\n    *,\n    *:before,\n    *:after {\n      @include box-sizing(border-box);\n    }\n\n    html,\n    body {\n      font-size: $base-font-size;\n    }\n\n    // Default body styles\n    body {\n      background: $body-bg;\n      color: $body-font-color;\n      padding: 0;\n      margin: 0;\n      font-family: $body-font-family;\n      font-weight: $body-font-weight;\n      font-style: $body-font-style;\n      line-height: $base-line-height; // Set to $base-line-height to take on browser default of 150%\n      position: relative;\n      cursor: $cursor-auto-value;\n    }\n\n    a:hover {\n      cursor: $cursor-pointer-value;\n    }\n\n    // Grid Defaults to get images and embeds to work properly\n    img {\n      max-width: 100%;\n      height: auto;\n    }\n\n    img {\n      -ms-interpolation-mode: bicubic;\n    }\n\n    #map_canvas,\n    .map_canvas {\n\n      img,\n      embed,\n      object {\n        max-width: none !important;\n      }\n    }\n\n    // Miscellaneous useful HTML classes\n    .left {\n      float: left !important;\n    }\n\n    .right {\n      float: right !important;\n    }\n\n    .clearfix {\n      @include clearfix;\n    }\n\n    // Hide visually and from screen readers\n    .hide {\n      display: none !important;\n      visibility: hidden;\n    }\n\n    // Hide visually and from screen readers, but maintain layout\n    .invisible {\n      visibility: hidden;\n    }\n\n    // Font smoothing\n    // Antialiased font smoothing works best for light text on a dark background.\n    // Apply to single elements instead of globally to body.\n    // Note this only applies to webkit-based desktop browsers and Firefox 25 (and later) on the Mac.\n    .antialiased {\n      -webkit-font-smoothing: antialiased;\n      -moz-osx-font-smoothing: grayscale;\n    }\n\n    // Get rid of gap under images by making them display: inline-block; by default\n    img {\n      display: inline-block;\n      vertical-align: middle;\n    }\n\n    //\n    // Global resets for forms\n    //\n\n    // Make sure textarea takes on height automatically\n    textarea {\n      height: auto;\n      min-height: 50px;\n    }\n\n    // Make select elements 100% width by default\n    select {\n      width: 100%;\n    }\n  }\n}","@charset \"utf-8\";\n/* TOC – Color Variables\n\n- Basics\n- Corporate Identity Colorpalette\n- Foundation Color Variables\n- Grey Scale\n- Topbar-Navigation\n- Footer\n- Code\n\n*/\n\n\n\n/* Basics\n------------------------------------------------------------------- */\n\n$text-color         : #111;\n$body-font-color    : $text-color;\n$body-bg            : #fdfdfd;\n\n\n\n/* Corporate Identity Colorpalette\n   https://color.adobe.com/de/Flat-Design-Colors-v2-color-theme-4341903/\n------------------------------------------------------------------- */\n\n$ci-1               : #334D5C; // dark turquoise\n$ci-2               : #45B29D; // turquoise\n$ci-3               : #EFC94C; // yellow\n$ci-4               : #be6409; // dark orange\n$ci-5               : #DF4949; // red\n$ci-6               : #A1D044; // green\n\n\n\n/* Foundation Color Variables\n------------------------------------------------------------------- */\n\n$primary-color      : $ci-1;\n$secondary-color    : $ci-6;\n$alert-color        : $ci-5;\n$success-color      : $ci-6;\n$warning-color      : $ci-4;\n$info-color         : $ci-1;\n\n\n\n/* Grey Scale\n------------------------------------------------------------------- */\n\n$grey-1             : #E4E4E4;\n$grey-2             : #D7D7D7;\n$grey-3             : #CBCBCB;\n$grey-4             : #BEBEBE;\n$grey-5             : #A4A4A4;\n$grey-6             : #979797;\n$grey-7             : #8B8B8B;\n$grey-8             : #7E7E7E;\n$grey-9             : #646464;\n$grey-10            : #575757;\n$grey-11            : #4B4B4B;\n$grey-12            : #3E3E3E;\n$grey-13            : #313131;\n$grey-14            : #242424;\n$grey-15            : #171717;\n$grey-16            : #0B0B0B;\n\n\n\n/* Topbar-Navigation\n------------------------------------------------------------------- */\n\n$topbar-bg-color    : $body-bg;\n$topbar-bg          : $topbar-bg-color;\n\n\n$topbar-dropdown-toggle-color: $ci-1;\n\n$topbar-link-color  : #000;\n$topbar-link-color-hover: #000;\n$topbar-link-color-active: #000;\n$topbar-link-color-active-hover: #000;\n\n$topbar-dropdown-label-color: $ci-2;\n$topbar-dropdown-link-bg-hover: $ci-6;\n\n$topbar-link-bg-active: $ci-6; // Active Navigation Link\n$topbar-link-bg-hover: $ci-6;\n$topbar-link-bg-active-hover: $ci-2;\n\n\n$topbar-dropdown-bg: $ci-6; // Background Mobile Navigation\n$topbar-dropdown-link-color: #000;\n$topbar-dropdown-link-bg: $ci-2;\n\n$topbar-menu-link-color-toggled: $ci-1;\n$topbar-menu-icon-color-toggled: $ci-1;\n$topbar-menu-link-color: #000;\n$topbar-menu-icon-color: #000;\n$topbar-menu-link-color-toggled: $ci-6;\n$topbar-menu-icon-color-toggled: $ci-6;\n\n\n\n/* Footer\n------------------------------------------------------------------- */\n\n$footer-bg          : $grey-8;\n$footer-color       : #fff;\n$footer-link-color  : $ci-6;\n\n\n$subfooter-bg       : $grey-13;\n$subfooter-color    : $grey-8;\n$subfooter-link-color: $grey-8;\n\n\n\n/* Code\n------------------------------------------------------------------- */\n\n$code-background-color: scale-color($secondary-color, $lightness: 70%);\n\n$highlight-background: #ffffff;\n$highlight-comment: #999988;\n$highlight-error: #a61717;\n$highlight-comment-special: #999999;\n$highlight-deleted: #000000;\n$highlight-error-2: #aa0000;\n$highlight-literal-string: #d14;\n$highlight-literal-number: #009999;\n$highlight-name-attribut: #008080;\n$highlight-error-background: #e3d2d2;\n$highlight-generic-deleted: #ffdddd;\n$highlight-generic-deleted-specific: #ffaaaa;\n$highlight-generic-inserted: #ddffdd;\n$highlight-generic-inserted-specific: #aaffaa;\n$highlight-generic-output: #888888;\n$highlight-generic-prompt: #555555;\n$highlight-subheading: #aaaaaa;\n$highlight-keyword-type: #445588;\n$highlight-name-builtin: #0086B3;\n$highlight-name-class: #445588;\n$highlight-name-entity: #800080;\n$highlight-name-exception: #990000;\n$highlight-name-function: #990000;\n$highlight-name-namespace: #555555;\n$highlight-name-tag: #000080;\n$highlight-text-whitespace: #bbbbbb;\n$highlight-literal-string-regex: #009926;\n$highlight-literal-string-symbol: #990073;\n\n\n/* links\n------------------------------------------------------------------- */\n$link-unvisited: #0921e2;\n$link-visited: #071582;\n$link-hover: darken( $link-unvisited, 10% );\n$link-focus: lighten( $link-unvisited, 20% );\n$link-active: darken( $link-unvisited, 20% );\n","@charset \"utf-8\";\n/*! normalize.css v3.0.2 | MIT License | git.io/normalize */\n\n/**\n * 1. Set default font family to sans-serif.\n * 2. Prevent iOS text size adjust after orientation change, without disabling\n *    user zoom.\n */\n\nhtml {\n  font-family: sans-serif; /* 1 */\n  -ms-text-size-adjust: 100%; /* 2 */\n  -webkit-text-size-adjust: 100%; /* 2 */\n}\n\n/**\n * Remove default margin.\n */\n\nbody {\n  margin: 0;\n}\n\n/* HTML5 display definitions\n   ========================================================================== */\n\n/**\n * Correct `block` display not defined for any HTML5 element in IE 8/9.\n * Correct `block` display not defined for `details` or `summary` in IE 10/11\n * and Firefox.\n * Correct `block` display not defined for `main` in IE 11.\n */\n\narticle,\naside,\ndetails,\nfigcaption,\nfigure,\nfooter,\nheader,\nhgroup,\nmain,\nmenu,\nnav,\nsection,\nsummary {\n  display: block;\n}\n\n/**\n * 1. Correct `inline-block` display not defined in IE 8/9.\n * 2. Normalize vertical alignment of `progress` in Chrome, Firefox, and Opera.\n */\n\naudio,\ncanvas,\nprogress,\nvideo {\n  display: inline-block; /* 1 */\n  vertical-align: baseline; /* 2 */\n}\n\n/**\n * Prevent modern browsers from displaying `audio` without controls.\n * Remove excess height in iOS 5 devices.\n */\n\naudio:not([controls]) {\n  display: none;\n  height: 0;\n}\n\n/**\n * Address `[hidden]` styling not present in IE 8/9/10.\n * Hide the `template` element in IE 8/9/11, Safari, and Firefox < 22.\n */\n\n[hidden],\ntemplate {\n  display: none;\n}\n\n/* Links\n   ========================================================================== */\n\n/**\n * Remove the gray background color from active links in IE 10.\n */\n\na {\n  background-color: transparent;\n}\n\n/**\n * Improve readability when focused and also mouse hovered in all browsers.\n */\n\na:active,\na:hover {\n  outline: 0;\n}\n\n/* Text-level semantics\n   ========================================================================== */\n\n/**\n * Address styling not present in IE 8/9/10/11, Safari, and Chrome.\n */\n\nabbr[title] {\n  border-bottom: 1px dotted;\n}\n\n/**\n * Address style set to `bolder` in Firefox 4+, Safari, and Chrome.\n */\n\nb,\nstrong {\n  font-weight: bold;\n}\n\n/**\n * Address styling not present in Safari and Chrome.\n */\n\ndfn {\n  font-style: italic;\n}\n\n/**\n * Address variable `h1` font-size and margin within `section` and `article`\n * contexts in Firefox 4+, Safari, and Chrome.\n */\n\nh1 {\n  font-size: 2em;\n  margin: 0.67em 0;\n}\n\n/**\n * Address styling not present in IE 8/9.\n */\n\nmark {\n  background: #ff0;\n  color: #000;\n}\n\n/**\n * Address inconsistent and variable font size in all browsers.\n */\n\nsmall {\n  font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` affecting `line-height` in all browsers.\n */\n\nsub,\nsup {\n  font-size: 75%;\n  line-height: 0;\n  position: relative;\n  vertical-align: baseline;\n}\n\nsup {\n  top: -0.5em;\n}\n\nsub {\n  bottom: -0.25em;\n}\n\n/* Embedded content\n   ========================================================================== */\n\n/**\n * Remove border when inside `a` element in IE 8/9/10.\n */\n\nimg {\n  border: 0;\n}\n\n/**\n * Correct overflow not hidden in IE 9/10/11.\n */\n\nsvg:not(:root) {\n  overflow: hidden;\n}\n\n/* Grouping content\n   ========================================================================== */\n\n/**\n * Address margin not present in IE 8/9 and Safari.\n */\n\nfigure {\n  margin: 1em 40px;\n}\n\n/**\n * Address differences between Firefox and other browsers.\n */\n\nhr {\n  -moz-box-sizing: content-box;\n  box-sizing: content-box;\n  height: 0;\n}\n\n/**\n * Contain overflow in all browsers.\n */\n\npre {\n  overflow: auto;\n}\n\n/**\n * Address odd `em`-unit font size rendering in all browsers.\n */\n\ncode,\nkbd,\npre,\nsamp {\n  font-family: monospace, monospace;\n  font-size: 1em;\n}\n\n/* Forms\n   ========================================================================== */\n\n/**\n * Known limitation: by default, Chrome and Safari on OS X allow very limited\n * styling of `select`, unless a `border` property is set.\n */\n\n/**\n * 1. Correct color not being inherited.\n *    Known issue: affects color of disabled elements.\n * 2. Correct font properties not being inherited.\n * 3. Address margins set differently in Firefox 4+, Safari, and Chrome.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n  color: inherit; /* 1 */\n  font: inherit; /* 2 */\n  margin: 0; /* 3 */\n}\n\n/**\n * Address `overflow` set to `hidden` in IE 8/9/10/11.\n */\n\nbutton {\n  overflow: visible;\n}\n\n/**\n * Address inconsistent `text-transform` inheritance for `button` and `select`.\n * All other form control elements do not inherit `text-transform` values.\n * Correct `button` style inheritance in Firefox, IE 8/9/10/11, and Opera.\n * Correct `select` style inheritance in Firefox.\n */\n\nbutton,\nselect {\n  text-transform: none;\n}\n\n/**\n * 1. Avoid the WebKit bug in Android 4.0.* where (2) destroys native `audio`\n *    and `video` controls.\n * 2. Correct inability to style clickable `input` types in iOS.\n * 3. Improve usability and consistency of cursor style between image-type\n *    `input` and others.\n */\n\nbutton,\nhtml input[type=\"button\"], /* 1 */\ninput[type=\"reset\"],\ninput[type=\"submit\"] {\n  -webkit-appearance: button; /* 2 */\n  cursor: pointer; /* 3 */\n}\n\n/**\n * Re-set default cursor for disabled elements.\n */\n\nbutton[disabled],\nhtml input[disabled] {\n  cursor: default;\n}\n\n/**\n * Remove inner padding and border in Firefox 4+.\n */\n\nbutton::-moz-focus-inner,\ninput::-moz-focus-inner {\n  border: 0;\n  padding: 0;\n}\n\n/**\n * Address Firefox 4+ setting `line-height` on `input` using `!important` in\n * the UA stylesheet.\n */\n\ninput {\n  line-height: normal;\n}\n\n/**\n * It's recommended that you don't attempt to style these elements.\n * Firefox's implementation doesn't respect box-sizing, padding, or width.\n *\n * 1. Address box sizing set to `content-box` in IE 8/9/10.\n * 2. Remove excess padding in IE 8/9/10.\n */\n\ninput[type=\"checkbox\"],\ninput[type=\"radio\"] {\n  box-sizing: border-box; /* 1 */\n  padding: 0; /* 2 */\n}\n\n/**\n * Fix the cursor style for Chrome's increment/decrement buttons. For certain\n * `font-size` values of the `input`, it causes the cursor style of the\n * decrement button to change from `default` to `text`.\n */\n\ninput[type=\"number\"]::-webkit-inner-spin-button,\ninput[type=\"number\"]::-webkit-outer-spin-button {\n  height: auto;\n}\n\n/**\n * 1. Address `appearance` set to `searchfield` in Safari and Chrome.\n * 2. Address `box-sizing` set to `border-box` in Safari and Chrome\n *    (include `-moz` to future-proof).\n */\n\ninput[type=\"search\"] {\n  -webkit-appearance: textfield; /* 1 */\n  -moz-box-sizing: content-box;\n  -webkit-box-sizing: content-box; /* 2 */\n  box-sizing: content-box;\n}\n\n/**\n * Remove inner padding and search cancel button in Safari and Chrome on OS X.\n * Safari (but not Chrome) clips the cancel button when the search input has\n * padding (and `textfield` appearance).\n */\n\ninput[type=\"search\"]::-webkit-search-cancel-button,\ninput[type=\"search\"]::-webkit-search-decoration {\n  -webkit-appearance: none;\n}\n\n/**\n * Define consistent border, margin, and padding.\n */\n\nfieldset {\n  border: 1px solid #c0c0c0;\n  margin: 0 2px;\n  padding: 0.35em 0.625em 0.75em;\n}\n\n/**\n * 1. Correct `color` not being inherited in IE 8/9/10/11.\n * 2. Remove padding so people aren't caught out if they zero out fieldsets.\n */\n\nlegend {\n  border: 0; /* 1 */\n  padding: 0; /* 2 */\n}\n\n/**\n * Remove default vertical scrollbar in IE 8/9/10/11.\n */\n\ntextarea {\n  overflow: auto;\n}\n\n/**\n * Don't inherit the `font-weight` (applied by a rule above).\n * NOTE: the default cannot safely be changed in Chrome and Safari on OS X.\n */\n\noptgroup {\n  font-weight: bold;\n}\n\n/* Tables\n   ========================================================================== */\n\n/**\n * Remove most spacing between table cells.\n */\n\ntable {\n  border-collapse: collapse;\n  border-spacing: 0;\n}\n\ntd,\nth {\n  padding: 0;\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-grid-classes: $include-html-classes !default;\n$include-xl-html-grid-classes: false !default;\n\n$row-width: rem-calc(1500) !default;\n$total-columns: 12 !default;\n\n$last-child-float: $opposite-direction !default;\n\n//\n// Grid Functions\n//\n\n// Deprecated: We'll drop support for this in 5.1, use grid-calc()\n@function gridCalc($colNumber, $totalColumns) {\n  @warn \"gridCalc() is deprecated, use grid-calc()\";\n  @return grid-calc($colNumber, $totalColumns);\n}\n\n// @FUNCTION\n// $colNumber - Found in settings file\n// $totalColumns - Found in settings file\n@function grid-calc($colNumber, $totalColumns) {\n  @return percentage(calc($colNumber / $totalColumns));\n}\n\n//\n// @mixins\n//\n\n// For creating container, nested, and collapsed rows.\n//\n//\n// $behavior - Any special behavior for this row? Default: false. Options: nest, collapse, nest-collapse, false.\n@mixin grid-row($behavior: false) {\n\n  // use @include grid-row(nest); to include a nested row\n  @if $behavior ==nest {\n    width: auto;\n    margin-#{$default-float}: - calc($column-gutter/2);\n    margin-#{$opposite-direction}: - calc($column-gutter/2);\n    margin-top: 0;\n    margin-bottom: 0;\n    max-width: none;\n  }\n\n  // use @include grid-row(collapse); to collapsed a container row margins\n  @else if $behavior ==collapse {\n    width: 100%;\n    margin: 0;\n    max-width: $row-width;\n  }\n\n  // use @include grid-row(nest-collapse); to collapse outer margins on a nested row\n  @else if $behavior ==nest-collapse {\n    width: auto;\n    margin: 0;\n    max-width: none;\n  }\n\n  // use @include grid-row; to use a container row\n  @else {\n    width: 100%;\n    margin-#{$default-float}: auto;\n    margin-#{$opposite-direction}: auto;\n    margin-top: 0;\n    margin-bottom: 0;\n    max-width: $row-width;\n  }\n\n  // Clearfix for all rows\n  @include clearfix();\n}\n\n// Creates a column, should be used inside of a media query to control layouts\n//\n// $columns - The number of columns this should be\n// $last-column - Is this the last column? Default: false.\n// $center - Center these columns? Default: false.\n// $offset - # of columns to offset. Default: false.\n// $push - # of columns to push. Default: false.\n// $pull - # of columns to pull. Default: false.\n// $collapse - Get rid of gutter padding on column? Default: false.\n// $float - Should this float? Default: true. Options: true, false, left, right.\n@mixin grid-column($columns: false,\n  $last-column: false,\n  $center: false,\n  $offset: false,\n  $push: false,\n  $pull: false,\n  $collapse: false,\n  $float: true,\n  $position: false) {\n\n  // If positioned for default .column, include relative position\n  // push and pull require position set\n  @if $position or $push or $pull {\n    position: relative;\n  }\n\n  // If collapsed, get rid of gutter padding\n  @if $collapse {\n    padding-left: 0;\n    padding-right: 0;\n  }\n\n  // Gutter padding whenever a column isn't set to collapse\n  // (use $collapse:null to do nothing)\n  @else if $collapse ==false {\n    padding-left: calc($column-gutter / 2);\n    padding-right: calc($column-gutter / 2);\n  }\n\n  // If a column number is given, calculate width\n  @if $columns {\n    width: grid-calc($columns, $total-columns);\n\n    // If last column, float naturally instead of to the right\n    @if $last-column {\n      float: $opposite-direction;\n    }\n  }\n\n  // Source Ordering, adds left/right depending on which you use.\n  @if $push {\n    #{$default-float}: grid-calc($push, $total-columns);\n    #{$opposite-direction}: auto;\n  }\n\n  @if $pull {\n    #{$opposite-direction}: grid-calc($pull, $total-columns);\n    #{$default-float}: auto;\n  }\n\n  @if $float {\n    @if $float ==left or $float ==true {\n      float: $default-float;\n    }\n\n    @else if $float ==right {\n      float: $opposite-direction;\n    }\n\n    @else {\n      float: none;\n    }\n  }\n\n  // If centered, get rid of float and add appropriate margins\n  @if $center {\n    margin-#{$default-float}: auto;\n    margin-#{$opposite-direction}: auto;\n    float: none;\n  }\n\n  // If offset, calculate appropriate margins\n  @if $offset {\n    margin-#{$default-float}: grid-calc($offset, $total-columns) !important;\n  }\n\n}\n\n// Create presentational classes for grid\n//\n// $size - Name of class to use, i.e. \"large\" will generate .large-1, .large-2, etc.\n@mixin grid-html-classes($size) {\n\n  @for $i from 0 through $total-columns - 1 {\n    .#{$size}-push-#{$i} {\n      @include grid-column($push: $i, $collapse: null, $float: false);\n    }\n\n    .#{$size}-pull-#{$i} {\n      @include grid-column($pull: $i, $collapse: null, $float: false);\n    }\n  }\n\n  .column,\n  .columns {\n    @include grid-column($columns: false, $position: true);\n  }\n\n\n  @for $i from 1 through $total-columns {\n    .#{$size}-#{$i} {\n      @include grid-column($columns: $i, $collapse: null, $float: false);\n    }\n  }\n\n  @for $i from 0 through $total-columns - 1 {\n    .#{$size}-offset-#{$i} {\n      @include grid-column($offset: $i, $collapse: null, $float: false);\n    }\n  }\n\n  .#{$size}-reset-order {\n    margin-#{$default-float}: 0;\n    margin-#{$opposite-direction}: 0;\n    left: auto;\n    right: auto;\n    float: $default-float;\n  }\n\n  .column.#{$size}-centered,\n  .columns.#{$size}-centered {\n    @include grid-column($center: true, $collapse: null, $float: false);\n  }\n\n  .column.#{$size}-uncentered,\n  .columns.#{$size}-uncentered {\n    margin-#{$default-float}: 0;\n    margin-#{$opposite-direction}: 0;\n    float: $default-float;\n  }\n\n  // Fighting [class*=\"column\"] + [class*=\"column\"]:last-child\n  .column.#{$size}-centered:last-child,\n  .columns.#{$size}-centered:last-child {\n    float: none;\n  }\n\n  // Fighting .column.<previous-size>-centered:last-child\n  .column.#{$size}-uncentered:last-child,\n  .columns.#{$size}-uncentered:last-child {\n    float: $default-float;\n  }\n\n  .column.#{$size}-uncentered.opposite,\n  .columns.#{$size}-uncentered.opposite {\n    float: $opposite-direction;\n  }\n\n  .row {\n    &.#{$size}-collapse {\n\n      >.column,\n      >.columns {\n        @include grid-column($collapse: true, $float: false);\n      }\n\n      .row {\n        margin-left: 0;\n        margin-right: 0;\n      }\n    }\n\n    &.#{$size}-uncollapse {\n\n      >.column,\n      >.columns {\n        @include grid-column;\n      }\n    }\n  }\n}\n\n@include exports(\"grid\") {\n  @if $include-html-grid-classes {\n    .row {\n      @include grid-row;\n\n      &.collapse {\n\n        >.column,\n        >.columns {\n          @include grid-column($collapse: true, $float: false);\n        }\n\n        .row {\n          margin-left: 0;\n          margin-right: 0;\n        }\n      }\n\n      .row {\n        @include grid-row($behavior: nest);\n\n        &.collapse {\n          @include grid-row($behavior: nest-collapse);\n        }\n      }\n    }\n\n    .column,\n    .columns {\n      @include grid-column($columns: $total-columns);\n    }\n\n    [class*=\"column\"]+[class*=\"column\"]:last-child {\n      float: $last-child-float;\n    }\n\n    [class*=\"column\"]+[class*=\"column\"].end {\n      float: $default-float;\n    }\n\n    @media #{$small-up} {\n      @include grid-html-classes($size: small);\n    }\n\n    @media #{$medium-up} {\n      @include grid-html-classes($size: medium);\n\n      // Old push and pull classes\n      @for $i from 0 through $total-columns - 1 {\n        .push-#{$i} {\n          @include grid-column($push: $i, $collapse: null, $float: false);\n        }\n\n        .pull-#{$i} {\n          @include grid-column($pull: $i, $collapse: null, $float: false);\n        }\n      }\n    }\n\n    @media #{$large-up} {\n      @include grid-html-classes($size: large);\n\n      @for $i from 0 through $total-columns - 1 {\n        .push-#{$i} {\n          @include grid-column($push: $i, $collapse: null, $float: false);\n        }\n\n        .pull-#{$i} {\n          @include grid-column($pull: $i, $collapse: null, $float: false);\n        }\n      }\n    }\n  }\n\n  @if $include-xl-html-grid-classes {\n    @media #{$xlarge-up} {\n      @include grid-html-classes($size: xlarge);\n    }\n\n    @media #{$xxlarge-up} {\n      @include grid-html-classes($size: xxlarge);\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"../functions\";\n//\n// Foundation Variables\n//\n\n// Data attribute namespace\n// styles get applied to [data-mysite-plugin], etc\n$namespace: false !default;\n\n// The default font-size is set to 100% of the browser style sheet (usually 16px)\n// for compatibility with browser-based text zoom or user-set defaults.\n\n// Since the typical default browser font-size is 16px, that makes the calculation for grid size.\n// If you want your base font-size to be different and not have it affect the grid breakpoints,\n// set $rem-base to $base-font-size and make sure $base-font-size is a px value.\n$base-font-size: 100% !default;\n\n// $base-line-height is 24px while $base-font-size is 16px\n$base-line-height: 1.5 !default;\n\n//\n// Global Foundation Mixins\n//\n\n// @mixins\n//\n// We use this to control border radius.\n// $radius - Default: $global-radius || 4px\n@mixin radius($radius: $global-radius) {\n  @if $radius {\n    border-radius: $radius;\n  }\n}\n\n// @mixins\n//\n// We use this to create equal side border radius on elements.\n// $side - Options: left, right, top, bottom\n@mixin side-radius($side, $radius: $global-radius) {\n  @if ($side ==left or $side ==right) {\n    -webkit-border-bottom-#{$side}-radius: $radius;\n    -webkit-border-top-#{$side}-radius: $radius;\n    border-bottom-#{$side}-radius: $radius;\n    border-top-#{$side}-radius: $radius;\n  }\n\n  @else {\n    -webkit-#{$side}-left-radius: $radius;\n    -webkit-#{$side}-right-radius: $radius;\n    border-#{$side}-left-radius: $radius;\n    border-#{$side}-right-radius: $radius;\n  }\n}\n\n// @mixins\n//\n// We can control whether or not we have inset shadows edges.\n// $active - Default: true, Options: false\n@mixin inset-shadow($active: true) {\n  box-shadow: $shiny-edge-size $shiny-edge-color inset;\n\n  @if $active {\n    &:active {\n      box-shadow: $shiny-edge-size $shiny-edge-active-color inset;\n    }\n  }\n}\n\n// @mixins\n//\n// We use this to add transitions to elements\n// $property - Default: all, Options: http://www.w3.org/TR/css3-transitions/#animatable-properties\n// $speed - Default: 300ms\n// $ease - Default:ease-out, Options: http://css-tricks.com/almanac/properties/t/transition-timing-function/\n@mixin single-transition($property: all, $speed: 300ms, $ease: ease-out) {\n  transition: $property $speed $ease;\n}\n\n// @mixins\n//\n// We use this to add box-sizing across browser prefixes\n@mixin box-sizing($type: border-box) {\n  -webkit-box-sizing: $type; // Android < 2.3, iOS < 4\n  -moz-box-sizing: $type; // Firefox < 29\n  box-sizing: $type; // Chrome, IE 8+, Opera, Safari 5.1\n}\n\n// @mixins\n//\n// We use this to create isosceles triangles\n// $triangle-size - Used to set border-size. No default, set a px or em size.\n// $triangle-color - Used to set border-color which makes up triangle. No default\n// $triangle-direction - Used to determine which direction triangle points. Options: top, bottom, left, right\n@mixin css-triangle($triangle-size, $triangle-color, $triangle-direction) {\n  content: \"\";\n  display: block;\n  width: 0;\n  height: 0;\n  border: inset $triangle-size;\n\n  @if ($triangle-direction ==top) {\n    border-color: $triangle-color transparent transparent transparent;\n    border-top-style: solid;\n  }\n\n  @if ($triangle-direction ==bottom) {\n    border-color: transparent transparent $triangle-color transparent;\n    border-bottom-style: solid;\n  }\n\n  @if ($triangle-direction ==left) {\n    border-color: transparent transparent transparent $triangle-color;\n    border-left-style: solid;\n  }\n\n  @if ($triangle-direction ==right) {\n    border-color: transparent $triangle-color transparent transparent;\n    border-right-style: solid;\n  }\n}\n\n// @mixins\n//\n// We use this to create the icon with three lines aka the hamburger icon, the menu-icon or the navicon\n// $width - Width of hamburger icon in rem\n// $left - If false, icon will be centered horizontally || explicitly set value in rem\n// $top - If false, icon will be centered vertically || explicitly set value in rem\n// $thickness - thickness of lines in hamburger icon, set value in px\n// $gap - spacing between the lines in hamburger icon, set value in px\n// $color - icon color\n// $hover-color - icon color during hover\n// $offcanvas - Set to true of @include in offcanvas\n@mixin hamburger($width, $left, $top, $thickness, $gap, $color, $hover-color, $offcanvas) {\n  span::after {\n    content: \"\";\n    position: absolute;\n    display: block;\n    height: 0;\n\n    @if $offcanvas {\n      @if $top {\n        top: $top;\n      }\n\n      @else {\n        top: 50%;\n        margin-top: (-$width/2);\n      }\n\n      @if $left {\n        left: $left;\n      }\n\n      @else {\n        left: ($tabbar-menu-icon-width - $width)/2;\n      }\n    }\n\n    @else {\n      top: 50%;\n      margin-top: -(calc($width / 2));\n      #{$opposite-direction}: $topbar-link-padding;\n    }\n\n    box-shadow: 0 0 0 $thickness $color,\n    0 ($gap + $thickness) 0 $thickness $color,\n    0 (2 * $gap + 2*$thickness) 0 $thickness $color;\n    width: $width;\n  }\n\n  span:hover:after {\n    box-shadow:\n      0 0 0 $thickness $hover-color,\n      0 $gap + $thickness 0 $thickness $hover-color,\n      0 (2 * $gap + 2*$thickness) 0 $thickness $hover-color;\n  }\n}\n\n// We use this to do clear floats\n@mixin clearfix {\n\n  &:before,\n  &:after {\n    content: \" \";\n    display: table;\n  }\n\n  &:after {\n    clear: both;\n  }\n}\n\n// @mixins\n//\n// We use this to add a glowing effect to block elements\n// $selector - Used for selector state. Default: focus, Options: hover, active, visited\n// $fade-time - Default: 300ms\n// $glowing-effect-color - Default: fade-out($primary-color, .25)\n@mixin block-glowing-effect($selector: focus, $fade-time: 300ms, $glowing-effect-color: fade-out($primary-color, .25)) {\n  transition: box-shadow $fade-time, border-color $fade-time ease-in-out;\n\n  &:#{$selector} {\n    box-shadow: 0 0 5px $glowing-effect-color;\n    border-color: $glowing-effect-color;\n  }\n}\n\n// @mixins\n//\n// We use this to translate elements in 2D\n// $horizontal: Default: 0\n// $vertical: Default: 0\n@mixin translate2d($horizontal: 0, $vertical: 0) {\n  transform: translate($horizontal, $vertical)\n}\n\n// @mixins\n//\n// Makes an element visually hidden, but accessible.\n// @see http://snook.ca/archives/html_and_css/hiding-content-for-accessibility\n@mixin element-invisible {\n  position: absolute !important;\n  height: 1px;\n  width: 1px;\n  overflow: hidden;\n  clip: rect(1px, 1px, 1px, 1px);\n}\n\n// @mixins\n//\n// Turns off the element-invisible effect.\n@mixin element-invisible-off {\n  position: static !important;\n  height: auto;\n  width: auto;\n  overflow: visible;\n  clip: auto;\n}\n\n$white : #FFFFFF !default;\n$ghost : #FAFAFA !default;\n$snow : #F9F9F9 !default;\n$vapor : #F6F6F6 !default;\n$white-smoke : #F5F5F5 !default;\n$silver : #EFEFEF !default;\n$smoke : #EEEEEE !default;\n$gainsboro : #DDDDDD !default;\n$iron : #CCCCCC !default;\n$base : #AAAAAA !default;\n$aluminum : #999999 !default;\n$jumbo : #888888 !default;\n$monsoon : #777777 !default;\n$steel : #666666 !default;\n$charcoal : #555555 !default;\n$tuatara : #444444 !default;\n$oil : #333333 !default;\n$jet : #222222 !default;\n$black : #000000 !default;\n\n// We use these as default colors throughout\n$primary-color: #008CBA !default; // bondi-blue\n$secondary-color: #e7e7e7 !default; // white-lilac\n$alert-color: #f04124 !default; // cinnabar\n$success-color: #43AC6A !default; // sea-green\n$warning-color: #f08a24 !default; // carrot\n$info-color: #a0d3e8 !default; // cornflower\n\n// We use these to define default font stacks\n$font-family-sans-serif: \"Helvetica Neue\", Helvetica, Roboto, Arial, sans-serif !default;\n$font-family-serif: Georgia, Cambria, \"Times New Roman\", Times, serif !default;\n$font-family-monospace: Consolas, \"Liberation Mono\", Courier, monospace !default;\n\n// We use these to define default font weights\n$font-weight-normal: normal !default;\n$font-weight-bold: bold !default;\n\n// We use these to control various global styles\n$body-bg: #fff !default;\n$body-font-color: #222 !default;\n$body-font-family: $font-family-sans-serif !default;\n$body-font-weight: $font-weight-normal !default;\n$body-font-style: normal !default;\n\n// We use this to control font-smoothing\n$font-smoothing: antialiased !default;\n\n// We use these to control text direction settings\n$text-direction: ltr !default;\n$default-float: left !default;\n$opposite-direction: right !default;\n\n@if $text-direction ==ltr {\n  $default-float: left;\n  $opposite-direction: right;\n}\n\n@else {\n  $default-float: right;\n  $opposite-direction: left;\n}\n\n// We use these to make sure border radius matches unless we want it different.\n$global-radius: 3px !default;\n$global-rounded: 1000px !default;\n\n// We use these to control inset shadow shiny edges and depressions.\n$shiny-edge-size: 0 1px 0 !default;\n$shiny-edge-color: rgba(#fff, .5) !default;\n$shiny-edge-active-color: rgba(#000, .2) !default;\n\n// We use this to control whether or not CSS classes come through in the gem files.\n$include-html-classes: true !default;\n$include-print-styles: true !default;\n$include-html-global-classes: $include-html-classes !default;\n\n$column-gutter: rem-calc(30) !default;\n\n// Media Query Ranges\n$small-range: (\n  0,\n  40em) !default;\n$medium-range: (\n  40.063em,\n  64em) !default;\n$large-range: (\n  64.063em,\n  90em) !default;\n$xlarge-range: (\n  90.063em,\n  120em) !default;\n$xxlarge-range: (\n  120.063em,\n  99999999em) !default;\n\n\n$screen: \"only screen\" !default;\n\n$landscape: \"#{$screen} and (orientation: landscape)\" !default;\n$portrait: \"#{$screen} and (orientation: portrait)\" !default;\n\n$small-up: $screen !default;\n$small-only: \"#{$screen} and (max-width: #{upper-bound($small-range)})\" !default;\n\n$medium-up: \"#{$screen} and (min-width:#{lower-bound($medium-range)})\" !default;\n$medium-only: \"#{$screen} and (min-width:#{lower-bound($medium-range)}) and (max-width:#{upper-bound($medium-range)})\" !default;\n\n$large-up: \"#{$screen} and (min-width:#{lower-bound($large-range)})\" !default;\n$large-only: \"#{$screen} and (min-width:#{lower-bound($large-range)}) and (max-width:#{upper-bound($large-range)})\" !default;\n\n$xlarge-up: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)})\" !default;\n$xlarge-only: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)}) and (max-width:#{upper-bound($xlarge-range)})\" !default;\n\n$xxlarge-up: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)})\" !default;\n$xxlarge-only: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)}) and (max-width:#{upper-bound($xxlarge-range)})\" !default;\n\n// Legacy\n$small: $medium-up;\n$medium: $medium-up;\n$large: $large-up;\n\n\n//We use this as cursors values for enabling the option of having custom cursors in the whole site's stylesheet\n$cursor-auto-value: auto !default;\n$cursor-crosshair-value: crosshair !default;\n$cursor-default-value: default !default;\n$cursor-pointer-value: pointer !default;\n$cursor-help-value: help !default;\n$cursor-text-value: text !default;\n\n\n@include exports(\"global\") {\n\n  // Meta styles are included in all builds, as they are a dependency of the Javascript.\n  // Used to provide media query values for javascript components.\n  // Forward slash placed around everything to convince PhantomJS to read the value.\n\n  meta.foundation-version {\n    font-family: \"/5.5.0/\";\n  }\n\n  meta.foundation-mq-small {\n    font-family: \"/\" + unquote($small-up) + \"/\";\n    width: lower-bound($small-range\n    );\n}\n\nmeta.foundation-mq-small-only {\n  font-family: \"/\" + unquote($small-only) + \"/\";\n  width: lower-bound($small-range);\n}\n\nmeta.foundation-mq-medium {\n  font-family: \"/\" + unquote($medium-up) + \"/\";\n  width: lower-bound($medium-range);\n}\n\nmeta.foundation-mq-medium-only {\n  font-family: \"/\" + unquote($medium-only) + \"/\";\n  width: lower-bound($medium-range);\n}\n\nmeta.foundation-mq-large {\n  font-family: \"/\" + unquote($large-up) + \"/\";\n  width: lower-bound($large-range);\n}\n\nmeta.foundation-mq-large-only {\n  font-family: \"/\" + unquote($large-only) + \"/\";\n  width: lower-bound($large-range);\n}\n\nmeta.foundation-mq-xlarge {\n  font-family: \"/\" + unquote($xlarge-up) + \"/\";\n  width: lower-bound($xlarge-range);\n}\n\nmeta.foundation-mq-xlarge-only {\n  font-family: \"/\" + unquote($xlarge-only) + \"/\";\n  width: lower-bound($xlarge-range);\n}\n\nmeta.foundation-mq-xxlarge {\n  font-family: \"/\" + unquote($xxlarge-up) + \"/\";\n  width: lower-bound($xxlarge-range);\n}\n\nmeta.foundation-data-attribute-namespace {\n  font-family: #{$namespace};\n}\n\n@if $include-html-global-classes {\n\n  // Must be 100% for off canvas to work\n  html,\n  body {\n    height: 100%;\n  }\n\n  // Set box-sizing globally to handle padding and border widths\n  *,\n  *:before,\n  *:after {\n    @include box-sizing(border-box);\n  }\n\n  html,\n  body {\n    font-size: $base-font-size;\n  }\n\n  // Default body styles\n  body {\n    background: $body-bg;\n    color: $body-font-color;\n    padding: 0;\n    margin: 0;\n    font-family: $body-font-family;\n    font-weight: $body-font-weight;\n    font-style: $body-font-style;\n    line-height: $base-line-height; // Set to $base-line-height to take on browser default of 150%\n    position: relative;\n    cursor: $cursor-auto-value;\n  }\n\n  a:hover {\n    cursor: $cursor-pointer-value;\n  }\n\n  // Grid Defaults to get images and embeds to work properly\n  img {\n    max-width: 100%;\n    height: auto;\n  }\n\n  img {\n    -ms-interpolation-mode: bicubic;\n  }\n\n  #map_canvas,\n  .map_canvas {\n\n    img,\n    embed,\n    object {\n      max-width: none !important;\n    }\n  }\n\n  // Miscellaneous useful HTML classes\n  .left {\n    float: left !important;\n  }\n\n  .right {\n    float: right !important;\n  }\n\n  .clearfix {\n    @include clearfix;\n  }\n\n  // Hide visually and from screen readers\n  .hide {\n    display: none !important;\n    visibility: hidden;\n  }\n\n  // Hide visually and from screen readers, but maintain layout\n  .invisible {\n    visibility: hidden;\n  }\n\n  // Font smoothing\n  // Antialiased font smoothing works best for light text on a dark background.\n  // Apply to single elements instead of globally to body.\n  // Note this only applies to webkit-based desktop browsers and Firefox 25 (and later) on the Mac.\n  .antialiased {\n    -webkit-font-smoothing: antialiased;\n    -moz-osx-font-smoothing: grayscale;\n  }\n\n  // Get rid of gap under images by making them display: inline-block; by default\n  img {\n    display: inline-block;\n    vertical-align: middle;\n  }\n\n  //\n  // Global resets for forms\n  //\n\n  // Make sure textarea takes on height automatically\n  textarea {\n    height: auto;\n    min-height: 50px;\n  }\n\n  // Make select elements 100% width by default\n  select {\n    width: 100%;\n  }\n}\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-button-classes: $include-html-classes !default;\n\n// We use these to build padding for buttons.\n$button-tny: rem-calc(10) !default;\n$button-sml: rem-calc(14) !default;\n$button-med: rem-calc(16) !default;\n$button-lrg: rem-calc(18) !default;\n\n// We use this to control the display property.\n$button-display: inline-block !default;\n$button-margin-bottom: rem-calc(20) !default;\n\n// We use these to control button text styles.\n$button-font-family: $body-font-family !default;\n$button-font-color: $white !default;\n$button-font-color-alt: $oil !default;\n$button-font-tny: rem-calc(11) !default;\n$button-font-sml: rem-calc(13) !default;\n$button-font-med: rem-calc(16) !default;\n$button-font-lrg: rem-calc(20) !default;\n$button-font-weight: $font-weight-normal !default;\n$button-font-align: center !default;\n\n// We use these to control various hover effects.\n$button-function-factor: -20% !default;\n\n// We use these to control button border styles.\n$button-border-width: 0 !default;\n$button-border-style: solid !default;\n$button-bg-color: $primary-color !default;\n$button-bg-hover: scale-color($button-bg-color, $lightness: $button-function-factor) !default;\n$button-border-color: $button-bg-hover !default;\n$secondary-button-bg-hover: scale-color($secondary-color, $lightness: $button-function-factor) !default;\n$secondary-button-border-color: $secondary-button-bg-hover !default;\n$success-button-bg-hover: scale-color($success-color, $lightness: $button-function-factor) !default;\n$success-button-border-color: $success-button-bg-hover !default;\n$alert-button-bg-hover: scale-color($alert-color, $lightness: $button-function-factor) !default;\n$alert-button-border-color: $alert-button-bg-hover !default;\n$warning-button-bg-hover: scale-color($warning-color, $lightness: $button-function-factor) !default;\n$warning-button-border-color: $warning-button-bg-hover !default;\n$info-button-bg-hover: scale-color($info-color, $lightness: $button-function-factor) !default;\n$info-button-border-color: $info-button-bg-hover !default;\n\n// We use this to set the default radius used throughout the core.\n$button-radius: $global-radius !default;\n$button-round: $global-rounded !default;\n\n// We use this to set default opacity and cursor for disabled buttons.\n$button-disabled-opacity: 0.7 !default;\n$button-disabled-cursor: $cursor-default-value !default;\n\n\n//\n// @MIXIN\n//\n// We use this mixin to create a default button base.\n//\n// $style - Sets base styles. Can be set to false. Default: true.\n// $display - Used to control display property. Default: $button-display || inline-block\n\n@mixin button-base($style:true, $display:$button-display) {\n  @if $style {\n    border-style: $button-border-style;\n    border-width: $button-border-width;\n    cursor: $cursor-pointer-value;\n    font-family: $button-font-family;\n    font-weight: $button-font-weight;\n    line-height: normal;\n    margin: 0 0 $button-margin-bottom;\n    position: relative;\n    text-decoration: none;\n    text-align: $button-font-align;\n    -webkit-appearance: none;\n    border-radius:0;\n  }\n  @if $display { display: $display; }\n}\n\n// @MIXIN\n//\n// We use this mixin to add button size styles\n//\n// $padding - Used to build padding for buttons Default: $button-med ||= rem-calc(12)\n// $full-width - We can set $full-width:true to remove side padding extend width - Default: false\n\n@mixin button-size($padding:$button-med, $full-width:false) {\n\n  // We control which padding styles come through,\n  // these can be turned off by setting $padding:false\n  @if $padding {\n    padding-top: $padding;\n    padding-#{$opposite-direction}: $padding * 2;\n    padding-bottom: $padding + rem-calc(1);\n    padding-#{$default-float}: $padding * 2;\n\n    // We control the font-size based on mixin input.\n    @if      $padding == $button-med { font-size: $button-font-med; }\n    @else if $padding == $button-tny { font-size: $button-font-tny; }\n    @else if $padding == $button-sml { font-size: $button-font-sml; }\n    @else if $padding == $button-lrg { font-size: $button-font-lrg; }\n  }\n\n  // We can set $full-width:true to remove side padding extend width.\n  @if $full-width {\n    // We still need to check if $padding is set.\n    @if $padding {\n    padding-top: $padding;\n    padding-bottom: $padding + rem-calc(1);\n    } @else if $padding == false {\n      padding-top:0;\n      padding-bottom:0;\n    }\n    padding-right: 0;\n    padding-left: 0;\n    width: 100%;\n  }\n}\n\n// @MIXIN\n//\n// we use this mixin to create the button hover and border colors\n\n// @MIXIN\n//\n// We use this mixin to add button color styles\n//\n// $bg - Background color. We can set $bg:false for a transparent background. Default: $primary-color.\n// $radius - If true, set to button radius which is $global-radius || explicitly set radius amount in px (ex. $radius:10px). Default: true\n// $disabled - We can set $disabled:true to create a disabled transparent button. Default: false\n// $bg-hover - Button Hover Background Color. Default: $button-bg-hover\n// $border-color - Button Border Color. Default: $button-border-color\n@mixin button-style($bg:$button-bg-color, $radius:false, $disabled:false, $bg-hover:null, $border-color:null) {\n\n  // We control which background styles are used,\n  // these can be removed by setting $bg:false\n  @if $bg {\n\n    @if $bg-hover == null {\n      $bg-hover: if($bg == $button-bg-color, $button-bg-hover, scale-color($bg, $lightness: $button-function-factor));\n    }\n\n    @if $border-color == null {\n      $border-color: if($bg == $button-bg-color, $button-border-color, scale-color($bg, $lightness: $button-function-factor));\n    }\n\n    // This find the lightness percentage of the background color.\n    $bg-lightness: lightness($bg);\n    $bg-hover-lightness: lightness($bg-hover);\n\n    background-color: $bg;\n    border-color: $border-color;\n    &:hover,\n    &:focus { background-color: $bg-hover; }\n\n    // We control the text color for you based on the background color.\n    color: if($bg-lightness > 70%, $button-font-color-alt, $button-font-color);\n\n    &:hover,\n    &:focus {\n      color: if($bg-hover-lightness > 70%, $button-font-color-alt, $button-font-color);\n    }\n  }\n\n  // We can set $disabled:true to create a disabled transparent button.\n  @if $disabled {\n    cursor: $button-disabled-cursor;\n    opacity: $button-disabled-opacity;\n    box-shadow: none;\n    &:hover,\n    &:focus { background-color: $bg; }\n  }\n\n  // We can control how much button radius is used.\n  @if $radius == true { @include radius($button-radius); }\n  @else if $radius { @include radius($radius); }\n\n}\n\n// @MIXIN\n//\n// We use this to quickly create buttons with a single mixin. As @jaredhardy puts it, \"the kitchen sink mixin\"\n//\n// $padding - Used to build padding for buttons Default: $button-med ||= rem-calc(12)\n// $bg - Primary color set in settings file. Default: $button-bg.\n// $radius - If true, set to button radius which is $global-radius || explicitly set radius amount in px (ex. $radius:10px). Default:false.\n// $full-width - We can set $full-width:true to remove side padding extend width. Default:false.\n// $disabled - We can set $disabled:true to create a disabled transparent button. Default:false.\n// $is-prefix - Not used? Default:false.\n// $bg-hover - Button Hover Color - Default null - see button-style mixin\n// $border-color - Button Border Color - Default null - see button-style mixin\n// $transition - We can control whether or not to include the background-color transition property - Default:true.\n@mixin button($padding:$button-med, $bg:$button-bg-color, $radius:false, $full-width:false, $disabled:false, $is-prefix:false, $bg-hover:null, $border-color:null, $transition: true) {\n  @include button-base;\n  @include button-size($padding, $full-width);\n  @include button-style($bg, $radius, $disabled, $bg-hover, $border-color);\n\n  @if $transition {\n    @include single-transition(background-color);\n  }\n}\n\n\n@include exports(\"button\") {\n  @if $include-html-button-classes {\n\n    // Default styles applied outside of media query\n    button, .button {\n      @include button-base;\n      @include button-size;\n      @include button-style;\n\n      @include single-transition(background-color);\n\n      &.secondary { @include button-style($bg:$secondary-color, $bg-hover:$secondary-button-bg-hover, $border-color:$secondary-button-border-color); }\n      &.success   { @include button-style($bg:$success-color, $bg-hover:$success-button-bg-hover, $border-color:$success-button-border-color); }\n      &.alert     { @include button-style($bg:$alert-color, $bg-hover:$alert-button-bg-hover, $border-color:$alert-button-border-color); }\n      &.warning   { @include button-style($bg:$warning-color, $bg-hover:$warning-button-bg-hover, $border-color:$warning-button-border-color); }\n      &.info      { @include button-style($bg:$info-color, $bg-hover:$info-button-bg-hover, $border-color:$info-button-border-color); }\n\n      &.large  { @include button-size($padding:$button-lrg); }\n      &.small  { @include button-size($padding:$button-sml); }\n      &.tiny   { @include button-size($padding:$button-tny); }\n      &.expand { @include button-size($padding:null,$full-width:true); }\n\n      &.left-align  { text-align: left; text-indent: rem-calc(12); }\n      &.right-align { text-align: right; padding-right: rem-calc(12); }\n\n      &.radius { @include button-style($bg:false, $radius:true); }\n      &.round  { @include button-style($bg:false, $radius:$button-round); }\n\n      &.disabled, &[disabled] { @include button-style($bg:$button-bg-color, $disabled:true, $bg-hover:$button-bg-hover, $border-color:$button-border-color);\n        &.secondary { @include button-style($bg:$secondary-color, $disabled:true, $bg-hover:$secondary-button-bg-hover, $border-color:$secondary-button-border-color); }\n        &.success { @include button-style($bg:$success-color, $disabled:true, $bg-hover:$success-button-bg-hover, $border-color:$success-button-border-color); }\n        &.alert { @include button-style($bg:$alert-color, $disabled:true, $bg-hover:$alert-button-bg-hover, $border-color:$alert-button-border-color); }\n        &.warning { @include button-style($bg:$warning-color, $disabled:true, $bg-hover:$warning-button-bg-hover, $border-color:$warning-button-border-color); }\n        &.info { @include button-style($bg:$info-color, $disabled:true, $bg-hover:$info-button-bg-hover, $border-color:$info-button-border-color); }\n      }\n    }\n\n    //firefox 2px fix\n    button::-moz-focus-inner {border:0; padding:0;}\n\n    @media #{$medium-up} {\n      button, .button {\n        @include button-base($style:false, $display:inline-block);\n        @include button-size($padding:false, $full-width:false);\n      }\n    }\n  }\n}\n","@charset \"utf-8\";\n\n$spacing-unit: 30px;\n\n\n// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n//\n\n// Table of Contents\n// Foundation Settings\n//\n// a. Base\n// b. Grid\n// c. Global\n// d. Media Query Ranges\n// e. Typography\n// 01. Accordion\n// 02. Alert Boxes\n// 03. Block Grid\n// 04. Breadcrumbs\n// 05. Buttons\n// 06. Button Groups\n// 07. Clearing\n// 08. Dropdown\n// 09. Dropdown Buttons\n// 10. Flex Video\n// 11. Forms\n// 12. Icon Bar\n// 13. Inline Lists\n// 14. Joyride\n// 15. Keystrokes\n// 16. Labels\n// 17. Magellan\n// 18. Off-canvas\n// 19. Orbit\n// 20. Pagination\n// 21. Panels\n// 22. Pricing Tables\n// 23. Progress Bar\n// 24. Range Slider\n// 25. Reveal\n// 26. Side Nav\n// 27. Split Buttons\n// 28. Sub Nav\n// 29. Switch\n// 30. Tables\n// 31. Tabs\n// 32. Thumbnails\n// 33. Tooltips\n// 34. Top Bar\n// 36. Visibility Classes\n\n// a. Base\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// This is the default html and body font-size for the base rem value.\n// $rem-base: 16px;\n\n// Allows the use of rem-calc() or lower-bound() in your settings\n@import \"functions\";\n\n// The default font-size is set to 100% of the browser style sheet (usually 16px)\n// for compatibility with browser-based text zoom or user-set defaults.\n\n// Since the typical default browser font-size is 16px, that makes the calculation for grid size.\n// If you want your base font-size to be different and not have it affect the grid breakpoints,\n// set $rem-base to $base-font-size and make sure $base-font-size is a px value.\n// $base-font-size: 100%;\n\n$base-font-size: 16px;\n$rem-base: $base-font-size;\n\n\n// The $base-font-size is 100% while $base-line-height is 150%\n// $base-line-height: 150%;\n\n// We use this to control whether or not CSS classes come through in the gem files.\n$include-html-classes: true;\n// $include-print-styles: true;\n$include-html-global-classes: $include-html-classes;\n\n// b. Grid\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-grid-classes: $include-html-classes;\n// $include-xl-html-grid-classes: false;\n\n// $row-width: rem-calc(1000);\n// $total-columns: 12;\n// $column-gutter: rem-calc(30);\n\n// c. Global\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// We use these to define default font stacks\n// $font-family-sans-serif: \"Lato\", \"Helvetica Neue\", \"Helvetica\", Helvetica, Arial, sans-serif;\n// $font-family-serif: \"Volkhov\", Georgia, Times, serif;\n// $font-family-monospace: \"Lucida Console\", Monaco, monospace;\n\n// We use these to define default font weights\n// $font-weight-normal: normal !default;\n// $font-weight-bold: bold !default;\n\n// $white       : #FFFFFF;\n// $ghost       : #FAFAFA;\n// $snow        : #F9F9F9;\n// $vapor       : #F6F6F6;\n// $white-smoke : #F5F5F5;\n// $silver      : #EFEFEF;\n// $smoke       : #EEEEEE;\n// $gainsboro   : #DDDDDD;\n// $iron        : #CCCCCC;\n// $base        : #AAAAAA;\n// $aluminum    : #999999;\n// $jumbo       : #888888;\n// $monsoon     : #777777;\n// $steel       : #666666;\n// $charcoal    : #555555;\n// $tuatara     : #444444;\n// $oil         : #333333;\n// $jet         : #222222;\n// $black       : #000000;\n\n// We use these as default colors throughout\n// $primary-color: #008CBA;\n// $secondary-color: #e7e7e7;\n// $alert-color: #f04124;\n// $success-color: #43AC6A;\n// $warning-color: #f08a24;\n// $info-color: #a0d3e8;\n\n// We use these to control various global styles\n// $body-bg: $white;\n// $body-font-color: $jet;\n// $body-font-family: $font-family-sans-serif;\n// $body-font-weight: $font-weight-normal;\n// $body-font-style: normal;\n\n// We use this to control font-smoothing\n// $font-smoothing: antialiased;\n\n// We use these to control text direction settings\n// $text-direction: ltr;\n// $opposite-direction: right;\n// $default-float: left;\n// $last-child-float: $opposite-direction;\n\n// We use these to make sure border radius matches unless we want it different.\n$global-radius: 3px;\n// $global-rounded: 1000px;\n\n// We use these to control inset shadow shiny edges and depressions.\n// $shiny-edge-size: 0 1px 0;\n// $shiny-edge-color: rgba($white, .5);\n// $shiny-edge-active-color: rgba($black, .2);\n\n// // d. Media Query Ranges\n// // - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $small-range: (0em, 40em);\n// $medium-range: (40.063em, 64em);\n// $large-range: (64.063em, 90em);\n// $xlarge-range: (90.063em, 120em);\n// $xxlarge-range: (120.063em, 99999999em);\n\n// $screen: \"only screen\";\n\n// // $landscape: \"#{$screen} and (orientation: landscape)\";\n// // $portrait: \"#{$screen} and (orientation: portrait)\";\n\n// $small-up: $screen;\n// $small-only: \"#{$screen} and (max-width: #{upper-bound($small-range)})\";\n\n// $medium-up: \"#{$screen} and (min-width:#{lower-bound($medium-range)})\";\n// $medium-only: \"#{$screen} and (min-width:#{lower-bound($medium-range)}) and (max-width:#{upper-bound($medium-range)})\";\n\n// $large-up: \"#{$screen} and (min-width:#{lower-bound($large-range)})\";\n// $large-only: \"#{$screen} and (min-width:#{lower-bound($large-range)}) and (max-width:#{upper-bound($large-range)})\";\n\n// $xlarge-up: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)})\";\n// $xlarge-only: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)}) and (max-width:#{upper-bound($xlarge-range)})\";\n\n// $xxlarge-up: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)})\";\n// $xxlarge-only: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)}) and (max-width:#{upper-bound($xxlarge-range)})\";\n\n// Legacy\n// $small: $medium-up;\n// $medium: $medium-up;\n// $large: $large-up;\n\n// We use this as cursors values for enabling the option of having custom cursors in the whole site's stylesheet\n// $cursor-crosshair-value: crosshair;\n// $cursor-default-value: default;\n// $cursor-pointer-value: pointer;\n// $cursor-help-value: help;\n// $cursor-text-value: text;\n\n// e. Typography\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-type-classes: $include-html-classes;\n\n// We use these to control header font styles\n// $header-font-family: $font-family-serif;\n// $header-font-weight: $font-weight-normal;\n// $header-font-style: normal;\n// $header-font-color: $jet;\n// $header-line-height: 1.4;\n// $header-top-margin: .2rem;\n// $header-bottom-margin: .5rem;\n// $header-text-rendering: optimizeLegibility;\n\n// We use these to control header font sizes\n// $h1-font-size: rem-calc(54);\n// $h2-font-size: rem-calc(36);\n// $h3-font-size: rem-calc(29);\n// $h4-font-size: rem-calc(24);\n// $h5-font-size: rem-calc(19);\n// $h6-font-size: 1rem;\n\n// We use these to control header size reduction on small screens\n// $h1-font-reduction: rem-calc(10) !default;\n// $h2-font-reduction: rem-calc(10) !default;\n// $h3-font-reduction: rem-calc(5) !default;\n// $h4-font-reduction: rem-calc(5) !default;\n// $h5-font-reduction: 0 !default;\n// $h6-font-reduction: 0 !default;\n\n// These control how subheaders are styled.\n// $subheader-line-height: 1.4;\n// $subheader-font-color: scale-color($header-font-color, $lightness: 35%);\n// $subheader-font-weight: $font-weight-normal;\n// $subheader-top-margin: .2rem;\n// $subheader-bottom-margin: .5rem;\n\n// A general <small> styling\n// $small-font-size: 60%;\n// $small-font-color: scale-color($header-font-color, $lightness: 35%);\n\n// We use these to style paragraphs\n// $paragraph-font-family: inherit;\n// $paragraph-font-weight: $font-weight-normal;\n// $paragraph-font-size: 1rem;\n// $paragraph-line-height: 1.6;\n// $paragraph-margin-bottom: rem-calc(20);\n// $paragraph-aside-font-size: rem-calc(14);\n// $paragraph-aside-line-height: 1.35;\n// $paragraph-aside-font-style: italic;\n// $paragraph-text-rendering: optimizeLegibility;\n\n// We use these to style <code> tags\n// $code-color: $oil;\n// $code-font-family: $font-family-monospace;\n// $code-font-weight: $font-weight-normal;\n// $code-background-color: scale-color($secondary-color, $lightness: 70%);\n// $code-border-size: 1px;\n// $code-border-style: solid;\n// $code-border-color: scale-color($code-background-color, $lightness: -10%);\n// $code-padding: rem-calc(2) rem-calc(5) rem-calc(1);\n\n// We use these to style anchors\n// $anchor-text-decoration: none;\n// $anchor-text-decoration-hover: none;\n// $anchor-font-color: $primary-color;\n// $anchor-font-color-hover: scale-color($primary-color, $lightness: -14%);\n\n// We use these to style the <hr> element\n// $hr-border-width: 1px;\n// $hr-border-style: solid;\n$hr-border-color: $grey-3;\n// $hr-margin: rem-calc(20);\n\n// We use these to style lists\n// $list-font-family: $paragraph-font-family;\n// $list-font-size: $paragraph-font-size;\n// $list-line-height: $paragraph-line-height;\n// $list-margin-bottom: $paragraph-margin-bottom;\n// $list-style-position: outside;\n$list-side-margin: 1.3rem;\n// $list-ordered-side-margin: 1.4rem;\n// $list-side-margin-no-bullet: 0;\n// $list-nested-margin: rem-calc(20);\n// $definition-list-header-weight: $font-weight-bold;\n// $definition-list-header-margin-bottom: .3rem;\n// $definition-list-margin-bottom: rem-calc(12);\n\n// We use these to style blockquotes\n// $blockquote-font-color: scale-color($header-font-color, $lightness: 35%);\n// $blockquote-padding: rem-calc(9 20 0 19);\n// $blockquote-border: 1px solid $gainsboro;\n// $blockquote-cite-font-size: rem-calc(13);\n// $blockquote-cite-font-color: scale-color($header-font-color, $lightness: 23%);\n// $blockquote-cite-link-color: $blockquote-cite-font-color;\n\n// Acronym styles\n// $acronym-underline: 1px dotted $gainsboro;\n\n// We use these to control padding and margin\n// $microformat-padding: rem-calc(10 12);\n// $microformat-margin: rem-calc(0 0 20 0);\n\n// We use these to control the border styles\n// $microformat-border-width: 1px;\n// $microformat-border-style: solid;\n// $microformat-border-color: $gainsboro;\n\n// We use these to control full name font styles\n// $microformat-fullname-font-weight: $font-weight-bold;\n// $microformat-fullname-font-size: rem-calc(15);\n\n// We use this to control the summary font styles\n// $microformat-summary-font-weight: $font-weight-bold;\n\n// We use this to control abbr padding\n// $microformat-abbr-padding: rem-calc(0 1);\n\n// We use this to control abbr font styles\n// $microformat-abbr-font-weight: $font-weight-bold;\n// $microformat-abbr-font-decoration: none;\n\n// 01. Accordion\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-accordion-classes: $include-html-classes;\n\n$accordion-navigation-padding: rem-calc(12);\n// $accordion-navigation-bg-color: #ffffff;\n// $accordion-navigation-hover-bg-color: $grey-1;\n// $accordion-navigation-active-bg-color: $grey-1;\n// $accordion-navigation-font-color: $jet;\n// $accordion-navigation-font-size: rem-calc(16);\n// $accordion-navigation-font-family: $body-font-family;\n\n// $accordion-content-padding: $column-gutter/2;\n$accordion-content-active-bg-color: $body-bg;\n\n// 02. Alert Boxes\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-alert-classes: $include-html-classes;\n\n// We use this to control alert padding.\n// $alert-padding-top: rem-calc(14);\n// $alert-padding-default-float: $alert-padding-top;\n// $alert-padding-opposite-direction: $alert-padding-top + rem-calc(10);\n// $alert-padding-bottom: $alert-padding-top;\n\n// We use these to control text style.\n// $alert-font-weight: $font-weight-normal;\n$alert-font-size: rem-calc(15);\n// $alert-font-color: $white;\n// $alert-font-color-alt: scale-color($secondary-color, $lightness: -66%);\n\n// We use this for close hover effect.\n// $alert-function-factor: -14%;\n\n// We use these to control border styles.\n// $alert-border-style: solid;\n// $alert-border-width: 1px;\n// $alert-border-color: scale-color($primary-color, $lightness: $alert-function-factor);\n// $alert-bottom-margin: rem-calc(20);\n\n// We use these to style the close buttons\n// $alert-close-color: $oil;\n// $alert-close-top: 50%;\n// $alert-close-position: rem-calc(4);\n// $alert-close-font-size: rem-calc(22);\n// $alert-close-opacity: 0.3;\n// $alert-close-opacity-hover: 0.5;\n// $alert-close-padding: 9px 6px 4px;\n\n// We use this to control border radius\n// $alert-radius: $global-radius;\n\n// We use this to control transition effects\n// $alert-transition-speed: 300ms;\n// $alert-transition-ease: ease-out;\n\n// 03. Block Grid\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-block-grid-classes: $include-html-classes;\n// $include-xl-html-block-grid-classes: false;\n\n// We use this to control the maximum number of block grid elements per row\n// $block-grid-elements: 12;\n// $block-grid-default-spacing: rem-calc(20);\n// $align-block-grid-to-grid: false;\n\n// Enables media queries for block-grid classes. Set to false if writing semantic HTML.\n// $block-grid-media-queries: true;\n\n// 04. Breadcrumbs\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-nav-classes: $include-html-classes;\n\n// We use this to set the background color for the breadcrumb container.\n$crumb-bg: $grey-1;\n\n// We use these to set the padding around the breadcrumbs.\n// $crumb-padding: rem-calc(9 9 14 0);\n// $crumb-side-padding: rem-calc(12);\n\n// We use these to control border styles.\n// $crumb-function-factor: -10%;\n$crumb-border-size: 0;\n// $crumb-border-style: solid;\n$crumb-border-color: $grey-1;\n$crumb-radius: 0;\n\n// We use these to set various text styles for breadcrumbs.\n// $crumb-font-size: rem-calc(11);\n// $crumb-font-color: $primary-color;\n// $crumb-font-color-current: $oil;\n// $crumb-font-color-unavailable: $aluminum;\n// $crumb-font-transform: uppercase;\n// $crumb-link-decor: underline;\n\n// We use these to control the slash between breadcrumbs\n// $crumb-slash-color: $base;\n$crumb-slash: \"/\";\n\n// 05. Buttons\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-button-classes: $include-html-classes;\n\n// We use these to build padding for buttons.\n// $button-tny: rem-calc(10);\n// $button-sml: rem-calc(14);\n// $button-med: rem-calc(16);\n// $button-lrg: rem-calc(18);\n\n// We use this to control the display property.\n// $button-display: inline-block;\n// $button-margin-bottom: rem-calc(20);\n\n// We use these to control button text styles.\n// $button-font-family: $body-font-family;\n// $button-font-color: $white;\n// $button-font-color-alt: $oil;\n// $button-font-tny: rem-calc(11);\n// $button-font-sml: rem-calc(13);\n// $button-font-med: rem-calc(16);\n// $button-font-lrg: rem-calc(20);\n// $button-font-weight: $font-weight-normal;\n// $button-font-align: center;\n\n// We use these to control various hover effects.\n// $button-function-factor: -20%;\n\n// We use these to control button border and hover styles.\n// $button-border-width: 0px;\n// $button-border-style: solid;\n// $button-bg-color: $primary-color;\n// $button-bg-hover: scale-color($button-bg-color, $lightness: $button-function-factor);\n// $button-border-color: $button-bg-hover;\n// $secondary-button-bg-hover: scale-color($secondary-color, $lightness: $button-function-factor);\n// $secondary-button-border-color: $secondary-button-bg-hover;\n// $success-button-bg-hover: scale-color($success-color, $lightness: $button-function-factor);\n// $success-button-border-color: $success-button-bg-hover;\n// $alert-button-bg-hover: scale-color($alert-color, $lightness: $button-function-factor);\n// $alert-button-border-color: $alert-button-bg-hover;\n\n// We use this to set the default radius used throughout the core.\n// $button-radius: $global-radius;\n// $button-round: $global-rounded;\n\n// We use this to set default opacity and cursor for disabled buttons.\n// $button-disabled-opacity: 0.7;\n// $button-disabled-cursor: $cursor-default-value;\n\n// 06. Button Groups\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-button-classes: $include-html-classes;\n\n// Sets the margin for the right side by default, and the left margin if right-to-left direction is used\n// $button-bar-margin-opposite: rem-calc(10);\n// $button-group-border-width: 1px;\n\n// 07. Clearing\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-clearing-classes: $include-html-classes;\n\n// We use these to set the background colors for parts of Clearing.\n// $clearing-bg: $oil;\n// $clearing-caption-bg: $clearing-bg;\n// $clearing-carousel-bg: rgba(51,51,51,0.8);\n// $clearing-img-bg: $clearing-bg;\n\n// We use these to style the close button\n// $clearing-close-color: $iron;\n// $clearing-close-size: 30px;\n\n// We use these to style the arrows\n// $clearing-arrow-size: 12px;\n// $clearing-arrow-color: $clearing-close-color;\n\n// We use these to style captions\n// $clearing-caption-font-color: $iron;\n// $clearing-caption-font-size: 0.875em;\n// $clearing-caption-padding: 10px 30px 20px;\n\n// We use these to make the image and carousel height and style\n// $clearing-active-img-height: 85%;\n// $clearing-carousel-height: 120px;\n// $clearing-carousel-thumb-width: 120px;\n// $clearing-carousel-thumb-active-border: 1px solid rgb(255,255,255);\n\n// 08. Dropdown\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-dropdown-classes: $include-html-classes;\n\n// We use these to controls height and width styles.\n// $f-dropdown-max-width: 200px;\n// $f-dropdown-height: auto;\n// $f-dropdown-max-height: none;\n\n// Used for bottom position\n// $f-dropdown-margin-top: 2px;\n\n// Used for right position\n// $f-dropdown-margin-left: $f-dropdown-margin-top;\n\n// Used for left position\n// $f-dropdown-margin-right: $f-dropdown-margin-top;\n\n// Used for top position\n// $f-dropdown-margin-bottom: $f-dropdown-margin-top;\n\n// We use this to control the background color\n// $f-dropdown-bg: $white;\n\n// We use this to set the border styles for dropdowns.\n// $f-dropdown-border-style: solid;\n// $f-dropdown-border-width: 1px;\n// $f-dropdown-border-color: scale-color($white, $lightness: -20%);\n\n// We use these to style the triangle pip.\n// $f-dropdown-triangle-size: 6px;\n// $f-dropdown-triangle-color: $white;\n// $f-dropdown-triangle-side-offset: 10px;\n\n// We use these to control styles for the list elements.\n// $f-dropdown-list-style: none;\n// $f-dropdown-font-color: $charcoal;\n// $f-dropdown-font-size: rem-calc(14);\n// $f-dropdown-list-padding: rem-calc(5, 10);\n// $f-dropdown-line-height: rem-calc(18);\n// $f-dropdown-list-hover-bg: $smoke  ;\n// $dropdown-mobile-default-float: 0;\n\n// We use this to control the styles for when the dropdown has custom content.\n// $f-dropdown-content-padding: rem-calc(20);\n\n// Default radius for dropdown.\n// $f-dropdown-radius: $global-radius;\n\n\n// 09. Dropdown Buttons\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-button-classes: $include-html-classes;\n\n// We use these to set the color of the pip in dropdown buttons\n// $dropdown-button-pip-color: $white;\n// $dropdown-button-pip-color-alt: $oil;\n\n// $button-pip-tny: rem-calc(6);\n// $button-pip-sml: rem-calc(7);\n// $button-pip-med: rem-calc(9);\n// $button-pip-lrg: rem-calc(11);\n\n// We use these to style tiny dropdown buttons\n// $dropdown-button-padding-tny: $button-pip-tny * 7;\n// $dropdown-button-pip-size-tny: $button-pip-tny;\n// $dropdown-button-pip-opposite-tny: $button-pip-tny * 3;\n// $dropdown-button-pip-top-tny: -$button-pip-tny / 2 + rem-calc(1);\n\n// We use these to style small dropdown buttons\n// $dropdown-button-padding-sml: $button-pip-sml * 7;\n// $dropdown-button-pip-size-sml: $button-pip-sml;\n// $dropdown-button-pip-opposite-sml: $button-pip-sml * 3;\n// $dropdown-button-pip-top-sml: -$button-pip-sml / 2 + rem-calc(1);\n\n// We use these to style medium dropdown buttons\n// $dropdown-button-padding-med: $button-pip-med * 6 + rem-calc(3);\n// $dropdown-button-pip-size-med: $button-pip-med - rem-calc(3);\n// $dropdown-button-pip-opposite-med: $button-pip-med * 2.5;\n// $dropdown-button-pip-top-med: -$button-pip-med / 2 + rem-calc(2);\n\n// We use these to style large dropdown buttons\n// $dropdown-button-padding-lrg: $button-pip-lrg * 5 + rem-calc(3);\n// $dropdown-button-pip-size-lrg: $button-pip-lrg - rem-calc(6);\n// $dropdown-button-pip-opposite-lrg: $button-pip-lrg * 2.5;\n// $dropdown-button-pip-top-lrg: -$button-pip-lrg / 2 + rem-calc(3);\n\n// 10. Flex Video\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-media-classes: $include-html-classes;\n\n// We use these to control video container padding and margins\n// $flex-video-padding-top: rem-calc(25);\n// $flex-video-padding-bottom: 67.5%;\n// $flex-video-margin-bottom: rem-calc(16);\n\n// We use this to control widescreen bottom padding\n// $flex-video-widescreen-padding-bottom: 56.34%;\n\n// 11. Forms\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-form-classes: $include-html-classes;\n\n// We use this to set the base for lots of form spacing and positioning styles\n// $form-spacing: rem-calc(16);\n\n// We use these to style the labels in different ways\n// $form-label-pointer: pointer;\n// $form-label-font-size: rem-calc(14);\n// $form-label-font-weight: $font-weight-normal;\n// $form-label-line-height: 1.5;\n// $form-label-font-color: scale-color($black, $lightness: 30%);\n// $form-label-small-transform: capitalize;\n// $form-label-bottom-margin: 0;\n// $input-font-family: inherit;\n// $input-font-color: rgba(0,0,0,0.75);\n// $input-font-size: rem-calc(14);\n// $input-bg-color: $white;\n// $input-focus-bg-color: scale-color($white, $lightness: -2%);\n// $input-border-color: scale-color($white, $lightness: -20%);\n// $input-focus-border-color: scale-color($white, $lightness: -40%);\n// $input-border-style: solid;\n// $input-border-width: 1px;\n// $input-border-radius: $global-radius;\n// $input-disabled-bg: $gainsboro;\n// $input-disabled-cursor: $cursor-default-value;\n// $input-box-shadow: inset 0 1px 2px rgba(0,0,0,0.1);\n\n// We use these to style the fieldset border and spacing.\n// $fieldset-border-style: solid;\n// $fieldset-border-width: 1px;\n// $fieldset-border-color: $gainsboro;\n// $fieldset-padding: rem-calc(20);\n// $fieldset-margin: rem-calc(18 0);\n\n// We use these to style the legends when you use them\n// $legend-bg: $white;\n// $legend-font-weight: $font-weight-bold;\n// $legend-padding: rem-calc(0 3);\n\n// We use these to style the prefix and postfix input elements\n// $input-prefix-bg: scale-color($white, $lightness: -5%);\n// $input-prefix-border-color: scale-color($white, $lightness: -20%);\n// $input-prefix-border-size: 1px;\n// $input-prefix-border-type: solid;\n// $input-prefix-overflow: hidden;\n// $input-prefix-font-color: $oil;\n// $input-prefix-font-color-alt: $white;\n\n// We use this setting to turn on/off HTML5 number spinners (the up/down arrows)\n// $input-number-spinners: true;\n\n// We use these to style the error states for inputs and labels\n// $input-error-message-padding: rem-calc(6 9 9);\n// $input-error-message-top: -1px;\n// $input-error-message-font-size: rem-calc(12);\n// $input-error-message-font-weight: $font-weight-normal;\n// $input-error-message-font-style: italic;\n// $input-error-message-font-color: $white;\n// $input-error-message-font-color-alt: $oil;\n\n// We use this to style the glowing effect of inputs when focused\n// $input-include-glowing-effect: true;\n// $glowing-effect-fade-time: 0.45s;\n// $glowing-effect-color: $input-focus-border-color;\n\n// Select variables\n// $select-bg-color: $ghost;\n// $select-hover-bg-color: scale-color($select-bg-color, $lightness: -3%);\n\n// 12. Icon Bar\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// We use these to style the icon-bar and items\n// $include-html-icon-bar-classes: $include-html-classes;\n// $icon-bar-bg: $oil;\n// $icon-bar-font-color: $white;\n// $icon-bar-font-size: 1rem;\n// $icon-bar-hover-color: $primary-color;\n// $icon-bar-icon-color: $white;\n// $icon-bar-icon-size: 1.875rem;\n// $icon-bar-image-width: 1.875rem;\n// $icon-bar-image-height: 1.875rem;\n// $icon-bar-active-color: $primary-color;\n// $icon-bar-item-padding: 1.25rem;\n\n// 13. Inline Lists\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-inline-list-classes: $include-html-classes;\n\n// We use this to control the margins and padding of the inline list.\n// $inline-list-top-margin: 0;\n// $inline-list-opposite-margin: 0;\n// $inline-list-bottom-margin: rem-calc(17);\n// $inline-list-default-float-margin: rem-calc(-22);\n// $inline-list-default-float-list-margin: rem-calc(22);\n\n// $inline-list-padding: 0;\n\n// We use this to control the overflow of the inline list.\n// $inline-list-overflow: hidden;\n\n// We use this to control the list items\n// $inline-list-display: block;\n\n// We use this to control any elements within list items\n// $inline-list-children-display: block;\n\n// 14. Joyride\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-joyride-classes: $include-html-classes;\n\n// Controlling default Joyride styles\n// $joyride-tip-bg: $oil;\n// $joyride-tip-default-width: 300px;\n// $joyride-tip-padding: rem-calc(18 20 24);\n// $joyride-tip-border: solid 1px $charcoal;\n// $joyride-tip-radius: 4px;\n// $joyride-tip-position-offset: 22px;\n\n// Here, we're setting the tip font styles\n// $joyride-tip-font-color: $white;\n// $joyride-tip-font-size: rem-calc(14);\n// $joyride-tip-header-weight: $font-weight-bold;\n\n// This changes the nub size\n// $joyride-tip-nub-size: 10px;\n\n// This adjusts the styles for the timer when its enabled\n// $joyride-tip-timer-width: 50px;\n// $joyride-tip-timer-height: 3px;\n// $joyride-tip-timer-color: $steel;\n\n// This changes up the styles for the close button\n// $joyride-tip-close-color: $monsoon;\n// $joyride-tip-close-size: 24px;\n// $joyride-tip-close-weight: $font-weight-normal;\n\n// When Joyride is filling the screen, we use this style for the bg\n// $joyride-screenfill: rgba(0,0,0,0.5);\n\n// 15. Keystrokes\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-keystroke-classes: $include-html-classes;\n\n// We use these to control text styles.\n// $keystroke-font: \"Consolas\", \"Menlo\", \"Courier\", monospace;\n// $keystroke-font-size: inherit;\n// $keystroke-font-color: $jet;\n// $keystroke-font-color-alt: $white;\n// $keystroke-function-factor: -7%;\n\n// We use this to control keystroke padding.\n// $keystroke-padding: rem-calc(2 4 0);\n\n// We use these to control background and border styles.\n// $keystroke-bg: scale-color($white, $lightness: $keystroke-function-factor);\n// $keystroke-border-style: solid;\n// $keystroke-border-width: 1px;\n// $keystroke-border-color: scale-color($keystroke-bg, $lightness: $keystroke-function-factor);\n// $keystroke-radius: $global-radius;\n\n// 16. Labels\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-label-classes: $include-html-classes;\n\n// We use these to style the labels\n// $label-padding: rem-calc(4 8 4);\n// $label-radius: $global-radius;\n\n// We use these to style the label text\n// $label-font-sizing: rem-calc(11);\n// $label-font-weight: $font-weight-normal;\n// $label-font-color: $oil;\n// $label-font-color-alt: $white;\n// $label-font-family: $body-font-family;\n\n// 17. Magellan\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-magellan-classes: $include-html-classes;\n\n// $magellan-bg: $white;\n// $magellan-padding: 0 !important;\n\n// 18. Off-canvas\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-off-canvas-classes: $include-html-classes;\n\n// $tabbar-bg: $oil;\n// $tabbar-height: rem-calc(45);\n// $tabbar-icon-width: $tabbar-height;\n// $tabbar-line-height: $tabbar-height;\n// $tabbar-color: $white;\n// $tabbar-middle-padding: 0 rem-calc(10);\n\n// Off Canvas Divider Styles\n// $tabbar-right-section-border: solid 1px scale-color($tabbar-bg, $lightness: 13%);\n// $tabbar-left-section-border: solid 1px scale-color($tabbar-bg, $lightness: -50%);\n\n// Off Canvas Tab Bar Headers\n// $tabbar-header-color: $white;\n// $tabbar-header-weight: $font-weight-bold;\n// $tabbar-header-line-height: $tabbar-height;\n// $tabbar-header-margin: 0;\n\n// Off Canvas Menu Variables\n// $off-canvas-width: rem-calc(250);\n// $off-canvas-bg: $oil;\n// $off-canvas-bg-hover: scale-color($tabbar-bg, $lightness: -30%);\n\n// Off Canvas Menu List Variables\n// $off-canvas-label-padding: 0.3rem rem-calc(15);\n// $off-canvas-label-color: $aluminum;\n// $off-canvas-label-text-transform: uppercase;\n// $off-canvas-label-font-size: rem-calc(12);\n// $off-canvas-label-font-weight: $font-weight-bold;\n// $off-canvas-label-bg: $tuatara;\n// $off-canvas-label-border-top: 1px solid scale-color($tuatara, $lightness: 14%);\n// $off-canvas-label-border-bottom: none;\n// $off-canvas-label-margin:0;\n// $off-canvas-link-padding: rem-calc(10, 15);\n// $off-canvas-link-color: rgba($white, 0.7);\n// $off-canvas-link-border-bottom: 1px solid scale-color($off-canvas-bg, $lightness: -25%);\n// $off-canvas-back-bg: $tuatara;\n// $off-canvas-back-border-top: $off-canvas-label-border-top;\n// $off-canvas-back-border-bottom: $off-canvas-label-border-bottom;\n// $off-canvas-back-hover-bg: scale-color($off-canvas-back-bg, $lightness: -30%);\n// $off-canvas-back-hover-border-top: 1px solid scale-color($off-canvas-label-bg, $lightness: 14%);\n// $off-canvas-back-hover-border-bottom: none;\n\n// Off Canvas Menu Icon Variables\n// $tabbar-menu-icon-color: $white;\n// $tabbar-menu-icon-hover: scale-color($tabbar-menu-icon-color, $lightness: -30%);\n\n// $tabbar-menu-icon-text-indent: rem-calc(35);\n// $tabbar-menu-icon-width: $tabbar-height;\n// $tabbar-menu-icon-height: $tabbar-height;\n// $tabbar-menu-icon-padding: 0;\n\n// $tabbar-hamburger-icon-width: rem-calc(16);\n// $tabbar-hamburger-icon-left: false;\n// $tabbar-hamburger-icon-top: false;\n// $tabbar-hamburger-icon-thickness: 1px;\n// $tabbar-hamburger-icon-gap: 6px;\n\n// Off Canvas Back-Link Overlay\n// $off-canvas-overlay-transition: background 300ms ease;\n// $off-canvas-overlay-cursor: pointer;\n// $off-canvas-overlay-box-shadow: -4px 0 4px rgba($black, 0.5), 4px 0 4px rgba($black, 0.5);\n// $off-canvas-overlay-background: rgba($white, 0.2);\n// $off-canvas-overlay-background-hover: rgba($white, 0.05);\n\n// Transition Variables\n// $menu-slide: \"transform 500ms ease\";\n\n// 19. Orbit\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-orbit-classes: $include-html-classes;\n\n// We use these to control the caption styles\n// $orbit-container-bg: none;\n// $orbit-caption-bg: rgba(51,51,51, 0.8);\n// $orbit-caption-font-color: $white;\n// $orbit-caption-font-size: rem-calc(14);\n// $orbit-caption-position: \"bottom\"; // Supported values: \"bottom\", \"under\"\n// $orbit-caption-padding: rem-calc(10 14);\n// $orbit-caption-height: auto;\n\n// We use these to control the left/right nav styles\n// $orbit-nav-bg: transparent;\n// $orbit-nav-bg-hover: rgba(0,0,0,0.3);\n// $orbit-nav-arrow-color: $white;\n// $orbit-nav-arrow-color-hover: $white;\n\n// We use these to control the timer styles\n// $orbit-timer-bg: rgba(255,255,255,0.3);\n// $orbit-timer-show-progress-bar: true;\n\n// We use these to control the bullet nav styles\n// $orbit-bullet-nav-color: $iron;\n// $orbit-bullet-nav-color-active: $aluminum;\n// $orbit-bullet-radius: rem-calc(9);\n\n// We use these to controls the style of slide numbers\n// $orbit-slide-number-bg: rgba(0,0,0,0);\n// $orbit-slide-number-font-color: $white;\n// $orbit-slide-number-padding: rem-calc(5);\n\n// Hide controls on small\n// $orbit-nav-hide-for-small: true;\n// $orbit-bullet-hide-for-small: true;\n// $orbit-timer-hide-for-small: true;\n\n// Graceful Loading Wrapper and preloader\n// $wrapper-class: \"slideshow-wrapper\";\n// $preloader-class: \"preloader\";\n\n// 20. Pagination\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-pagination-classes: $include-html-classes;\n\n// We use these to control the pagination container\n// $pagination-height: rem-calc(24);\n// $pagination-margin: rem-calc(-5);\n\n// We use these to set the list-item properties\n// $pagination-li-float: $default-float;\n// $pagination-li-height: rem-calc(24);\n// $pagination-li-font-color: $jet;\n// $pagination-li-font-size: rem-calc(14);\n// $pagination-li-margin: rem-calc(5);\n\n// We use these for the pagination anchor links\n// $pagination-link-pad: rem-calc(1 10 1);\n// $pagination-link-font-color: $aluminum;\n// $pagination-link-active-bg: scale-color($white, $lightness: -10%);\n\n// We use these for disabled anchor links\n// $pagination-link-unavailable-cursor: default;\n// $pagination-link-unavailable-font-color: $aluminum;\n// $pagination-link-unavailable-bg-active: transparent;\n\n// We use these for currently selected anchor links\n// $pagination-link-current-background: $primary-color;\n// $pagination-link-current-font-color: $white;\n// $pagination-link-current-font-weight: $font-weight-bold;\n// $pagination-link-current-cursor: default;\n// $pagination-link-current-active-bg: $primary-color;\n\n// 21. Panels\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-panel-classes: $include-html-classes;\n\n// We use these to control the background and border styles\n$panel-bg: $grey-1;\n// $panel-border-style: solid;\n// $panel-border-size: 1px;\n\n// We use this % to control how much we darken things on hover\n// $panel-function-factor: -11%;\n// $panel-border-color: scale-color($panel-bg, $lightness: $panel-function-factor);\n\n// We use these to set default inner padding and bottom margin\n// $panel-margin-bottom: rem-calc(20);\n// $panel-padding: rem-calc(20);\n\n// We use these to set default font colors\n// $panel-font-color: $oil;\n// $panel-font-color-alt: $white;\n\n// $panel-header-adjust: true;\n// $callout-panel-link-color: $primary-color;\n\n// 22. Pricing Tables\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-pricing-classes: $include-html-classes;\n\n// We use this to control the border color\n// $price-table-border: solid 1px $gainsboro;\n\n// We use this to control the bottom margin of the pricing table\n// $price-table-margin-bottom: rem-calc(20);\n\n// We use these to control the title styles\n// $price-title-bg: $oil;\n// $price-title-padding: rem-calc(15 20);\n// $price-title-align: center;\n// $price-title-color: $smoke;\n// $price-title-weight: $font-weight-normal;\n// $price-title-size: rem-calc(16);\n// $price-title-font-family: $body-font-family;\n\n// We use these to control the price styles\n// $price-money-bg: $vapor  ;\n// $price-money-padding: rem-calc(15 20);\n// $price-money-align: center;\n// $price-money-color: $oil;\n// $price-money-weight: $font-weight-normal;\n// $price-money-size: rem-calc(32);\n// $price-money-font-family: $body-font-family;\n\n// We use these to control the description styles\n// $price-bg: $white;\n// $price-desc-color: $monsoon;\n// $price-desc-padding: rem-calc(15);\n// $price-desc-align: center;\n// $price-desc-font-size: rem-calc(12);\n// $price-desc-weight: $font-weight-normal;\n// $price-desc-line-height: 1.4;\n// $price-desc-bottom-border: dotted 1px $gainsboro;\n\n// We use these to control the list item styles\n// $price-item-color: $oil;\n// $price-item-padding: rem-calc(15);\n// $price-item-align: center;\n// $price-item-font-size: rem-calc(14);\n// $price-item-weight: $font-weight-normal;\n// $price-item-bottom-border: dotted 1px $gainsboro;\n\n// We use these to control the CTA area styles\n// $price-cta-bg: $white;\n// $price-cta-align: center;\n// $price-cta-padding: rem-calc(20 20 0);\n\n// 23. Progress Bar\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-media-classes: $include-html-classes;\n\n// We use this to set the progress bar height\n// $progress-bar-height: rem-calc(25);\n// $progress-bar-color: $vapor  ;\n\n// We use these to control the border styles\n// $progress-bar-border-color: scale-color($white, $lightness: 20%);\n// $progress-bar-border-size: 1px;\n// $progress-bar-border-style: solid;\n// $progress-bar-border-radius: $global-radius;\n\n// We use these to control the margin & padding\n// $progress-bar-pad: rem-calc(2);\n// $progress-bar-margin-bottom: rem-calc(10);\n\n// We use these to set the meter colors\n// $progress-meter-color: $primary-color;\n// $progress-meter-secondary-color: $secondary-color;\n// $progress-meter-success-color: $success-color;\n// $progress-meter-alert-color: $alert-color;\n\n// 24. Range Slider\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-range-slider-classes: $include-html-classes;\n\n// These variables define the slider bar styles\n// $range-slider-bar-width: 100%;\n// $range-slider-bar-height: rem-calc(16);\n\n// $range-slider-bar-border-width: 1px;\n// $range-slider-bar-border-style: solid;\n// $range-slider-bar-border-color: $gainsboro;\n// $range-slider-radius: $global-radius;\n// $range-slider-round: $global-rounded;\n// $range-slider-bar-bg-color: $ghost;\n\n// Vertical bar styles\n// $range-slider-vertical-bar-width: rem-calc(16);\n// $range-slider-vertical-bar-height: rem-calc(200);\n\n// These variables define the slider handle styles\n// $range-slider-handle-width: rem-calc(32);\n// $range-slider-handle-height: rem-calc(22);\n// $range-slider-handle-position-top: rem-calc(-5);\n// $range-slider-handle-bg-color: $primary-color;\n// $range-slider-handle-border-width: 1px;\n// $range-slider-handle-border-style: solid;\n// $range-slider-handle-border-color: none;\n// $range-slider-handle-radius: $global-radius;\n// $range-slider-handle-round: $global-rounded;\n// $range-slider-handle-bg-hover-color: scale-color($primary-color, $lightness: -12%);\n// $range-slider-handle-cursor: pointer;\n\n// 25. Reveal\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-reveal-classes: $include-html-classes;\n\n// We use these to control the style of the reveal overlay.\n// $reveal-overlay-bg: rgba($black, .45);\n// $reveal-overlay-bg-old: $black;\n\n// We use these to control the style of the modal itself.\n// $reveal-modal-bg: $white;\n// $reveal-position-top: rem-calc(100);\n// $reveal-default-width: 80%;\n// $reveal-max-width: $row-width;\n// $reveal-modal-padding: rem-calc(20);\n// $reveal-box-shadow: 0 0 10px rgba($black,.4);\n\n// We use these to style the reveal close button\n// $reveal-close-font-size: rem-calc(40);\n// $reveal-close-top: rem-calc(8);\n// $reveal-close-side: rem-calc(11);\n// $reveal-close-color: $base;\n// $reveal-close-weight: $font-weight-bold;\n\n// We use this to set the default radius used throughout the core.\n// $reveal-radius: $global-radius;\n// $reveal-round: $global-rounded;\n\n// We use these to control the modal border\n// $reveal-border-style: solid;\n// $reveal-border-width: 1px;\n// $reveal-border-color: $steel;\n\n// $reveal-modal-class: \"reveal-modal\";\n// $close-reveal-modal-class: \"close-reveal-modal\";\n\n// 26. Side Nav\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-nav-classes: $include-html-classes;\n\n// We use this to control padding.\n$side-nav-padding: rem-calc(0 0 0 0);\n\n// We use these to control list styles.\n// $side-nav-list-type: none;\n// $side-nav-list-position: inside;\n$side-nav-list-margin: rem-calc(0 0 0 0);\n\n// We use these to control link styles.\n$side-nav-link-color: $primary-color;\n$side-nav-link-color-active: scale-color($side-nav-link-color, $lightness: -40%);\n$side-nav-link-color-hover: scale-color($side-nav-link-color, $lightness: -40%);\n$side-nav-font-size: rem-calc(16);\n\n// $side-nav-link-bg-hover: hsla(0, 0, 0, 0.025);\n// $side-nav-link-margin: 0;\n// $side-nav-link-padding: rem-calc(7 14);\n// $side-nav-font-size: rem-calc(14);\n// $side-nav-font-weight: $font-weight-normal;\n// $side-nav-font-weight-active: $side-nav-font-weight;\n// $side-nav-font-family: $body-font-family;\n// $side-nav-font-family-active: $side-nav-font-family;\n\n// We use these to control heading styles.\n// $side-nav-heading-color: $side-nav-link-color;\n// $side-nav-heading-font-size: $side-nav-font-size;\n// $side-nav-heading-font-weight: bold;\n// $side-nav-heading-text-transform: uppercase;\n\n// We use these to control border styles\n$side-nav-divider-size: 1px;\n$side-nav-divider-style: solid;\n$side-nav-divider-color: $grey-1;\n\n\n\n// 27. Split Buttons\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-button-classes: $include-html-classes;\n\n// We use these to control different shared styles for Split Buttons\n// $split-button-function-factor: 10%;\n// $split-button-pip-color: $white;\n// $split-button-pip-color-alt: $oil;\n// $split-button-active-bg-tint: rgba(0,0,0,0.1);\n\n// We use these to control tiny split buttons\n// $split-button-padding-tny: $button-pip-tny * 10;\n// $split-button-span-width-tny: $button-pip-tny * 6;\n// $split-button-pip-size-tny: $button-pip-tny;\n// $split-button-pip-top-tny: $button-pip-tny * 2;\n// $split-button-pip-default-float-tny: rem-calc(-6);\n\n// We use these to control small split buttons\n// $split-button-padding-sml: $button-pip-sml * 10;\n// $split-button-span-width-sml: $button-pip-sml * 6;\n// $split-button-pip-size-sml: $button-pip-sml;\n// $split-button-pip-top-sml: $button-pip-sml * 1.5;\n// $split-button-pip-default-float-sml: rem-calc(-6);\n\n// We use these to control medium split buttons\n// $split-button-padding-med: $button-pip-med * 9;\n// $split-button-span-width-med: $button-pip-med * 5.5;\n// $split-button-pip-size-med: $button-pip-med - rem-calc(3);\n// $split-button-pip-top-med: $button-pip-med * 1.5;\n// $split-button-pip-default-float-med: rem-calc(-6);\n\n// We use these to control large split buttons\n// $split-button-padding-lrg: $button-pip-lrg * 8;\n// $split-button-span-width-lrg: $button-pip-lrg * 5;\n// $split-button-pip-size-lrg: $button-pip-lrg - rem-calc(6);\n// $split-button-pip-top-lrg: $button-pip-lrg + rem-calc(5);\n// $split-button-pip-default-float-lrg: rem-calc(-6);\n\n// 28. Sub Nav\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-nav-classes: $include-html-classes;\n\n// We use these to control margin and padding\n// $sub-nav-list-margin: rem-calc(-4 0 18);\n// $sub-nav-list-padding-top: rem-calc(4);\n\n// We use this to control the definition\n// $sub-nav-font-family: $body-font-family;\n// $sub-nav-font-size: rem-calc(14);\n// $sub-nav-font-color: $aluminum;\n// $sub-nav-font-weight: $font-weight-normal;\n// $sub-nav-text-decoration: none;\n// $sub-nav-padding: rem-calc(3 16);\n// $sub-nav-border-radius: 3px;\n// $sub-nav-font-color-hover: scale-color($sub-nav-font-color, $lightness: -25%);\n\n// We use these to control the active item styles\n// $sub-nav-active-font-weight: $font-weight-normal;\n// $sub-nav-active-bg: $primary-color;\n// $sub-nav-active-bg-hover: scale-color($sub-nav-active-bg, $lightness: -14%);\n// $sub-nav-active-color: $white;\n// $sub-nav-active-padding: $sub-nav-padding;\n// $sub-nav-active-cursor: default;\n\n// $sub-nav-item-divider: \"\";\n// $sub-nav-item-divider-margin: rem-calc(12);\n\n// 29. Switch\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-form-classes: $include-html-classes;\n\n// Controlling border styles and background colors for the switch container\n// $switch-border-color: scale-color($white, $lightness: -20%);\n// $switch-border-style: solid;\n// $switch-border-width: 1px;\n// $switch-bg: $white;\n\n// We use these to control the switch heights for our default classes\n// $switch-height-tny: rem-calc(22);\n// $switch-height-sml: rem-calc(28);\n// $switch-height-med: rem-calc(36);\n// $switch-height-lrg: rem-calc(44);\n// $switch-bottom-margin: rem-calc(20);\n\n// We use these to control default font sizes for our classes.\n// $switch-font-size-tny: 11px;\n// $switch-font-size-sml: 12px;\n// $switch-font-size-med: 14px;\n// $switch-font-size-lrg: 17px;\n// $switch-label-side-padding: 6px;\n\n// We use these to style the switch-paddle\n// $switch-paddle-bg: $white;\n// $switch-paddle-fade-to-color: scale-color($switch-paddle-bg, $lightness: -10%);\n// $switch-paddle-border-color: scale-color($switch-paddle-bg, $lightness: -35%);\n// $switch-paddle-border-width: 1px;\n// $switch-paddle-border-style: solid;\n// $switch-paddle-transition-speed: .1s;\n// $switch-paddle-transition-ease: ease-out;\n// $switch-positive-color: scale-color($success-color, $lightness: 94%);\n// $switch-negative-color: $white-smoke;\n\n// Outline Style for tabbing through switches\n// $switch-label-outline: 1px dotted $jumbo;\n\n// 30. Tables\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-table-classes: $include-html-classes;\n\n// These control the background color for the table and even rows\n// $table-bg: $white;\n$table-even-row-bg: $grey-1;\n\n// These control the table cell border style\n// $table-border-style: solid;\n// $table-border-size: 1px;\n// $table-border-color: $gainsboro;\n\n// These control the table head styles\n$table-head-bg: $grey-2;\n// $table-head-font-size: rem-calc(14);\n// $table-head-font-color: $jet;\n// $table-head-font-weight: $font-weight-bold;\n// $table-head-padding: rem-calc(8 10 10);\n\n// These control the row padding and font styles\n// $table-row-padding: rem-calc(9 10);\n// $table-row-font-size: rem-calc(14);\n// $table-row-font-color: $jet;\n// $table-line-height: rem-calc(18);\n\n// These are for controlling the layout, display and margin of tables\n// $table-layout: auto;\n// $table-display: table-cell;\n// $table-margin-bottom: rem-calc(20);\n\n// 31. Tabs\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-tabs-classes: $include-html-classes;\n\n// $tabs-navigation-padding: rem-calc(16);\n// $tabs-navigation-bg-color: $silver  ;\n// $tabs-navigation-active-bg-color: $white;\n// $tabs-navigation-hover-bg-color: scale-color($tabs-navigation-bg-color, $lightness: -6%);\n// $tabs-navigation-font-color: $jet;\n// $tabs-navigation-active-font-color: $tabs-navigation-font-color;\n// $tabs-navigation-font-size: rem-calc(16);\n// $tabs-navigation-font-family: $body-font-family;\n\n// $tabs-content-margin-bottom: rem-calc(24);\n// $tabs-content-padding: $column-gutter/2;\n\n// $tabs-vertical-navigation-margin-bottom: 1.25rem;\n\n// 32. Thumbnails\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-media-classes: $include-html-classes;\n\n// We use these to control border styles\n// $thumb-border-style: solid;\n// $thumb-border-width: 4px;\n// $thumb-border-color: $white;\n// $thumb-box-shadow: 0 0 0 1px rgba($black,.2);\n// $thumb-box-shadow-hover: 0 0 6px 1px rgba($primary-color,0.5);\n\n// Radius and transition speed for thumbs\n// $thumb-radius: $global-radius;\n// $thumb-transition-speed: 200ms;\n\n// 33. Tooltips\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-tooltip-classes: $include-html-classes;\n\n// $has-tip-border-bottom: dotted 1px $iron;\n// $has-tip-font-weight: $font-weight-bold;\n// $has-tip-font-color: $oil;\n// $has-tip-border-bottom-hover: dotted 1px scale-color($primary-color, $lightness: -55%);\n// $has-tip-font-color-hover: $primary-color;\n// $has-tip-cursor-type: help;\n\n// $tooltip-padding: rem-calc(12);\n// $tooltip-bg: $oil;\n// $tooltip-font-size: rem-calc(14);\n// $tooltip-font-weight: $font-weight-normal;\n// $tooltip-font-color: $white;\n// $tooltip-line-height: 1.3;\n// $tooltip-close-font-size: rem-calc(10);\n// $tooltip-close-font-weight: $font-weight-normal;\n// $tooltip-close-font-color: $monsoon;\n// $tooltip-font-size-sml: rem-calc(14);\n// $tooltip-radius: $global-radius;\n// $tooltip-rounded: $global-rounded;\n// $tooltip-pip-size: 5px;\n// $tooltip-max-width: 300px;\n\n// 34. Top Bar\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-top-bar-classes: $include-html-classes;\n\n// Height and margin\n$topbar-height: rem-calc(50);\n// $topbar-margin-bottom: 0;\n\n// Controlling the styles for the title in the top bar\n$topbar-title-weight: $font-weight-bold;\n$topbar-title-font-size: rem-calc(19);\n\n// Style the top bar dropdown elements\n// $topbar-dropdown-bg: $oil;\n// $topbar-dropdown-link-color: $white;\n// $topbar-dropdown-link-bg: $ci-2;\n// $topbar-dropdown-link-weight: $font-weight-normal;\n// $topbar-dropdown-toggle-size: 5px;\n// $topbar-dropdown-toggle-color: $ci-2;\n// $topbar-dropdown-toggle-alpha: 0.4;\n\n// Set the link colors and styles for top-level nav\n// $topbar-link-color: #000;\n// $topbar-link-color-hover: #000;\n// $topbar-link-color-active: #000;\n// $topbar-link-color-active-hover: #000;\n// $topbar-link-weight: $font-weight-normal;\n$topbar-link-font-size: rem-calc(15);\n// $topbar-link-hover-lightness: -10%; // Darken by 10%\n// $topbar-link-bg: $topbar-bg;\n// $topbar-link-bg-color-hover: #ff0;\n// $topbar-link-bg-hover: #f00;\n// $topbar-link-bg-active: $primary-color;\n// $topbar-link-bg-active-hover: scale-color($primary-color, $lightness: -14%);\n// $topbar-link-font-family: $body-font-family;\n$topbar-link-text-transform: uppercase;\n// $topbar-link-padding: $topbar-height / 3;\n// $topbar-back-link-size: $h5-font-size;\n// $topbar-link-dropdown-padding: 20px;\n\n// $topbar-button-font-size: 0.75rem;\n// $topbar-button-top: 7px;\n\n// $topbar-dropdown-label-color: #f77;\n// $topbar-dropdown-label-text-transform: uppercase;\n// $topbar-dropdown-label-font-weight: $font-weight-bold;\n// $topbar-dropdown-label-font-size: rem-calc(10);\n// $topbar-dropdown-label-bg: $oil;\n\n// Top menu icon styles\n$topbar-menu-link-transform: uppercase;\n// $topbar-menu-link-font-size: rem-calc(13);\n// $topbar-menu-link-weight: $font-weight-bold;\n// $topbar-menu-link-color: $white;\n// $topbar-menu-icon-color: $white;\n// $topbar-menu-link-color-toggled: $ci-6;\n// $topbar-menu-icon-color-toggled: $ci-6;\n\n// Transitions and breakpoint styles\n// $topbar-transition-speed: 300ms;\n// Using rem-calc for the below breakpoint causes issues with top bar\n$topbar-breakpoint: #{lower-bound($large-range)}; // Change to 9999px for always mobile layout\n$topbar-media-query: \"only screen and (min-width: #{$topbar-breakpoint})\" !default;\n\n// Divider Styles\n$topbar-divider-border-bottom: solid 0px scale-color($topbar-bg-color, $lightness: 23%);\n$topbar-divider-border-top: solid 0px scale-color($topbar-bg-color, $lightness: -50%);\n\n// Sticky Class\n// $topbar-sticky-class: \".sticky\";\n// $topbar-arrows: true; //Set false to remove the triangle icon from the menu item\n\n// 36. Visibility Classes\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-visibility-classes: $include-html-classes;\n// $include-table-visibility-classes: true;\n// $include-legacy-visibility-classes: true;\n// $include-accessibility-classes: true;\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n@import \"buttons\";\n\n//\n// @variables\n//\n$include-html-form-classes: $include-html-classes !default;\n\n// We use this to set the base for lots of form spacing and positioning styles\n$form-spacing: rem-calc(16) !default;\n\n// We use these to style the labels in different ways\n$form-label-pointer: pointer !default;\n$form-label-font-size: rem-calc(14) !default;\n$form-label-font-weight: $font-weight-normal !default;\n$form-label-line-height: 1.5 !default;\n$form-label-font-color: scale-color($black, $lightness: 30%) !default;\n$form-label-small-transform: capitalize !default;\n$form-label-bottom-margin: 0 !default;\n$input-font-family: inherit !default;\n$input-font-color: rgba(0, 0, 0, 0.75) !default;\n$input-font-size: rem-calc(14) !default;\n$input-bg-color: $white !default;\n$input-focus-bg-color: scale-color($white, $lightness: -2%) !default;\n$input-border-color: scale-color($white, $lightness: -20%) !default;\n$input-focus-border-color: scale-color($white, $lightness: -40%) !default;\n$input-border-style: solid !default;\n$input-border-width: 1px !default;\n$input-border-radius: $global-radius !default;\n$input-disabled-bg: $gainsboro !default;\n$input-disabled-cursor: $cursor-default-value !default;\n$input-box-shadow: inset 0 1px 2px rgba(0, 0, 0, 0.1) !default;\n$input-include-glowing-effect: true !default;\n\n// We use these to style the fieldset border and spacing.\n$fieldset-border-style: solid !default;\n$fieldset-border-width: 1px !default;\n$fieldset-border-color: $gainsboro !default;\n$fieldset-padding: rem-calc(20) !default;\n$fieldset-margin: rem-calc(18 0) !default;\n\n// We use these to style the legends when you use them\n$legend-bg: $white !default;\n$legend-font-weight: $font-weight-bold !default;\n$legend-padding: rem-calc(0 3) !default;\n\n// We use these to style the prefix and postfix input elements\n$input-prefix-bg: scale-color($white, $lightness: -5%) !default;\n$input-prefix-border-color: scale-color($white, $lightness: -20%) !default;\n$input-prefix-border-size: 1px !default;\n$input-prefix-border-type: solid !default;\n$input-prefix-overflow: hidden !default;\n$input-prefix-font-color: $oil !default;\n$input-prefix-font-color-alt: $white !default;\n\n// We use this setting to turn on/off HTML5 number spinners (the up/down arrows)\n$input-number-spinners: true !default;\n\n// We use these to style the error states for inputs and labels\n$input-error-message-padding: rem-calc(6 9 9) !default;\n$input-error-message-top: -1px !default;\n$input-error-message-font-size: rem-calc(12) !default;\n$input-error-message-font-weight: $font-weight-normal !default;\n$input-error-message-font-style: italic !default;\n$input-error-message-font-color: $white !default;\n$input-error-message-bg-color: $alert-color !default;\n$input-error-message-font-color-alt: $oil !default;\n\n// We use this to style the glowing effect of inputs when focused\n$glowing-effect-fade-time: 0.45s !default;\n$glowing-effect-color: $input-focus-border-color !default;\n\n// Select variables\n$select-bg-color: $ghost !default;\n$select-hover-bg-color: scale-color($select-bg-color, $lightness: -3%) !default;\n\n//\n// @MIXINS\n//\n\n// We use this mixin to give us form styles for rows inside of forms\n@mixin form-row-base {\n  .row {\n    margin: 0 calc((-1 * $form-spacing) / 2);\n\n    .column,\n    .columns {\n      padding: 0 calc($form-spacing / 2);\n    }\n\n    // Use this to collapse the margins of a form row\n    &.collapse {\n      margin: 0;\n\n      .column,\n      .columns {\n        padding: 0;\n      }\n\n      input {\n        @include side-radius($opposite-direction, 0);\n      }\n\n    }\n  }\n\n  input.column,\n  input.columns,\n  textarea.column,\n  textarea.columns {\n    padding-#{$default-float}: calc($form-spacing / 2);\n  }\n}\n\n// @MIXIN\n//\n// We use this mixin to give all basic form elements their style\n@mixin form-element {\n  background-color: $input-bg-color;\n  font-family: $input-font-family;\n\n  border: {\n    style: $input-border-style;\n    width: $input-border-width;\n    color: $input-border-color;\n  }\n\n  box-shadow: $input-box-shadow;\n  color: $input-font-color;\n  display: block;\n  font-size: $input-font-size;\n  margin: 0 0 $form-spacing 0;\n  padding: calc($form-spacing / 2);\n  height: ($input-font-size + ($form-spacing * 1.5) - rem-calc(1));\n  width: 100%;\n  @include box-sizing(border-box);\n\n  @if $input-include-glowing-effect {\n    @include block-glowing-effect(focus, $glowing-effect-fade-time, $glowing-effect-color);\n  }\n\n  // Basic focus styles\n  &:focus {\n    background: $input-focus-bg-color;\n    border-color: $input-focus-border-color;\n    outline: none;\n  }\n\n  // Disabled Styles\n  &:disabled {\n    background-color: $input-disabled-bg;\n    cursor: $input-disabled-cursor;\n  }\n\n  // Disabled background input background color\n  &[disabled],\n  &[readonly],\n  fieldset[disabled] & {\n    background-color: $input-disabled-bg;\n    cursor: $input-disabled-cursor;\n  }\n}\n\n// @MIXIN\n//\n// We use this mixin to create form labels\n//\n// $alignment - Alignment options. Default: false. Options: [right, inline, false]\n// $base-style - Control whether or not the base styles come through. Default: true.\n@mixin form-label($alignment: false, $base-style: true) {\n\n  // Control whether or not the base styles come through.\n  @if $base-style {\n    font-size: $form-label-font-size;\n    color: $form-label-font-color;\n    cursor: $form-label-pointer;\n    display: block;\n    font-weight: $form-label-font-weight;\n    line-height: $form-label-line-height;\n    margin-bottom: $form-label-bottom-margin;\n  }\n\n  // Alignment options\n  @if $alignment ==right {\n    float: none !important;\n    text-align: right;\n  }\n\n  @else if $alignment ==inline {\n    margin: 0 0 $form-spacing 0;\n    padding: calc($form-spacing / 2) + rem-calc($input-border-width) 0;\n  }\n}\n\n// We use this mixin to create postfix/prefix form Labels\n@mixin prefix-postfix-base {\n  display: block;\n  position: relative;\n  z-index: 2;\n  text-align: center;\n  width: 100%;\n  padding-top: 0;\n  padding-bottom: 0;\n  border-style: $input-prefix-border-type;\n  border-width: $input-prefix-border-size;\n  overflow: $input-prefix-overflow;\n  font-size: $form-label-font-size;\n  height: ($input-font-size + ($form-spacing * 1.5) - rem-calc(1));\n  line-height: ($input-font-size + ($form-spacing * 1.5) - rem-calc(1));\n}\n\n// @MIXIN\n//\n// We use this mixin to create prefix label styles\n// $bg - Default:$input-prefix-bg || scale-color($white, $lightness: -5%) !default;\n// $is-button - Toggle position settings if prefix is a button. Default:false\n//\n@mixin prefix($bg: $input-prefix-bg, $border: $input-prefix-border-color, $is-button: false) {\n\n  @if $bg {\n    $bg-lightness: lightness($bg);\n    background: $bg;\n    border-#{$opposite-direction}: none;\n\n    // Control the font color based on background brightness\n    @if $bg-lightness >70% or $bg ==yellow {\n      color: $input-prefix-font-color;\n    }\n\n    @else {\n      color: $input-prefix-font-color-alt;\n    }\n  }\n\n  @if $border {\n    border-color: $border;\n  }\n\n  @if $is-button {\n    padding-#{$default-float}: 0;\n    padding-#{$opposite-direction}: 0;\n    padding-top: 0;\n    padding-bottom: 0;\n    text-align: center;\n    border: none;\n  }\n\n}\n\n// @MIXIN\n//\n// We use this mixin to create postfix label styles\n// $bg - Default:$input-prefix-bg || scale-color($white, $lightness: -5%) !default;\n// $is-button - Toggle position settings if prefix is a button. Default: false\n@mixin postfix($bg: $input-prefix-bg, $border: $input-prefix-border-color, $is-button: false) {\n\n  @if $bg {\n    $bg-lightness: lightness($bg);\n    background: $bg;\n    border-#{$default-float}: none;\n\n    // Control the font color based on background brightness\n    @if $bg-lightness >70% or $bg ==yellow {\n      color: $input-prefix-font-color;\n    }\n\n    @else {\n      color: $input-prefix-font-color-alt;\n    }\n  }\n\n  @if $border {\n    border-color: $border;\n  }\n\n  @if $is-button {\n    padding-#{$default-float}: 0;\n    padding-#{$opposite-direction}: 0;\n    padding-top: 0;\n    padding-bottom: 0;\n    text-align: center;\n    border: none;\n  }\n\n}\n\n// We use this mixin to style fieldsets\n@mixin fieldset {\n  border: $fieldset-border-width $fieldset-border-style $fieldset-border-color;\n  padding: $fieldset-padding;\n  margin: $fieldset-margin;\n\n  // and legend styles\n  legend {\n    font-weight: $legend-font-weight;\n    background: $legend-bg;\n    padding: $legend-padding;\n    margin: 0;\n    margin-#{$default-float}: rem-calc(-3);\n  }\n}\n\n// @MIXIN\n//\n// We use this mixin to control border and background color of error inputs\n// $color - Default: $alert-color (found in settings file)\n@mixin form-error-color($color: $alert-color) {\n  border-color: $color;\n  background-color: rgba($color, 0.1);\n\n  // Go back to normal on focus\n  &:focus {\n    background: $input-focus-bg-color;\n    border-color: $input-focus-border-color;\n  }\n}\n\n// @MIXIN\n//\n// We use this simple mixin to style labels for error inputs\n// $color - Default:$alert-color. Found in settings file\n@mixin form-label-error-color($color: $alert-color) {\n  color: $color;\n}\n\n// @MIXIN\n//\n// We use this mixin to create error message styles\n// $bg - Default: $alert-color (Found in settings file)\n@mixin form-error-message($bg: $input-error-message-bg-color) {\n  display: block;\n  padding: $input-error-message-padding;\n  margin-top: $input-error-message-top;\n  margin-bottom: $form-spacing;\n  font-size: $input-error-message-font-size;\n  font-weight: $input-error-message-font-weight;\n  font-style: $input-error-message-font-style;\n\n  // We can control the text color based on the brightness of the background.\n  $bg-lightness: lightness($bg);\n  background: $bg;\n\n  @if $bg-lightness < 70% or $bg ==yellow {\n    color: $input-error-message-font-color;\n  }\n\n  @else {\n    color: $input-error-message-font-color-alt;\n  }\n}\n\n// We use this mixin to style select elements\n@mixin form-select {\n  -webkit-appearance: none !important;\n  border-radius: 0;\n  background-color: $select-bg-color;\n\n  // Hide the dropdown arrow shown in newer IE versions\n  &::-ms-expand {\n    display: none;\n  }\n\n  // The custom arrow has some fake horizontal padding so we can align it\n  // from the right side of the element without relying on CSS3\n  background-image: url(data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZlcnNpb249IjEuMSIgeD0iMTJweCIgeT0iMHB4IiB3aWR0aD0iMjRweCIgaGVpZ2h0PSIzcHgiIHZpZXdCb3g9IjAgMCA2IDMiIGVuYWJsZS1iYWNrZ3JvdW5kPSJuZXcgMCAwIDYgMyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI+PHBvbHlnb24gcG9pbnRzPSI1Ljk5MiwwIDIuOTkyLDMgLTAuMDA4LDAgIi8+PC9zdmc+);\n\n  // We can safely use leftmost and rightmost now\n  background-position: if($text-direction =='rtl', 0%, 100%) center;\n\n  background-repeat: no-repeat;\n\n  border: {\n    style: $input-border-style;\n    width: $input-border-width;\n    color: $input-border-color;\n  }\n\n  padding: calc($form-spacing / 2);\n  font-size: $input-font-size;\n  font-family: $body-font-family;\n  color: $input-font-color;\n  line-height: normal;\n  @include radius(0);\n\n  &.radius {\n    @include radius($global-radius);\n  }\n\n  &:hover {\n    background-color: $select-hover-bg-color;\n    border-color: $input-focus-border-color;\n  }\n\n  // Disabled Styles\n  &:disabled {\n    background-color: $input-disabled-bg;\n    cursor: $input-disabled-cursor;\n  }\n}\n\n// We use this mixin to turn on/off HTML5 number spinners\n@mixin html5number($browser, $on: true) {\n  @if $on==false {\n    @if $browser==webkit {\n      -webkit-appearance: none;\n      margin: 0;\n    }\n\n    @else if $browser==moz {\n      -moz-appearance: textfield;\n    }\n  }\n}\n\n@include exports(\"form\") {\n  @if $include-html-form-classes {\n\n    /* Standard Forms */\n    form {\n      margin: 0 0 $form-spacing;\n    }\n\n    /* Using forms within rows, we need to set some defaults */\n    form .row {\n      @include form-row-base;\n    }\n\n    /* Label Styles */\n    label {\n      @include form-label;\n\n      &.right {\n        @include form-label(right, false);\n      }\n\n      &.inline {\n        @include form-label(inline, false);\n      }\n\n      /* Styles for required inputs */\n      small {\n        text-transform: $form-label-small-transform;\n        color: scale-color($form-label-font-color, $lightness: 15%);\n      }\n    }\n\n    /* Attach elements to the beginning or end of an input */\n    .prefix,\n    .postfix {\n      @include prefix-postfix-base;\n    }\n\n    /* Adjust padding, alignment and radius if pre/post element is a button */\n    .postfix.button {\n      @include button-size(false, false);\n      @include postfix(false, false, true);\n    }\n\n    .prefix.button {\n      @include button-size(false, false);\n      @include prefix(false, false, true);\n    }\n\n    .prefix.button.radius {\n      @include radius(0);\n      @include side-radius($default-float, $button-radius);\n    }\n\n    .postfix.button.radius {\n      @include radius(0);\n      @include side-radius($opposite-direction, $button-radius);\n    }\n\n    .prefix.button.round {\n      @include radius(0);\n      @include side-radius($default-float, $button-round);\n    }\n\n    .postfix.button.round {\n      @include radius(0);\n      @include side-radius($opposite-direction, $button-round);\n    }\n\n    /* Separate prefix and postfix styles when on span or label so buttons keep their own */\n    span.prefix,\n    label.prefix {\n      @include prefix();\n    }\n\n    span.postfix,\n    label.postfix {\n      @include postfix();\n    }\n\n    /* We use this to get basic styling on all basic form elements */\n    #{text-inputs(all, 'input')} {\n      -webkit-appearance: none;\n      border-radius: 0;\n      @include form-element;\n\n      @if $input-include-glowing-effect ==false {\n        @include single-transition(all, 0.15s, linear);\n      }\n\n      &.radius {\n        @include radius($input-border-radius);\n      }\n    }\n\n    form {\n      .row {\n        .prefix-radius.row.collapse {\n\n          input,\n          textarea,\n          select {\n            @include radius(0);\n            @include side-radius($opposite-direction, $button-radius);\n          }\n\n          .prefix {\n            @include radius(0);\n            @include side-radius($default-float, $button-radius);\n          }\n        }\n\n        .postfix-radius.row.collapse {\n\n          input,\n          textarea,\n          select {\n            @include radius(0);\n            @include side-radius($default-float, $button-radius);\n          }\n\n          .postfix {\n            @include radius(0);\n            @include side-radius($opposite-direction, $button-radius);\n          }\n        }\n\n        .prefix-round.row.collapse {\n\n          input,\n          textarea,\n          select {\n            @include radius(0);\n            @include side-radius($opposite-direction, $button-round);\n          }\n\n          .prefix {\n            @include radius(0);\n            @include side-radius($default-float, $button-round);\n          }\n        }\n\n        .postfix-round.row.collapse {\n\n          input,\n          textarea,\n          select {\n            @include radius(0);\n            @include side-radius($default-float, $button-round);\n          }\n\n          .postfix {\n            @include radius(0);\n            @include side-radius($opposite-direction, $button-round);\n          }\n        }\n      }\n    }\n\n    input[type=\"submit\"] {\n      -webkit-appearance: none;\n      border-radius: 0;\n    }\n\n    /* Respect enforced amount of rows for textarea */\n    textarea[rows] {\n      height: auto;\n    }\n\n    /* Not allow resize out of parent */\n    textarea {\n      max-width: 100%;\n    }\n\n    /* Add height value for select elements to match text input height */\n    select {\n      @include form-select;\n      height: ($input-font-size + ($form-spacing * 1.5) - rem-calc(1));\n    }\n\n    /* Adjust margin for form elements below */\n    input[type=\"file\"],\n    input[type=\"checkbox\"],\n    input[type=\"radio\"],\n    select {\n      margin: 0 0 $form-spacing 0;\n    }\n\n    input[type=\"checkbox\"]+label,\n    input[type=\"radio\"]+label {\n      display: inline-block;\n      margin-#{$default-float}: $form-spacing * .5;\n      margin-#{$opposite-direction}: $form-spacing;\n      margin-bottom: 0;\n      vertical-align: baseline;\n    }\n\n    /* Normalize file input width */\n    input[type=\"file\"] {\n      width: 100%;\n    }\n\n    /* HTML5 Number spinners settings */\n    input[type=number] {\n      @include html5number(moz, $input-number-spinners)\n    }\n\n    input[type=\"number\"]::-webkit-inner-spin-button,\n    input[type=\"number\"]::-webkit-outer-spin-button {\n      @include html5number(webkit, $input-number-spinners);\n    }\n\n    /* We add basic fieldset styling */\n    fieldset {\n      @include fieldset;\n    }\n\n    /* Error Handling */\n\n    #{data('abide')} {\n\n      .error small.error,\n      .error span.error,\n      span.error,\n      small.error {\n        @include form-error-message;\n      }\n\n      span.error,\n      small.error {\n        display: none;\n      }\n    }\n\n    span.error,\n    small.error {\n      @include form-error-message;\n    }\n\n    .error {\n\n      input,\n      textarea,\n      select {\n        margin-bottom: 0;\n      }\n\n      input[type=\"checkbox\"],\n      input[type=\"radio\"] {\n        margin-bottom: $form-spacing\n      }\n\n      label,\n      label.error {\n        @include form-label-error-color;\n      }\n\n      small.error {\n        @include form-error-message;\n      }\n\n      >label {\n        >small {\n          color: scale-color($form-label-font-color, $lightness: 15%);\n          background: transparent;\n          padding: 0;\n          text-transform: $form-label-small-transform;\n          font-style: normal;\n          font-size: 60%;\n          margin: 0;\n          display: inline;\n        }\n      }\n\n      span.error-message {\n        display: block;\n      }\n    }\n\n    input.error,\n    textarea.error,\n    select.error {\n      margin-bottom: 0;\n    }\n\n    label.error {\n      @include form-label-error-color;\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n@import \"grid\";\n@import \"buttons\";\n@import \"forms\";\n\n//\n// Top Bar Variables\n//\n$include-html-top-bar-classes: $include-html-classes !default;\n\n// Background color for the top bar\n$topbar-bg-color: $oil !default;\n$topbar-bg: $topbar-bg-color !default;\n\n// Height and margin\n$topbar-height: rem-calc(45) !default;\n$topbar-margin-bottom: 0 !default;\n\n// Controlling the styles for the title in the top bar\n$topbar-title-weight: $font-weight-normal !default;\n$topbar-title-font-size: rem-calc(17) !default;\n\n// Set the link colors and styles for top-level nav\n$topbar-link-color: $white !default;\n$topbar-link-color-hover: $white !default;\n$topbar-link-color-active: $white !default;\n$topbar-link-color-active-hover: $white !default;\n$topbar-link-weight: $font-weight-normal !default;\n$topbar-link-font-size: rem-calc(13) !default;\n$topbar-link-hover-lightness: -10% !default; // Darken by 10%\n$topbar-link-bg: $topbar-bg !default;\n$topbar-link-bg-hover: $oil !default;\n$topbar-link-bg-color-hover: $charcoal !default;\n$topbar-link-bg-active: $primary-color !default;\n$topbar-link-bg-active-hover: scale-color($primary-color, $lightness: -14%) !default;\n$topbar-link-font-family: $body-font-family !default;\n$topbar-link-text-transform: none !default;\n$topbar-link-padding: calc($topbar-height / 3) !default;\n$topbar-back-link-size: rem-calc(18) !default;\n$topbar-link-dropdown-padding: rem-calc(20) !default;\n$topbar-button-font-size: 0.75rem !default;\n$topbar-button-top: 7px !default;\n\n// Style the top bar dropdown elements\n$topbar-dropdown-bg: $oil !default;\n$topbar-dropdown-link-color: $white !default;\n$topbar-dropdown-link-color-hover: $topbar-link-color-hover !default;\n$topbar-dropdown-link-bg: $oil !default;\n$topbar-dropdown-link-bg-hover: $oil !default;\n$topbar-dropdown-link-weight: $font-weight-normal !default;\n$topbar-dropdown-toggle-size: 5px !default;\n$topbar-dropdown-toggle-color: $white !default;\n$topbar-dropdown-toggle-alpha: 0.4 !default;\n\n$topbar-dropdown-label-color: $monsoon !default;\n$topbar-dropdown-label-text-transform: uppercase !default;\n$topbar-dropdown-label-font-weight: $font-weight-bold !default;\n$topbar-dropdown-label-font-size: rem-calc(10) !default;\n$topbar-dropdown-label-bg: $oil !default;\n\n// Top menu icon styles\n$topbar-menu-link-transform: uppercase !default;\n$topbar-menu-link-font-size: rem-calc(13) !default;\n$topbar-menu-link-weight: $font-weight-bold !default;\n$topbar-menu-link-color: $white !default;\n$topbar-menu-icon-color: $white !default;\n$topbar-menu-link-color-toggled: $jumbo !default;\n$topbar-menu-icon-color-toggled: $jumbo !default;\n\n// Transitions and breakpoint styles\n$topbar-transition-speed: 300ms !default;\n// Using rem-calc for the below breakpoint causes issues with top bar\n$topbar-breakpoint: #{lower-bound($medium-range)} !default; // Change to 9999px for always mobile layout\n$topbar-media-query: $medium-up !default;\n\n// Top-bar input styles\n$topbar-input-height: rem-calc(28) !default;\n\n// Divider Styles\n$topbar-divider-border-bottom: solid 1px scale-color($topbar-bg-color, $lightness: 13%) !default;\n$topbar-divider-border-top: solid 1px scale-color($topbar-bg-color, $lightness: -50%) !default;\n\n// Sticky Class\n$topbar-sticky-class: \".sticky\" !default;\n$topbar-arrows: true !default; //Set false to remove the triangle icon from the menu item\n$topbar-dropdown-arrows: true !default; //Set false to remove the \\00bb >> text from dropdown subnavigation li\n\n// Accessibility mixins for hiding and showing the menu dropdown items\n@mixin topbar-hide-dropdown {\n  // Makes an element visually hidden by default, but visible when focused.\n  display: block;\n  @include element-invisible();\n}\n\n@mixin topbar-show-dropdown {\n  display: block;\n  @include element-invisible-off();\n  position: absolute !important; // Reset the position from static to absolute\n}\n\n@include exports(\"top-bar\") {\n\n  @if $include-html-top-bar-classes {\n\n    // Used to provide media query values for javascript components.\n    // This class is generated despite the value of $include-html-top-bar-classes\n    // to ensure width calculations work correctly.\n    meta.foundation-mq-topbar {\n      font-family: \"/\" + unquote($topbar-media-query) + \"/\";\n      width: $topbar-breakpoint;\n    }\n\n    /* Wrapped around .top-bar to contain to grid width */\n    .contain-to-grid {\n      width: 100%;\n      background: $topbar-bg;\n\n      .top-bar {\n        margin-bottom: $topbar-margin-bottom;\n      }\n    }\n\n    // Wrapped around .top-bar to make it stick to the top\n    .fixed {\n      width: 100%;\n      #{$default-float}: 0;\n      position: fixed;\n      top: 0;\n      z-index: 99;\n\n      &.expanded:not(.top-bar) {\n        overflow-y: auto;\n        height: auto;\n        width: 100%;\n        max-height: 100%;\n\n        .title-area {\n          position: fixed;\n          width: 100%;\n          z-index: 99;\n        }\n\n        // Ensure you can scroll the menu on small screens\n        .top-bar-section {\n          z-index: 98;\n          margin-top: $topbar-height;\n        }\n      }\n    }\n\n    .top-bar {\n      overflow: hidden;\n      height: $topbar-height;\n      line-height: $topbar-height;\n      position: relative;\n      background: $topbar-bg;\n      margin-bottom: $topbar-margin-bottom;\n\n      // Topbar Global list Styles\n      ul {\n        margin-bottom: 0;\n        list-style: none;\n      }\n\n      .row {\n        max-width: none;\n      }\n\n      form,\n      input {\n        margin-bottom: 0;\n      }\n\n      input {\n        height: $topbar-input-height;\n        padding-top: .35rem;\n        padding-bottom: .35rem;\n        font-size: $topbar-button-font-size;\n      }\n\n      .button,\n      button {\n        padding-top: .35rem + rem-calc(1);\n        padding-bottom: .35rem + rem-calc(1);\n        margin-bottom: 0;\n        font-size: $topbar-button-font-size;\n        // position: relative;\n        // top: -1px;\n\n        // Corrects a slight misalignment when put next to an input field\n        @media #{$small-only} {\n          position: relative;\n          top: -1px;\n        }\n      }\n\n      // Title Area\n      .title-area {\n        position: relative;\n        margin: 0;\n      }\n\n      .name {\n        height: $topbar-height;\n        margin: 0;\n        font-size: $rem-base;\n\n        h1,\n        h2,\n        h3,\n        h4,\n        p,\n        span {\n          line-height: $topbar-height;\n          font-size: $topbar-title-font-size;\n          margin: 0;\n\n          a {\n            font-weight: $topbar-title-weight;\n            color: $topbar-link-color;\n            width: 75%;\n            display: block;\n            padding: 0 $topbar-link-padding;\n          }\n        }\n      }\n\n      // Menu toggle button on small devices\n      .toggle-topbar {\n        position: absolute;\n        #{$opposite-direction}: 0;\n        top: 0;\n\n        a {\n          color: $topbar-link-color;\n          text-transform: $topbar-menu-link-transform;\n          font-size: $topbar-menu-link-font-size;\n          font-weight: $topbar-menu-link-weight;\n          position: relative;\n          display: block;\n          padding: 0 $topbar-link-padding;\n          height: $topbar-height;\n          line-height: $topbar-height;\n        }\n\n        // Adding the class \"menu-icon\" will add the 3-line icon people love and adore.\n        &.menu-icon {\n          top: 50%;\n          margin-top: -16px;\n\n          a {\n            @if $text-direction ==rtl {\n              text-indent: -58px;\n            }\n\n            height: 34px;\n            line-height: 33px;\n            padding: 0 $topbar-link-padding+rem-calc(25) 0 $topbar-link-padding;\n            color: $topbar-menu-link-color;\n            position: relative;\n\n            & {\n              // @include hamburger icon\n              //\n              // We use this to create the icon with three lines aka the hamburger icon, the menu-icon or the navicon\n              // $width - Width of hamburger icon\n              // $left - If false, icon will be centered horizontally || explicitly set value in rem\n              // $top - If false, icon will be centered vertically || explicitly set value in rem\n              // $thickness - thickness of lines in hamburger icon, set value in px\n              // $gap - spacing between the lines in hamburger icon, set value in px\n              // $color - icon color\n              // $hover-color - icon color during hover, here it isn't set b/c it would override $topbar-menu-icon-color-toggled\n              // $offcanvas - Set to false of @include in topbar\n              @include hamburger(16px, false, 0, 1px, 6px, $topbar-menu-icon-color, \"\", false);\n            }\n          }\n        }\n      }\n\n      // Change things up when the top-bar is expanded\n      &.expanded {\n        height: auto;\n        background: transparent;\n\n        .title-area {\n          background: $topbar-bg;\n        }\n\n        .toggle-topbar {\n          a {\n            color: $topbar-menu-link-color-toggled;\n\n            span::after {\n              // Shh, don't tell, but box-shadows create the menu icon :)\n              // Change the color of the bars when the menu is expanded, using given thickness from hamburger() above\n              box-shadow: 0 0 0 1px $topbar-menu-icon-color-toggled,\n                0 7px 0 1px $topbar-menu-icon-color-toggled,\n                0 14px 0 1px $topbar-menu-icon-color-toggled;\n            }\n          }\n        }\n      }\n    }\n\n    // Right and Left Navigation that stacked by default\n    .top-bar-section {\n      #{$default-float}: 0;\n      position: relative;\n      width: auto;\n      @include single-transition($default-float, $topbar-transition-speed);\n\n      ul {\n        padding: 0;\n        width: 100%;\n        height: auto;\n        display: block;\n        font-size: $rem-base;\n        margin: 0;\n      }\n\n      .divider,\n      [role=\"separator\"] {\n        border-top: $topbar-divider-border-top;\n        clear: both;\n        height: 1px;\n        width: 100%;\n      }\n\n      ul li {\n        background: $topbar-dropdown-bg;\n\n        &>a {\n          display: block;\n          width: 100%;\n          color: $topbar-link-color;\n          padding: 12px 0 12px 0;\n          padding-#{$default-float}: $topbar-link-padding;\n          font-family: $topbar-link-font-family;\n          font-size: $topbar-link-font-size;\n          font-weight: $topbar-link-weight;\n          text-transform: $topbar-link-text-transform;\n\n          &.button {\n            font-size: $topbar-link-font-size;\n            padding-#{$opposite-direction}: $topbar-link-padding;\n            padding-#{$default-float}: $topbar-link-padding;\n            @include button-style($bg: $primary-color);\n          }\n\n          &.button.secondary {\n            @include button-style($bg: $secondary-color);\n          }\n\n          &.button.success {\n            @include button-style($bg: $success-color);\n          }\n\n          &.button.alert {\n            @include button-style($bg: $alert-color);\n          }\n\n          &.button.warning {\n            @include button-style($bg: $warning-color);\n          }\n        }\n\n        >button {\n          font-size: $topbar-link-font-size;\n          padding-#{$opposite-direction}: $topbar-link-padding;\n          padding-#{$default-float}: $topbar-link-padding;\n          @include button-style($bg: $primary-color);\n\n          &.secondary {\n            @include button-style($bg: $secondary-color);\n          }\n\n          &.success {\n            @include button-style($bg: $success-color);\n          }\n\n          &.alert {\n            @include button-style($bg: $alert-color);\n          }\n\n          &.warning {\n            @include button-style($bg: $warning-color);\n          }\n        }\n\n        // Apply the hover link color when it has that class\n        &:hover:not(.has-form)>a {\n          background-color: $topbar-link-bg-color-hover;\n\n          @if ($topbar-link-bg-hover) {\n            background: $topbar-link-bg-hover;\n          }\n\n          color: $topbar-link-color-hover;\n        }\n\n        // Apply the active link color when it has that class\n        &.active>a {\n          background: $topbar-link-bg-active;\n          color: $topbar-link-color-active;\n\n          &:hover {\n            background: $topbar-link-bg-active-hover;\n            color: $topbar-link-color-active-hover;\n          }\n        }\n      }\n\n      // Add some extra padding for list items contains buttons\n      .has-form {\n        padding: $topbar-link-padding;\n      }\n\n      // Styling for list items that have a dropdown within them.\n      .has-dropdown {\n        position: relative;\n\n        &>a {\n          &:after {\n            @if ($topbar-arrows) {\n              @include css-triangle($topbar-dropdown-toggle-size, rgba($topbar-dropdown-toggle-color, $topbar-dropdown-toggle-alpha), $default-float);\n            }\n\n            margin-#{$opposite-direction}: $topbar-link-padding;\n            margin-top: -(calc($topbar-dropdown-toggle-size / 2)) - 2;\n            position: absolute;\n            top: 50%;\n            #{$opposite-direction}: 0;\n          }\n        }\n\n        &.moved {\n          position: static;\n\n          &>.dropdown {\n            @include topbar-show-dropdown();\n            width: 100%;\n          }\n\n          &>a:after {\n            display: none;\n          }\n        }\n      }\n\n      // Styling elements inside of dropdowns\n      .dropdown {\n        padding: 0;\n        position: absolute;\n        #{$default-float}: 100%;\n        top: 0;\n        z-index: 99;\n        @include topbar-hide-dropdown();\n\n        li {\n          width: 100%;\n          height: auto;\n\n          a {\n            font-weight: $topbar-dropdown-link-weight;\n            padding: 8px $topbar-link-padding;\n\n            &.parent-link {\n              font-weight: $topbar-link-weight;\n            }\n          }\n\n          &.title h5,\n          &.parent-link {\n            // Back Button\n            margin-bottom: 0;\n            margin-top: 0;\n            font-size: $topbar-back-link-size;\n\n            a {\n              color: $topbar-link-color;\n              // line-height: ($topbar-height / 2);\n              display: block;\n\n              &:hover {\n                background: none;\n              }\n            }\n          }\n\n          &.has-form {\n            padding: 8px $topbar-link-padding;\n          }\n\n          .button,\n          button {\n            top: auto;\n          }\n        }\n\n        label {\n          padding: 8px $topbar-link-padding 2px;\n          margin-bottom: 0;\n          text-transform: $topbar-dropdown-label-text-transform;\n          color: $topbar-dropdown-label-color;\n          font-weight: $topbar-dropdown-label-font-weight;\n          font-size: $topbar-dropdown-label-font-size;\n        }\n      }\n    }\n\n    .js-generated {\n      display: block;\n    }\n\n\n    // Top Bar styles intended for screen sizes above the breakpoint.\n    @media #{$topbar-media-query} {\n      .top-bar {\n        background: $topbar-bg;\n        @include clearfix;\n        overflow: visible;\n\n        .toggle-topbar {\n          display: none;\n        }\n\n        .title-area {\n          float: $default-float;\n        }\n\n        .name h1 a {\n          width: auto;\n        }\n\n        input,\n        .button,\n        button {\n          font-size: rem-calc(14);\n          position: relative;\n          height: $topbar-input-height;\n          top: calc(($topbar-height - $topbar-input-height) / 2);\n        }\n\n        &.expanded {\n          background: $topbar-bg;\n        }\n      }\n\n      .contain-to-grid .top-bar {\n        max-width: $row-width;\n        margin: 0 auto;\n        margin-bottom: $topbar-margin-bottom;\n      }\n\n      .top-bar-section {\n        @include single-transition(none, 0, 0);\n        #{$default-float}: 0 !important;\n\n        ul {\n          width: auto;\n          height: auto !important;\n          display: inline;\n\n          li {\n            float: $default-float;\n\n            .js-generated {\n              display: none;\n            }\n          }\n        }\n\n        li {\n          &.hover {\n            >a:not(.button) {\n              background-color: $topbar-link-bg-color-hover;\n\n              @if ($topbar-link-bg-hover) {\n                background: $topbar-link-bg-hover;\n              }\n\n              color: $topbar-link-color-hover;\n            }\n          }\n\n          &:not(.has-form) {\n            a:not(.button) {\n              padding: 0 $topbar-link-padding;\n              line-height: $topbar-height;\n              background: $topbar-link-bg;\n\n              &:hover {\n                background-color: $topbar-link-bg-color-hover;\n\n                @if ($topbar-link-bg-hover) {\n                  background: $topbar-link-bg-hover;\n                }\n              }\n            }\n          }\n\n          &.active:not(.has-form) {\n            a:not(.button) {\n              padding: 0 $topbar-link-padding;\n              line-height: $topbar-height;\n              color: $topbar-link-color-active;\n              background: $topbar-link-bg-active;\n\n              &:hover {\n                background: $topbar-link-bg-active-hover;\n                color: $topbar-link-color-active-hover;\n              }\n            }\n          }\n        }\n\n        .has-dropdown {\n          @if($topbar-arrows) {\n            &>a {\n              padding-#{$opposite-direction}: $topbar-link-padding + $topbar-link-dropdown-padding !important;\n\n              &:after {\n                @include css-triangle($topbar-dropdown-toggle-size, rgba($topbar-dropdown-toggle-color, $topbar-dropdown-toggle-alpha), top);\n                margin-top: -(calc($topbar-dropdown-toggle-size / 2));\n                top: calc($topbar-height / 2);\n              }\n            }\n          }\n\n          &.moved {\n            position: relative;\n\n            &>.dropdown {\n              @include topbar-hide-dropdown();\n            }\n          }\n\n          &.hover,\n          &.not-click:hover {\n            &>.dropdown {\n              @include topbar-show-dropdown();\n            }\n          }\n\n          >a:focus+.dropdown {\n            @include topbar-show-dropdown();\n          }\n\n          .dropdown li.has-dropdown {\n            &>a {\n              @if ($topbar-dropdown-arrows) {\n                &:after {\n                  border: none;\n                  content: \"\\00bb\";\n                  top: 1rem;\n                  margin-top: -1px;\n                  #{$opposite-direction}: 5px;\n                  line-height: 1.2;\n                }\n              }\n            }\n          }\n        }\n\n        .dropdown {\n          #{$default-float}: 0;\n          top: auto;\n          background: transparent;\n          min-width: 100%;\n\n          li {\n            a {\n              color: $topbar-dropdown-link-color;\n              line-height: $topbar-height;\n              white-space: nowrap;\n              padding: 12px $topbar-link-padding;\n              background: $topbar-dropdown-link-bg;\n            }\n\n            &:not(.has-form):not(.active) {\n              &>a:not(.button) {\n                color: $topbar-dropdown-link-color;\n                background: $topbar-dropdown-link-bg;\n              }\n\n              &:hover>a:not(.button) {\n                color: $topbar-dropdown-link-color-hover;\n                background-color: $topbar-link-bg-color-hover;\n\n                @if ($topbar-dropdown-link-bg-hover) {\n                  background: $topbar-dropdown-link-bg-hover;\n                }\n              }\n            }\n\n            label {\n              white-space: nowrap;\n              background: $topbar-dropdown-label-bg;\n            }\n\n            // Second Level Dropdowns\n            .dropdown {\n              #{$default-float}: 100%;\n              top: 0;\n            }\n          }\n        }\n\n        &>ul>.divider,\n        &>ul>[role=\"separator\"] {\n          border-bottom: none;\n          border-top: none;\n          border-#{$opposite-direction}: $topbar-divider-border-bottom;\n          clear: none;\n          height: $topbar-height;\n          width: 0;\n        }\n\n        .has-form {\n          background: $topbar-link-bg;\n          padding: 0 calc($topbar-height / 3);\n          height: $topbar-height;\n        }\n\n        // Position overrides for ul.right and ul.left\n        .#{$opposite-direction} {\n          li .dropdown {\n            #{$default-float}: auto;\n            #{$opposite-direction}: 0;\n\n            li .dropdown {\n              #{$opposite-direction}: 100%;\n            }\n          }\n        }\n\n        .#{$default-float} {\n          li .dropdown {\n            #{$opposite-direction}: auto;\n            #{$default-float}: 0;\n\n            li .dropdown {\n              #{$default-float}: 100%;\n            }\n          }\n        }\n      }\n\n      // Degrade gracefully when Javascript is disabled. Displays dropdown and changes\n      // background & text color on hover.\n      .no-js .top-bar-section {\n        ul li {\n\n          // Apply the hover link color when it has that class\n          &:hover>a {\n            background-color: $topbar-link-bg-color-hover;\n\n            @if ($topbar-link-bg-hover) {\n              background: $topbar-link-bg-hover;\n            }\n\n            color: $topbar-link-color-hover;\n          }\n\n          // Apply the active link color when it has that class\n          &:active>a {\n            background: $topbar-link-bg-active;\n            color: $topbar-link-color-active;\n          }\n        }\n\n        .has-dropdown {\n          &:hover {\n            &>.dropdown {\n              @include topbar-show-dropdown();\n            }\n          }\n\n          >a:focus+.dropdown {\n            @include topbar-show-dropdown();\n          }\n        }\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n\n$include-html-accordion-classes: $include-html-classes !default;\n\n$accordion-navigation-padding: rem-calc(16) !default;\n$accordion-navigation-bg-color: $silver !default;\n$accordion-navigation-hover-bg-color: scale-color($accordion-navigation-bg-color, $lightness: -5%) !default;\n$accordion-navigation-active-bg-color: scale-color($accordion-navigation-bg-color, $lightness: -3%) !default;\n$accordion-navigation-font-color: $jet !default;\n$accordion-navigation-font-size: rem-calc(16) !default;\n$accordion-navigation-font-family: $body-font-family !default;\n\n$accordion-content-padding: calc($column-gutter / 2) !default;\n$accordion-content-active-bg-color: $white !default;\n\n\n//  Mixin: accordion-container()\n//  Description: Responsible for the container component of accordions, generating styles relating to a margin of zero and a clearfix\n//  Explicit Dependencies: a clearfix mixin *is* defined.\n//  Implicit Dependencies: None\n\n@mixin accordion-container() {\n  @include clearfix;\n  margin-bottom: 0;\n}\n\n//  Mixin: accordion-navigation( $bg, $hover-bg, $active-bg, $padding, $active_class,  $font-color, $font-size, $font-family){\n//    @params $bg-color: [ color or string ]: Specify the background color for the navigation element\n//    @params $hover-bg-color [ color or string ]: Specify the background color for the navigation element when hovered\n//    @params $active-bg [ color or string ]: Specify the background color for the navigation element when clicked and not released.\n//    @params $active_class [ string ]: Specify the class name used to keep track of which accordion tab should be visible\n//    @params $font-color [ color or string ]: Color of the font for accordion\n//    @params $font-size [ number ]: Specify the font-size of the text inside the navigation element\n//    @params $font-family [ string ]: Specify the font family for the text of the navigation of the accordion\n\n@mixin accordion-navigation($bg: $accordion-navigation-bg-color, $hover-bg: $accordion-navigation-hover-bg-color, $active-bg: $accordion-navigation-active-bg-color, $padding: $accordion-navigation-padding, $active_class: 'active', $font-color: $accordion-navigation-font-color, $font-size: $accordion-navigation-font-size, $font-family: $accordion-navigation-font-family ) {\n  display: block;\n  margin-bottom: 0 !important;\n\n  @if type-of($active_class) !=\"string\" {\n    @warn \"`#{$active_class}` isn't a valid string. A valid string is needed to correctly be interpolated as a CSS class. CSS classes cannot start with a number or consist of only numbers. CSS will not be generated for the active state of this navigation component.\"\n  }\n\n  @else {\n    &.#{ $active_class }>a {\n      background: $active-bg;\n    }\n  }\n\n  >a {\n    background: $bg;\n    color: $font-color;\n\n    @if type-of($padding) !=number {\n      @warn \"`#{$padding}` was read as #{type-of($padding)}\";\n\n      @if $accordion-navigation-padding !=null {\n        @warn \"#{$padding} was read as a #{type-of($padding)}\";\n        @warn \"`#{$padding}` isn't a valid number. $accordion-navigation-padding (#{$accordion-navigation-padding}) will be used instead.)\";\n        padding: $accordion-navigation-padding;\n      }\n\n      @else {\n        @warn \"`#{$padding}` isn't a valid number and $accordion-navigation-padding is missing. A value of `null` is returned to not output an invalid value for padding\";\n        padding: null;\n      }\n    }\n\n    @else {\n      padding: $padding;\n    }\n\n    display: block;\n    font-family: $font-family;\n\n    @if type-of($font-size) !=number {\n      @warn \"`#{$font-size}` was read as a #{type-of($font-size)}\";\n\n      @if $accordion-navigation-font-size !=null {\n        @warn \"`#{$font-size}` is not a valid number. The value of $accordion-navigation-font-size will be used instead (#{$accordion-navigation-font-size}).\";\n        font-size: $accordion-navigation-font-size;\n      }\n\n      @else {\n        @warn \"`#{$font-size}` is not a valid number and the default value of $accordion-navigation-font-size is not defined. A value of `null` will be returned to not generate an invalid value for font-size.\";\n        font-size: null;\n\n      }\n    }\n\n    @else {\n      font-size: $font-size;\n    }\n\n    &:hover {\n      background: $hover-bg;\n    }\n  }\n}\n\n//  Mixin: accordion-content($bg, $padding, $active-class)\n//    @params $padding [ number ]: Padding for the content of the container\n//    @params $bg [ color  ]: Background color for the content when it's visible\n//    @params $active_class [ string ]: Class name used to keep track of which accordion tab should be visible.\n\n@mixin accordion-content($bg: $accordion-content-active-bg-color, $padding: $accordion-content-padding, $active_class: 'active') {\n  display: none;\n\n  @if type-of($padding) !=\"number\" {\n    @warn \"#{$padding} was read as a #{type-of($padding)}\";\n\n    @if $accordion-content-padding !=null {\n      @warn \"`#{$padding}` isn't a valid number. $accordion-content-padding used instead\";\n      padding: $accordion-content-padding;\n    }\n\n    @else {\n      @warn \"`#{$padding}` isn't a valid number and the default value of $accordion-content-padding is not defined. A value of `null` is returned to not output an invalid value for padding.\";\n      padding: null;\n    }\n  }\n\n  @else {\n    padding: $padding;\n  }\n\n  @if type-of($active_class) !=\"string\" {\n    @warn \"`#{$active_class}` isn't a valid string. A valid string is needed to correctly be interpolated as a CSS class. CSS classes cannot start with a number or consist of only numbers. CSS will not be generated for the active state of the content. \"\n  }\n\n  @else {\n    &.#{$active_class} {\n      display: block;\n      background: $bg;\n    }\n  }\n}\n\n@include exports(\"accordion\") {\n  @if $include-html-accordion-classes {\n    .accordion {\n      @include clearfix;\n      margin-bottom: 0;\n\n      .accordion-navigation,\n      dd {\n        display: block;\n        margin-bottom: 0 !important;\n\n        &.active>a {\n          background: $accordion-navigation-active-bg-color;\n        }\n\n        >a {\n          background: $accordion-navigation-bg-color;\n          color: $accordion-navigation-font-color;\n          padding: $accordion-navigation-padding;\n          display: block;\n          font-family: $accordion-navigation-font-family;\n          font-size: $accordion-navigation-font-size;\n\n          &:hover {\n            background: $accordion-navigation-hover-bg-color;\n          }\n        }\n\n        >.content {\n          display: none;\n          padding: $accordion-content-padding;\n\n          &.active {\n            display: block;\n            background: $accordion-content-active-bg-color;\n          }\n        }\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// Alert Box Variables\n//\n$include-html-alert-classes: $include-html-classes !default;\n\n// We use this to control alert padding.\n$alert-padding-top: rem-calc(14) !default;\n$alert-padding-default-float: $alert-padding-top !default;\n$alert-padding-opposite-direction: $alert-padding-top + rem-calc(10) !default;\n$alert-padding-bottom: $alert-padding-top !default;\n\n// We use these to control text style.\n$alert-font-weight: $font-weight-normal !default;\n$alert-font-size: rem-calc(13) !default;\n$alert-font-color: $white !default;\n$alert-font-color-alt: scale-color($secondary-color, $lightness: -66%) !default;\n\n// We use this for close hover effect.\n$alert-function-factor: -14% !default;\n\n// We use these to control border styles.\n$alert-border-style: solid !default;\n$alert-border-width: 1px !default;\n$alert-border-color: scale-color($primary-color, $lightness: $alert-function-factor) !default;\n$alert-bottom-margin: rem-calc(20) !default;\n\n// We use these to style the close buttons\n$alert-close-color: $oil !default;\n$alert-close-top: 50% !default;\n$alert-close-position: rem-calc(4) !default;\n$alert-close-font-size: rem-calc(22) !default;\n$alert-close-opacity: 0.3 !default;\n$alert-close-opacity-hover: 0.5 !default;\n$alert-close-padding: 9px 6px 4px !default;\n$alert-close-background: inherit !default;\n\n// We use this to control border radius\n$alert-radius: $global-radius !default;\n\n$alert-transition-speed: 300ms !default;\n$alert-transition-ease: ease-out !default;\n\n//\n// Alert Mixins\n//\n\n// We use this mixin to create a default alert base.\n@mixin alert-base {\n  border-style: $alert-border-style;\n  border-width: $alert-border-width;\n  display: block;\n  font-weight: $alert-font-weight;\n  margin-bottom: $alert-bottom-margin;\n  position: relative;\n  padding: $alert-padding-top $alert-padding-opposite-direction $alert-padding-bottom $alert-padding-default-float;\n  font-size: $alert-font-size;\n  @include single-transition(opacity, $alert-transition-speed, $alert-transition-ease)\n}\n\n// We use this mixin to add alert styles\n//\n// $bg - The background of the alert. Default: $primary-color.\n@mixin alert-style($bg: $primary-color) {\n\n  // This finds the lightness percentage of the background color.\n  $bg-lightness: lightness($bg);\n\n  // We control which background color and border come through.\n  background-color: $bg;\n  border-color: scale-color($bg, $lightness: $alert-function-factor);\n\n  // We control the text color for you based on the background color.\n  @if $bg-lightness >70% {\n    color: $alert-font-color-alt;\n  }\n\n  @else {\n    color: $alert-font-color;\n  }\n\n}\n\n// We use this to create the close button.\n@mixin alert-close {\n  font-size: $alert-close-font-size;\n  padding: $alert-close-padding;\n  line-height: 0;\n  position: absolute;\n  top: $alert-close-top;\n  margin-top: -(calc($alert-close-font-size / 2));\n  #{$opposite-direction}: $alert-close-position;\n  color: $alert-close-color;\n  opacity: $alert-close-opacity;\n  background: $alert-close-background;\n\n  &:hover,\n  &:focus {\n    opacity: $alert-close-opacity-hover;\n  }\n}\n\n// We use this to quickly create alerts with a single mixin.\n//\n// $bg - Background of alert. Default: $primary-color.\n// $radius - Radius of alert box. Default: false.\n@mixin alert($bg: $primary-color, $radius: false) {\n  @include alert-base;\n  @include alert-style($bg);\n  @include radius($radius);\n}\n\n@include exports(\"alert-box\") {\n  @if $include-html-alert-classes {\n    .alert-box {\n      @include alert;\n\n      .close {\n        @include alert-close;\n      }\n\n      &.radius {\n        @include radius($alert-radius);\n      }\n\n      &.round {\n        @include radius($global-rounded);\n      }\n\n      &.success {\n        @include alert-style($success-color);\n      }\n\n      &.alert {\n        @include alert-style($alert-color);\n      }\n\n      &.secondary {\n        @include alert-style($secondary-color);\n      }\n\n      &.warning {\n        @include alert-style($warning-color);\n      }\n\n      &.info {\n        @include alert-style($info-color);\n      }\n\n      &.alert-close {\n        opacity: 0\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// Breadcrumb Variables\n//\n$include-html-nav-classes: $include-html-classes !default;\n\n// We use this to set the background color for the breadcrumb container.\n$crumb-bg: scale-color($secondary-color, $lightness: 55%) !default;\n\n// We use these to set the padding around the breadcrumbs.\n$crumb-padding: rem-calc(9 14 9) !default;\n$crumb-side-padding: rem-calc(12) !default;\n\n// We use these to control border styles.\n$crumb-function-factor: -10% !default;\n$crumb-border-size: 1px !default;\n$crumb-border-style: solid !default;\n$crumb-border-color: scale-color($crumb-bg, $lightness: $crumb-function-factor) !default;\n$crumb-radius: $global-radius !default;\n\n// We use these to set various text styles for breadcrumbs.\n$crumb-font-size: rem-calc(11) !default;\n$crumb-font-color: $primary-color !default;\n$crumb-font-color-current: $oil !default;\n$crumb-font-color-unavailable: $aluminum !default;\n$crumb-font-transform: uppercase !default;\n$crumb-link-decor: underline !default;\n\n// We use these to control the slash between breadcrumbs\n$crumb-slash-color: $base !default;\n$crumb-slash: \"/\" !default;\n\n//\n// Breadcrumb Mixins\n//\n\n// We use this mixin to create a container around our breadcrumbs\n@mixin crumb-container {\n  display: block;\n  padding: $crumb-padding;\n  overflow: hidden;\n  margin-#{$default-float}: 0;\n  list-style: none;\n  border-style: $crumb-border-style;\n  border-width: $crumb-border-size;\n\n  // We control which background color and border come through.\n  background-color: $crumb-bg;\n  border-color: $crumb-border-color;\n}\n\n// We use this mixin to create breadcrumb styles from list items.\n@mixin crumbs {\n\n  // A normal state will make the links look and act like clickable breadcrumbs.\n  margin: 0;\n  float: $default-float;\n  font-size: $crumb-font-size;\n  line-height: $crumb-font-size;\n  text-transform: $crumb-font-transform;\n  color: $crumb-font-color;\n\n  &:hover a, &:focus a { text-decoration: $crumb-link-decor; }\n\n  a {\n    color: $crumb-font-color;\n  }\n\n  // Current is for the link of the current page\n  &.current {\n    cursor: $cursor-default-value;\n    color: $crumb-font-color-current;\n    a {\n      cursor: $cursor-default-value;\n      color: $crumb-font-color-current;\n    }\n\n    &:hover, &:hover a,\n    &:focus, &:focus a { text-decoration: none; }\n  }\n\n  // Unavailable removed color and link styles so it looks inactive.\n  &.unavailable {\n    color: $crumb-font-color-unavailable;\n    a { color: $crumb-font-color-unavailable; }\n\n    &:hover,\n    &:hover a,\n    &:focus,\n    a:focus {\n      text-decoration: none;\n      color: $crumb-font-color-unavailable;\n      cursor: $cursor-default-value;\n    }\n  }\n\n  &:before {\n    content: \"#{$crumb-slash}\";\n    color: $crumb-slash-color;\n    margin: 0 $crumb-side-padding;\n    position: relative;\n    top: 1px;\n  }\n\n  &:first-child:before {\n    content: \" \";\n    margin: 0;\n  }\n}\n\n@include exports(\"breadcrumbs\") {\n  @if $include-html-nav-classes {\n    .breadcrumbs {\n      @include crumb-container;\n      @include radius($crumb-radius);\n\n      &>* {\n        @include crumbs;\n      }\n    }\n  }\n}\n\n/* Accessibility - hides the forward slash */\n[aria-label=\"breadcrumbs\"] [aria-hidden=\"true\"]:after {\n  content: \"/\";\n  }\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// Block Grid Variables\n//\n$include-html-block-grid-classes: $include-html-classes !default;\n$include-xl-html-block-grid-classes: false !default;\n\n// We use this to control the maximum number of block grid elements per row\n$block-grid-elements: 12 !default;\n$block-grid-default-spacing: rem-calc(20) !default;\n\n$align-block-grid-to-grid: false !default;\n\n@if $align-block-grid-to-grid {\n  $block-grid-default-spacing: $column-gutter;\n}\n\n// Enables media queries for block-grid classes. Set to false if writing semantic HTML.\n$block-grid-media-queries: true !default;\n\n//\n// Block Grid Mixins\n//\n\n// Create a custom block grid\n//\n// $per-row - # of items to display per row. Default: false.\n// $spacing - # of ems to use as padding on each block item. Default: rem-calc(20).\n// $base-style - Apply a base style to block grid. Default: true.\n@mixin block-grid($per-row: false,\n  $spacing: $block-grid-default-spacing,\n  $include-spacing: true,\n  $base-style: true) {\n\n  @if $base-style {\n    display: block;\n    padding: 0;\n\n    @if $align-block-grid-to-grid {\n      margin: 0;\n    }\n\n    @else {\n      margin: 0 calc(-1 * $spacing / 2);\n    }\n\n    @include clearfix;\n\n    &>li {\n      display: block;\n      height: auto;\n      float: $default-float;\n\n      @if $include-spacing {\n        padding: 0 calc($spacing / 2) $spacing;\n      }\n    }\n  }\n\n  @if $per-row {\n    &>li {\n      width: calc(100% / $per-row);\n\n      @if $include-spacing {\n        padding: 0 ($spacing/2) $spacing;\n      }\n\n      list-style: none;\n\n      &:nth-of-type(1n) {\n        clear: none;\n      }\n\n      &:nth-of-type(#{$per-row}n+1) {\n        clear: both;\n      }\n\n      @if $align-block-grid-to-grid {\n        @include block-grid-aligned($per-row, $spacing);\n      }\n    }\n  }\n}\n\n@mixin block-grid-aligned($per-row, $spacing) {\n  @for $i from 1 through $block-grid-elements {\n    @if $per-row >=$i {\n      $grid-column: '+'+$i;\n\n      @if $per-row ==$i {\n        $grid-column: '';\n      }\n\n      &:nth-of-type(#{$per-row}n#{unquote($grid-column)}) {\n        padding-left: ($spacing - (($spacing / $per-row) * ($per-row - ($i - 1))));\n        padding-right: ($spacing - (($spacing / $per-row) * $i));\n      }\n    }\n  }\n}\n\n// Generate presentational markup for block grid.\n//\n// $size - Name of class to use, i.e. \"large\" will generate .large-block-grid-1, .large-block-grid-2, etc.\n@mixin block-grid-html-classes($size, $include-spacing) {\n  @for $i from 1 through $block-grid-elements {\n    .#{$size}-block-grid-#{($i)} {\n      @include block-grid($i, $block-grid-default-spacing, $include-spacing, false);\n    }\n  }\n}\n\n@include exports(\"block-grid\") {\n  @if $include-html-block-grid-classes {\n\n    [class*=\"block-grid-\"] {\n      @include block-grid;\n    }\n\n    @if $block-grid-media-queries {\n      @media #{$small-up} {\n        @include block-grid-html-classes($size: small, $include-spacing: false);\n      }\n\n      @media #{$medium-up} {\n        @include block-grid-html-classes($size: medium, $include-spacing: false);\n      }\n\n      @media #{$large-up} {\n        @include block-grid-html-classes($size: large, $include-spacing: false);\n      }\n\n      @if $include-xl-html-block-grid-classes {\n        @media #{$xlarge-up} {\n          @include block-grid-html-classes($size: xlarge, $include-spacing: false);\n        }\n\n        @media #{$xxlarge-up} {\n          @include block-grid-html-classes($size: xxlarge, $include-spacing: false);\n        }\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n@import \"buttons\";\n\n//\n// Button Group Variables\n//\n$include-html-button-classes: $include-html-classes !default;\n\n// Sets the margin for the right side by default, and the left margin if right-to-left direction is used\n$button-bar-margin-opposite: rem-calc(10) !default;\n$button-group-border-width: 1px !default;\n\n//\n// Button Group Mixins\n//\n\n// We use this to add styles for a button group container\n@mixin button-group-container($styles: true, $float: false) {\n  @if $styles {\n    list-style: none;\n    margin: 0;\n    #{$default-float}: 0;\n    @include clearfix();\n  }\n\n  @if $float {\n    float: #{$default-float};\n    margin-#{$opposite-direction}: $button-bar-margin-opposite;\n\n    & div {\n      overflow: hidden;\n    }\n  }\n}\n\n// We use this to control styles for button groups\n@mixin button-group-style($radius: false, $even: false, $float: false, $orientation: horizontal) {\n\n  >button,\n  .button {\n    border-#{$default-float}: $button-group-border-width solid;\n    border-color: rgba(255, 255, 255, 0.5);\n  }\n\n  &:first-child {\n\n    button,\n    .button {\n      border-#{$default-float}: 0;\n    }\n  }\n\n  // We use this to control the flow, or remove those styles completely.\n  @if $float {\n    margin: 0;\n    float: $float;\n    display: list-item;\n\n    // Make sure the first child doesn't get the negative margin.\n    &:first-child {\n      margin-#{$default-float}: 0;\n    }\n  }\n\n  @else {\n    margin: 0 -2px;\n    display: inline-block;\n  }\n\n  @if $orientation ==vertical {\n    display: block;\n    margin: 0;\n\n    >button,\n    .button {\n      border-top: $button-group-border-width solid;\n      border-color: rgba(255, 255, 255, 0.5);\n      border-left-width: 0;\n      margin: 0;\n      display: block;\n    }\n\n    &:first-child {\n\n      button,\n      .button {\n        border-top: 0;\n      }\n    }\n  }\n\n  // We use these to control left and right radius on first/last buttons in the group.\n  @if $radius ==true {\n\n    &,\n    &>a,\n    &>button,\n    &>.button {\n      @include radius(0);\n    }\n\n    &:first-child,\n    &:first-child>a,\n    &:first-child>button,\n    &:first-child>.button {\n      @if $orientation ==vertical {\n        @include side-radius(top, $button-radius);\n      }\n\n      @else {\n        @include side-radius($default-float, $button-radius);\n      }\n    }\n\n    &:last-child,\n    &:last-child>a,\n    &:last-child>button,\n    &:last-child>.button {\n      @if $orientation ==vertical {\n        @include side-radius(bottom, $button-radius);\n      }\n\n      @else {\n        @include side-radius($opposite-direction, $button-radius);\n      }\n    }\n  }\n\n  @else if $radius {\n\n    &,\n    &>a,\n    &>button,\n    &>.button {\n      @include radius(0);\n    }\n\n    &:first-child,\n    &:first-child>a,\n    &:first-child>button,\n    &:first-child>.button {\n      @if $orientation ==vertical {\n        @include side-radius(top, $radius);\n      }\n\n      @else {\n        @include side-radius($default-float, $radius);\n      }\n    }\n\n    &:last-child,\n    &:last-child>a,\n    &:last-child>button,\n    &:last-child>.button {\n      @if $orientation ==vertical {\n        @include side-radius(bottom, $radius);\n      }\n\n      @else {\n        @include side-radius($opposite-direction, $radius);\n      }\n    }\n  }\n\n  // We use this to make the buttons even width across their container\n  @if $even {\n    width: percentage(calc((100/$even) / 100));\n\n    button,\n    .button {\n      width: 100%;\n    }\n  }\n}\n\n@include exports(\"button-group\") {\n  @if $include-html-button-classes {\n    .button-group {\n      @include button-group-container;\n\n      &>li {\n        @include button-group-style();\n      }\n\n      &.stack {\n        &>li {\n          @include button-group-style($orientation: vertical);\n          float: none;\n        }\n      }\n\n      &.stack-for-small {\n        &>li {\n          @include button-group-style($orientation: horizontal);\n\n          @media #{$small-only} {\n            @include button-group-style($orientation: vertical);\n          }\n        }\n      }\n\n      &.radius>* {\n        @include button-group-style($radius: $button-radius, $float: null);\n      }\n\n      &.radius.stack>* {\n        @include button-group-style($radius: $button-radius, $float: null, $orientation: vertical);\n      }\n\n      &.radius.stack-for-small>* {\n        @media #{$medium-up} {\n          @include button-group-style($radius: $button-radius, $orientation: horizontal);\n        }\n\n        @media #{$small-only} {\n          @include button-group-style($radius: $button-radius, $orientation: vertical);\n        }\n      }\n\n      &.round>* {\n        @include button-group-style($radius: $button-round, $float: null);\n      }\n\n      &.round.stack>* {\n        @include button-group-style($radius: $button-med, $float: null, $orientation: vertical);\n      }\n\n      &.round.stack-for-small>* {\n        @media #{$medium-up} {\n          @include button-group-style($radius: $button-round, $orientation: horizontal);\n        }\n\n        @media #{$small-only} {\n          @include button-group-style($radius: $button-med, $orientation: vertical);\n        }\n      }\n\n      @for $i from 2 through 8 {\n        &.even-#{$i} li {\n          @include button-group-style($even: $i, $float: null);\n        }\n      }\n    }\n\n    .button-bar {\n      @include clearfix;\n\n      .button-group {\n        @include button-group-container($styles: false, $float: true);\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-clearing-classes: $include-html-classes !default;\n\n// We use these to set the background colors for parts of Clearing.\n$clearing-bg: $oil !default;\n$clearing-caption-bg: $clearing-bg !default;\n$clearing-carousel-bg: rgba(51,51,51,0.8) !default;\n$clearing-img-bg: $clearing-bg !default;\n\n// We use these to style the close button\n$clearing-close-color: $iron !default;\n$clearing-close-size: 30px !default;\n\n// We use these to style the arrows\n$clearing-arrow-size: 12px !default;\n$clearing-arrow-color: $clearing-close-color !default;\n\n// We use these to style captions\n$clearing-caption-font-color: $iron !default;\n$clearing-caption-font-size: 0.875em !default;\n$clearing-caption-padding: 10px 30px 20px !default;\n\n// We use these to make the image and carousel height and style\n$clearing-active-img-height: 85% !default;\n$clearing-carousel-height: 120px !default;\n$clearing-carousel-thumb-width: 120px !default;\n$clearing-carousel-thumb-active-border: 1px solid rgb(255,255,255) !default;\n\n@include exports(\"clearing\") {\n  @if $include-html-clearing-classes {\n    // We decided to not create a mixin for Clearing because it relies\n    // on predefined classes and structure to work properly.\n    // The variables above should give enough control.\n\n    /* Clearing Styles */\n    .clearing-thumbs, #{data('clearing')} {\n      @include clearfix;\n      margin-bottom: 0;\n      margin-#{$default-float}: 0;\n      list-style: none;\n\n      li {\n        float: $default-float;\n        margin-#{$opposite-direction}: 10px;\n      }\n\n      &[class*=\"block-grid-\"] li {\n        margin-#{$opposite-direction}: 0;\n      }\n    }\n\n    .clearing-blackout {\n      background: $clearing-bg;\n      position: fixed;\n      width: 100%;\n      height: 100%;\n      top: 0;\n      #{$default-float}: 0;\n      z-index: 998;\n\n      .clearing-close { display: block; }\n    }\n\n    .clearing-container {\n      position: relative;\n      z-index: 998;\n      height: 100%;\n      overflow: hidden;\n      margin: 0;\n    }\n\n    .clearing-touch-label {\n      position: absolute;\n      top: 50%;\n      left: 50%;\n      color: $base;\n      font-size: 0.6em;\n    }\n\n    .visible-img {\n      height: 95%;\n      position: relative;\n\n      img {\n        position: absolute;\n        #{$default-float}: 50%;\n        top: 50%;\n        margin-#{$default-float}: -50%;\n        max-height: 100%;\n        max-width: 100%;\n      }\n    }\n\n    .clearing-caption {\n      color: $clearing-caption-font-color;\n      font-size: $clearing-caption-font-size;\n      line-height: 1.3;\n      margin-bottom: 0;\n      text-align: center;\n      bottom: 0;\n      background: $clearing-caption-bg;\n      width: 100%;\n      padding: $clearing-caption-padding;\n      position: absolute;\n      #{$default-float}: 0;\n    }\n\n    .clearing-close {\n      z-index: 999;\n      padding-#{$default-float}: 20px;\n      padding-top: 10px;\n      font-size: $clearing-close-size;\n      line-height: 1;\n      color: $clearing-close-color;\n      display: none;\n\n      &:hover,\n      &:focus { color: $iron; }\n    }\n\n    .clearing-assembled .clearing-container { height: 100%;\n      .carousel > ul { display: none; }\n    }\n\n    // If you want to show a lightbox, but only have a single image come through as the thumbnail\n    .clearing-feature li {\n      display: none;\n      &.clearing-featured-img {\n        display: block;\n      }\n    }\n\n    // Large screen overrides\n    @media #{$medium-up} {\n      .clearing-main-prev,\n      .clearing-main-next {\n        position: absolute;\n        height: 100%;\n        width: 40px;\n        top: 0;\n        & > span {\n          position: absolute;\n          top: 50%;\n          display: block;\n          width: 0;\n          height: 0;\n          border: solid $clearing-arrow-size;\n          &:hover { opacity: 0.8; }\n        }\n      }\n      .clearing-main-prev {\n        #{$default-float}: 0;\n        & > span {\n          #{$default-float}: 5px;\n          border-color: transparent;\n          border-#{$opposite-direction}-color: $clearing-arrow-color;\n        }\n      }\n      .clearing-main-next {\n        #{$opposite-direction}: 0;\n        & > span {\n          border-color: transparent;\n          border-#{$default-float}-color: $clearing-arrow-color;\n        }\n      }\n    \n      .clearing-main-prev.disabled,\n      .clearing-main-next.disabled { opacity: 0.3; }\n\n      .clearing-assembled .clearing-container {\n\n        .carousel {\n          background: $clearing-carousel-bg;\n          height: $clearing-carousel-height;\n          margin-top: 10px;\n          text-align: center;\n\n          & > ul {\n            display: inline-block;\n            z-index: 999;\n            height: 100%;\n            position: relative;\n            float: none;\n\n            li {\n              display: block;\n              width: $clearing-carousel-thumb-width;\n              min-height: inherit;\n              float: $default-float;\n              overflow: hidden;\n              margin-#{$opposite-direction}: 0;\n              padding: 0;\n              position: relative;\n              cursor: $cursor-pointer-value;\n              opacity: 0.4;\n              clear: none;\n\n              &.fix-height {\n                img {\n                  height: 100%;\n                  max-width: none;\n                }\n              }\n\n              a.th {\n                border: none;\n                box-shadow: none;\n                display: block;\n              }\n\n              img {\n              cursor: $cursor-pointer-value !important;\n              width: 100% !important;\n              }\n\n              &.visible { opacity: 1; }\n              &:hover { opacity: 0.8; }\n            }\n          }\n        }\n\n        .visible-img {\n          background: $clearing-img-bg;\n          overflow: hidden;\n          height: $clearing-active-img-height;\n        }\n      }\n\n      .clearing-close {\n        position: absolute;\n        top: 10px;\n        #{$opposite-direction}: 20px;\n        padding-#{$default-float}: 0;\n        padding-top: 0;\n      }\n    }\n\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-dropdown-classes: $include-html-classes !default;\n\n// We use these to controls height and width styles.\n$f-dropdown-max-width: 200px !default;\n$f-dropdown-height: auto !default;\n$f-dropdown-max-height: none !default;\n\n// Used for bottom position\n$f-dropdown-margin-top: 2px !default;\n\n// Used for right position\n$f-dropdown-margin-left: $f-dropdown-margin-top !default;\n\n// Used for left position\n$f-dropdown-margin-right: $f-dropdown-margin-top !default;\n\n// Used for top position\n$f-dropdown-margin-bottom: $f-dropdown-margin-top !default;\n\n// We use this to control the background color\n$f-dropdown-bg: $white !default;\n\n// We use this to set the border styles for dropdowns.\n$f-dropdown-border-style: solid !default;\n$f-dropdown-border-width: 1px !default;\n$f-dropdown-border-color: scale-color($white, $lightness: -20%) !default;\n\n// We use these to style the triangle pip.\n$f-dropdown-triangle-size: 6px !default;\n$f-dropdown-triangle-color: $white !default;\n$f-dropdown-triangle-side-offset: 10px !default;\n\n// We use these to control styles for the list elements.\n$f-dropdown-list-style: none !default;\n$f-dropdown-font-color: $charcoal !default;\n$f-dropdown-font-size: rem-calc(14) !default;\n$f-dropdown-list-padding: rem-calc(5, 10) !default;\n$f-dropdown-line-height: rem-calc(18) !default;\n$f-dropdown-list-hover-bg: $smoke !default;\n$dropdown-mobile-default-float: 0 !default;\n\n// We use this to control the styles for when the dropdown has custom content.\n$f-dropdown-content-padding: rem-calc(20) !default;\n\n// Default radius for dropdown.\n$f-dropdown-radius: $global-radius !default;\n\n//\n// @mixins\n//\n//\n// NOTE: Make default max-width change between list and content types. Can add more width with classes, maybe .small, .medium, .large, etc.;\n// We use this to style the dropdown container element.\n// $content-list - Sets list-style. Default: list. Options: [list, content]\n// $triangle - Sets if dropdown has triangle. Default:true.\n// $max-width - Default: $f-dropdown-max-width || 200px.\n@mixin dropdown-container($content:list, $triangle:true, $max-width:$f-dropdown-max-width) {\n  position: absolute;\n  left: -9999px;\n  list-style: $f-dropdown-list-style;\n  margin-#{$default-float}: 0;\n  outline: none;\n\n  > *:first-child { margin-top: 0; }\n  > *:last-child { margin-bottom: 0; }\n\n  @if $content == list {\n    width: 100%;\n    max-height: $f-dropdown-max-height;\n    height: $f-dropdown-height;\n    background: $f-dropdown-bg;\n    border: $f-dropdown-border-style $f-dropdown-border-width $f-dropdown-border-color;\n    font-size: $f-dropdown-font-size;\n    z-index: 89;\n  }\n  @else if $content == content {\n    padding: $f-dropdown-content-padding;\n    width: 100%;\n    height: $f-dropdown-height;\n    max-height: $f-dropdown-max-height;\n    background: $f-dropdown-bg;\n    border: $f-dropdown-border-style $f-dropdown-border-width $f-dropdown-border-color;\n    font-size: $f-dropdown-font-size;\n    z-index: 89;\n  }\n\n  @if $triangle == bottom {\n    margin-top: $f-dropdown-margin-top;\n\n    &:before {\n      @include css-triangle($f-dropdown-triangle-size, $f-dropdown-triangle-color, bottom);\n      position: absolute;\n      top: -($f-dropdown-triangle-size * 2);\n      #{$default-float}: $f-dropdown-triangle-side-offset;\n      z-index: 89;\n    }\n    &:after {\n      @include css-triangle($f-dropdown-triangle-size + 1, $f-dropdown-border-color, bottom);\n      position: absolute;\n      top: -(($f-dropdown-triangle-size + 1) * 2);\n      #{$default-float}: $f-dropdown-triangle-side-offset - 1;\n      z-index: 88;\n    }\n\n    &.right:before {\n      #{$default-float}: auto;\n      #{$opposite-direction}: $f-dropdown-triangle-side-offset;\n    }\n    &.right:after {\n      #{$default-float}: auto;\n      #{$opposite-direction}: $f-dropdown-triangle-side-offset - 1;\n    }\n  }\n\n  @if $triangle == $default-float {\n    margin-top: 0;\n    margin-#{$default-float}: $f-dropdown-margin-right;\n\n    &:before {\n      @include css-triangle($f-dropdown-triangle-size, $f-dropdown-triangle-color, #{$opposite-direction});\n      position: absolute;\n      top: $f-dropdown-triangle-side-offset;\n      #{$default-float}: -($f-dropdown-triangle-size * 2);\n      z-index: 89;\n    }\n    &:after {\n      @include css-triangle($f-dropdown-triangle-size + 1, $f-dropdown-border-color, #{$opposite-direction});\n      position: absolute;\n      top: $f-dropdown-triangle-side-offset - 1;\n      #{$default-float}: -($f-dropdown-triangle-size * 2) - 2;\n      z-index: 88;\n    }\n\n  }\n\n  @if $triangle == $opposite-direction {\n    margin-top: 0;\n    margin-#{$default-float}: -$f-dropdown-margin-right;\n\n    &:before {\n      @include css-triangle($f-dropdown-triangle-size, $f-dropdown-triangle-color, #{$default-float});\n      position: absolute;\n      top: $f-dropdown-triangle-side-offset;\n      #{$opposite-direction}: -($f-dropdown-triangle-size * 2);\n      #{$default-float}: auto;\n      z-index: 89;\n    }\n    &:after {\n      @include css-triangle($f-dropdown-triangle-size + 1, $f-dropdown-border-color, #{$default-float});\n      position: absolute;\n      top: $f-dropdown-triangle-side-offset - 1;\n      #{$opposite-direction}: -($f-dropdown-triangle-size * 2) - 2;\n      #{$default-float}: auto;\n      z-index: 88;\n    }\n\n  }\n\n  @if $triangle == top {\n    margin-top: -$f-dropdown-margin-bottom;\n    margin-left: 0;\n\n    &:before {\n      @include css-triangle($f-dropdown-triangle-size, $f-dropdown-triangle-color, top);\n      position: absolute;\n      top: auto;\n      bottom: -($f-dropdown-triangle-size * 2);\n      #{$default-float}: $f-dropdown-triangle-side-offset;\n      #{$opposite-direction}: auto;\n      z-index: 89;\n    }\n    &:after {\n      @include css-triangle($f-dropdown-triangle-size + 1, $f-dropdown-border-color, top);\n      position: absolute;\n      top: auto;\n      bottom: -($f-dropdown-triangle-size * 2) - 2;\n      #{$default-float}: $f-dropdown-triangle-side-offset - 1;\n      #{$opposite-direction}: auto;\n      z-index: 88;\n    }\n\n  }\n\n  @if $max-width { max-width: $max-width; }\n  @else { max-width: $f-dropdown-max-width; }\n\n}\n\n// @MIXIN\n//\n// We use this to style the list elements or content inside the dropdown.\n\n@mixin dropdown-style {\n  font-size: $f-dropdown-font-size;\n  cursor: $cursor-pointer-value;\n\n  line-height: $f-dropdown-line-height;\n  margin: 0;\n\n  &:hover,\n  &:focus { background: $f-dropdown-list-hover-bg; }\n\n  &.radius { @include radius($f-dropdown-radius); }\n\n  a {\n    display: block;\n    padding: $f-dropdown-list-padding;\n    color: $f-dropdown-font-color;\n  }\n}\n\n@include exports(\"dropdown\") {\n  @if $include-html-dropdown-classes {\n\n    /* Foundation Dropdowns */\n    .f-dropdown {\n      @include dropdown-container(list, bottom);\n\n      &.drop-#{$opposite-direction} {\n        @include dropdown-container(list, #{$default-float});\n      }\n\n      &.drop-#{$default-float} {\n        @include dropdown-container(list, #{$opposite-direction});\n      }\n\n      &.drop-top {\n        @include dropdown-container(list, top);\n      }\n      // max-width: none;\n\n      li { @include dropdown-style; }\n\n      // You can also put custom content in these dropdowns\n      &.content { @include dropdown-container(content, $triangle:false); }\n\n      // Sizes\n      &.tiny    { max-width: 200px; }\n      &.small   { max-width: 300px; }\n      &.medium  { max-width: 500px; }\n      &.large   { max-width: 800px; }\n      &.mega    {\n        width:100%!important;\n        max-width:100%!important;\n\n        &.open{\n          left:0!important;\n        }\n      }\n    }\n\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-button-classes: $include-html-classes !default;\n\n// We use these to set the color of the pip in dropdown buttons\n$dropdown-button-pip-color: $white !default;\n$dropdown-button-pip-color-alt: $oil !default;\n\n$button-pip-tny: rem-calc(6) !default;\n$button-pip-sml: rem-calc(7) !default;\n$button-pip-med: rem-calc(9) !default;\n$button-pip-lrg: rem-calc(11) !default;\n\n// We use these to style tiny dropdown buttons\n$dropdown-button-padding-tny: $button-pip-tny * 7 !default;\n$dropdown-button-pip-size-tny: $button-pip-tny !default;\n$dropdown-button-pip-opposite-tny: $button-pip-tny * 3 !default;\n$dropdown-button-pip-top-tny: calc(-1 * $button-pip-tny / 2) + rem-calc(1) !default;\n\n// We use these to style small dropdown buttons\n$dropdown-button-padding-sml: $button-pip-sml * 7 !default;\n$dropdown-button-pip-size-sml: $button-pip-sml !default;\n$dropdown-button-pip-opposite-sml: $button-pip-sml * 3 !default;\n$dropdown-button-pip-top-sml: calc(-1 * $button-pip-sml / 2) + rem-calc(1) !default;\n\n// We use these to style medium dropdown buttons\n$dropdown-button-padding-med: $button-pip-med * 6 + rem-calc(3) !default;\n$dropdown-button-pip-size-med: $button-pip-med - rem-calc(3) !default;\n$dropdown-button-pip-opposite-med: $button-pip-med * 2.5 !default;\n$dropdown-button-pip-top-med: calc(-1 * $button-pip-med / 2) + rem-calc(2) !default;\n\n// We use these to style large dropdown buttons\n$dropdown-button-padding-lrg: $button-pip-lrg * 5 + rem-calc(3) !default;\n$dropdown-button-pip-size-lrg: $button-pip-lrg - rem-calc(6) !default;\n$dropdown-button-pip-opposite-lrg: $button-pip-lrg * 2.5 !default;\n$dropdown-button-pip-top-lrg: calc(-1 * $button-pip-lrg / 2) + rem-calc(3) !default;\n\n// @mixins\n//\n// Dropdown Button Mixin\n//\n// We use this mixin to build off of the button mixin and add dropdown button styles\n//\n// $padding - Determines the size of button you're working with. Default: medium. Options [tiny, small, medium, large]\n// $pip-color - Color of the little triangle that points to the dropdown. Default: $white.\n// $base-style - Add in base-styles. This can be set to false. Default:true\n\n@mixin dropdown-button($padding: medium, $pip-color: $white, $base-style: true) {\n\n  // We add in base styles, but they can be negated by setting to 'false'.\n  @if $base-style {\n    position: relative;\n    outline: none;\n\n    // This creates the base styles for the triangle pip\n    &::after {\n      position: absolute;\n      content: \"\";\n      width: 0;\n      height: 0;\n      display: block;\n      border-style: solid;\n      border-color: $dropdown-button-pip-color transparent transparent transparent;\n      top: 50%;\n    }\n  }\n\n  // If we're dealing with tiny buttons, use these styles\n  @if $padding ==tiny {\n    padding-#{$opposite-direction}: $dropdown-button-padding-tny;\n\n    &:after {\n      border-width: $dropdown-button-pip-size-tny;\n      #{$opposite-direction}: $dropdown-button-pip-opposite-tny;\n      margin-top: $dropdown-button-pip-top-tny;\n    }\n  }\n\n  // If we're dealing with small buttons, use these styles\n  @if $padding ==small {\n    padding-#{$opposite-direction}: $dropdown-button-padding-sml;\n\n    &::after {\n      border-width: $dropdown-button-pip-size-sml;\n      #{$opposite-direction}: $dropdown-button-pip-opposite-sml;\n      margin-top: $dropdown-button-pip-top-sml;\n    }\n  }\n\n  // If we're dealing with default (medium) buttons, use these styles\n  @if $padding ==medium {\n    padding-#{$opposite-direction}: $dropdown-button-padding-med;\n\n    &::after {\n      border-width: $dropdown-button-pip-size-med;\n      #{$opposite-direction}: $dropdown-button-pip-opposite-med;\n      margin-top: $dropdown-button-pip-top-med;\n    }\n  }\n\n  // If we're dealing with large buttons, use these styles\n  @if $padding ==large {\n    padding-#{$opposite-direction}: $dropdown-button-padding-lrg;\n\n    &::after {\n      border-width: $dropdown-button-pip-size-lrg;\n      #{$opposite-direction}: $dropdown-button-pip-opposite-lrg;\n      margin-top: $dropdown-button-pip-top-lrg;\n    }\n  }\n\n  // We can control the pip color. We didn't use logic in this case, just set it and forget it.\n  @if $pip-color {\n    &::after {\n      border-color: $pip-color transparent transparent transparent;\n    }\n  }\n}\n\n@include exports(\"dropdown-button\") {\n  @if $include-html-button-classes {\n\n    .dropdown.button,\n    button.dropdown {\n      @include dropdown-button;\n\n      &.tiny {\n        @include dropdown-button(tiny, $base-style: false);\n      }\n\n      &.small {\n        @include dropdown-button(small, $base-style: false);\n      }\n\n      &.large {\n        @include dropdown-button(large, $base-style: false);\n      }\n\n      &.secondary:after {\n        border-color: $dropdown-button-pip-color-alt transparent transparent transparent;\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-media-classes: $include-html-classes !default;\n\n// We use these to control video container padding and margins\n$flex-video-padding-top: rem-calc(25) !default;\n$flex-video-padding-bottom: 67.5% !default;\n$flex-video-margin-bottom: rem-calc(16) !default;\n\n// We use this to control widescreen bottom padding\n$flex-video-widescreen-padding-bottom: 56.34% !default;\n\n//\n// @mixins\n//\n\n@mixin flex-video-container {\n  position: relative;\n  padding-top: $flex-video-padding-top;\n  padding-bottom: $flex-video-padding-bottom;\n  height: 0;\n  margin-bottom: $flex-video-margin-bottom;\n  overflow: hidden;\n\n  &.widescreen { padding-bottom: $flex-video-widescreen-padding-bottom; }\n  &.vimeo { padding-top: 0; }\n\n  iframe,\n  object,\n  embed,\n  video {\n    position: absolute;\n    top: 0;\n    #{$default-float}: 0;\n    width: 100%;\n    height: 100%;\n  }\n}\n\n@include exports(\"flex-video\") {\n  @if $include-html-media-classes {\n    .flex-video { @include flex-video-container; }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-inline-list-classes: $include-html-classes !default;\n\n// We use this to control the margins and padding of the inline list.\n$inline-list-top-margin: 0 !default;\n$inline-list-opposite-margin: 0 !default;\n$inline-list-bottom-margin: rem-calc(17) !default;\n$inline-list-default-float-margin: rem-calc(-22) !default;\n$inline-list-default-float-list-margin: rem-calc(22) !default;\n\n$inline-list-padding: 0 !default;\n\n// We use this to control the overflow of the inline list.\n$inline-list-overflow: hidden !default;\n\n// We use this to control the list items\n$inline-list-display: block !default;\n\n// We use this to control any elements within list items\n$inline-list-children-display: block !default;\n\n//\n// @mixins\n//\n// We use this mixin to create inline lists\n@mixin inline-list {\n  margin: $inline-list-top-margin auto $inline-list-bottom-margin auto;\n  margin-#{$default-float}: $inline-list-default-float-margin;\n  margin-#{$opposite-direction}: $inline-list-opposite-margin;\n  padding: $inline-list-padding;\n  list-style: none;\n  overflow: $inline-list-overflow;\n\n  & > li {\n    list-style: none;\n    float: $default-float;\n    margin-#{$default-float}: $inline-list-default-float-list-margin;\n    display: $inline-list-display;\n    &>* { display: $inline-list-children-display; }\n  }\n}\n\n@include exports(\"inline-list\") {\n  @if $include-html-inline-list-classes {\n    .inline-list {\n      @include inline-list();\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-keystroke-classes: $include-html-classes !default;\n\n// We use these to control text styles.\n$keystroke-font: \"Consolas\", \"Menlo\", \"Courier\", monospace !default;\n$keystroke-font-size: inherit !default;\n$keystroke-font-color: $jet !default;\n$keystroke-font-color-alt: $white !default;\n$keystroke-function-factor: -7% !default;\n\n// We use this to control keystroke padding.\n$keystroke-padding: rem-calc(2 4 0) !default;\n\n// We use these to control background and border styles.\n$keystroke-bg: scale-color($white, $lightness: $keystroke-function-factor) !default;\n$keystroke-border-style: solid !default;\n$keystroke-border-width: 1px !default;\n$keystroke-border-color: scale-color($keystroke-bg, $lightness: $keystroke-function-factor) !default;\n$keystroke-radius: $global-radius !default;\n\n//\n// @mixins\n//\n// We use this mixin to create keystroke styles.\n// $bg - Default: $keystroke-bg || scale-color($white, $lightness: $keystroke-function-factor) !default;\n@mixin keystroke($bg:$keystroke-bg) {\n  // This find the lightness percentage of the background color.\n  $bg-lightness: lightness($bg);\n\n  background-color: $bg;\n  border-color: scale-color($bg, $lightness: $keystroke-function-factor);\n\n  // We adjust the font color based on the brightness of the background.\n  @if $bg-lightness > 70% { color: $keystroke-font-color; }\n  @else { color: $keystroke-font-color-alt; }\n\n  border-style: $keystroke-border-style;\n  border-width: $keystroke-border-width;\n  margin: 0;\n  font-family: $keystroke-font;\n  font-size: $keystroke-font-size;\n  padding: $keystroke-padding;\n}\n\n@include exports(\"keystroke\") {\n  @if $include-html-keystroke-classes  {\n    .keystroke,\n    kbd {\n      @include keystroke;\n      @include radius($keystroke-radius);\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-panel-classes: $include-html-classes !default;\n\n// We use these to control the background and border styles\n$panel-bg: scale-color($white, $lightness: -5%) !default;\n$panel-border-style: solid !default;\n$panel-border-size: 1px !default;\n\n// We use this % to control how much we darken things on hover\n$panel-function-factor: -11% !default;\n$panel-border-color: scale-color($panel-bg, $lightness: $panel-function-factor) !default;\n\n// We use these to set default inner padding and bottom margin\n$panel-margin-bottom: rem-calc(20) !default;\n$panel-padding: rem-calc(20) !default;\n\n// We use these to set default font colors\n$panel-font-color: $oil !default;\n$panel-font-color-alt: $white !default;\n\n$panel-header-adjust: true !default;\n$callout-panel-link-color: $primary-color !default;\n$callout-panel-link-color-hover: scale-color($callout-panel-link-color, $lightness: -14%) !default;\n\n//\n// @mixins\n//\n// We use this mixin to create panels.\n// $bg - Sets the panel background color. Default: $panel-pg || scale-color($white, $lightness: -5%) !default\n// $padding - Sets the panel padding amount. Default: $panel-padding || rem-calc(20)\n// $adjust - Sets the font color based on the darkness of the bg & resets header line-heights for panels. Default: $panel-header-adjust || true\n@mixin panel($bg: $panel-bg, $padding: $panel-padding, $adjust: $panel-header-adjust) {\n\n  @if $bg {\n    $bg-lightness: lightness($bg);\n\n    border-style: $panel-border-style;\n    border-width: $panel-border-size;\n    border-color: scale-color($bg, $lightness: $panel-function-factor);\n    margin-bottom: $panel-margin-bottom;\n    padding: $padding;\n\n    background: $bg;\n\n    @if $bg-lightness >=50% {\n      color: $panel-font-color;\n    }\n\n    @else {\n      color: $panel-font-color-alt;\n    }\n\n    // Respect the padding, fool.\n    &>:first-child {\n      margin-top: 0;\n    }\n\n    &>:last-child {\n      margin-bottom: 0;\n    }\n\n    @if $adjust {\n\n      // We set the font color based on the darkness of the bg.\n      @if $bg-lightness >=50% {\n\n        h1,\n        h2,\n        h3,\n        h4,\n        h5,\n        h6,\n        p,\n        li,\n        dl {\n          color: $panel-font-color;\n        }\n      }\n\n      @else {\n\n        h1,\n        h2,\n        h3,\n        h4,\n        h5,\n        h6,\n        p,\n        li,\n        dl {\n          color: $panel-font-color-alt;\n        }\n      }\n\n      // reset header line-heights for panels\n      h1,\n      h2,\n      h3,\n      h4,\n      h5,\n      h6 {\n        line-height: 1;\n        margin-bottom: calc(rem-calc(20) / 2);\n\n        &.subheader {\n          line-height: 1.4;\n        }\n      }\n    }\n  }\n}\n\n@include exports(\"panel\") {\n  @if $include-html-panel-classes {\n\n    /* Panels */\n    .panel {\n      @include panel;\n\n      &.callout {\n        @include panel(scale-color($primary-color, $lightness: 94%));\n\n        a:not(.button) {\n          color: $callout-panel-link-color;\n\n          &:hover,\n          &:focus {\n            color: $callout-panel-link-color-hover;\n          }\n        }\n      }\n\n      &.radius {\n        @include radius;\n      }\n\n    }\n\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n@import \"grid\";\n\n//\n// @name _reveal.scss\n// @dependencies _global.scss\n//\n\n$include-html-reveal-classes: $include-html-classes !default;\n\n// We use these to control the style of the reveal overlay.\n$reveal-overlay-bg: rgba($black, .45) !default;\n$reveal-overlay-bg-old: $black !default;\n\n// We use these to control the style of the modal itself.\n$reveal-modal-bg: $white !default;\n$reveal-position-top: rem-calc(250) !default;\n$reveal-default-width: 80% !default;\n$reveal-max-width: $row-width !default;\n$reveal-modal-padding: rem-calc(20) !default;\n$reveal-box-shadow: 0 0 10px rgba($black,.4) !default;\n\n// We use these to style the reveal close button\n$reveal-close-font-size: rem-calc(40) !default;\n$reveal-close-top: rem-calc(10) !default;\n$reveal-close-side: rem-calc(22) !default;\n$reveal-close-color: $base !default;\n$reveal-close-weight: $font-weight-bold !default;\n\n// We use this to set the default radius used throughout the core.\n$reveal-radius: $global-radius !default;\n$reveal-round: $global-rounded !default;\n\n// We use these to control the modal border\n$reveal-border-style: solid !default;\n$reveal-border-width: 1px !default;\n$reveal-border-color: $steel !default;\n\n$reveal-modal-class: \"reveal-modal\" !default;\n$close-reveal-modal-class: \"close-reveal-modal\" !default;\n\n//\n// @mixins\n//\n\n// We use this to create the reveal background overlay styles\n@mixin reveal-bg( $include-z-index-value: true ) {\n  //position: fixed;\n  position: absolute; // allows modal background to extend beyond window position\n  top: 0;\n  bottom: 0;\n  left: 0;\n  right: 0;\n  background: $reveal-overlay-bg-old; // Autoprefixer should be used to avoid such variables needed when Foundation for Sites can do so in the near future.\n  background: $reveal-overlay-bg;\n  z-index: if( $include-z-index-value, 1004, auto );\n  display: none;\n  #{$default-float}: 0;\n}\n\n// We use this mixin to create the structure of a reveal modal\n//\n// $base-style - Provides reveal base styles, can be set to false to override. Default: true, Options: false\n// $width - Sets reveal width Default: $reveal-default-width || 80%\n//\n@mixin reveal-modal-base( $base-style: true, $width:$reveal-default-width, $max-width:$reveal-max-width, $border-radius: $reveal-radius) {\n  @if $base-style {\n    visibility: hidden;\n    display: none;\n    position: absolute;\n    z-index: 1005;\n    width: 100vw;\n    top:0;\n    border-radius: $border-radius;\n    #{$default-float}: 0;\n\n    @media #{$small-only} {\n      min-height:100vh;\n    }\n\n    // Make sure rows don't have a min-width on them\n    .column, .columns { min-width: 0; }\n\n    // Get rid of margin from first and last element inside modal\n    & > :first-child { margin-top: 0; }\n\n    & > :last-child { margin-bottom: 0; }\n  }\n\n  @if $width {\n    @media #{$medium-up} {\n      width: $width;\n      max-width: $max-width;\n      left: 0;\n      right: 0;\n      margin: 0 auto;\n    }\n  }\n}\n\n// We use this to style the reveal modal defaults\n//\n// $bg - Sets background color of reveal modal. Default: $reveal-modal-bg || $white\n// $padding - Padding to apply to reveal modal. Default: $reveal-modal-padding.\n// $border - Choose whether reveal uses a border. Default: true, Options: false\n// $border-style - Set reveal border style. Default: $reveal-border-style || solid\n// $border-width - Width of border (i.e. 1px). Default: $reveal-border-width.\n// $border-color - Color of border. Default: $reveal-border-color.\n// $box-shadow - Choose whether or not to include the default box-shadow. Default: true, Options: false\n// $radius - If true, set to modal radius which is $global-radius || explicitly set radius amount in px (ex. $radius:10px). Default: false\n// $top-offset - Default: $reveal-position-top || 50px\n@mixin reveal-modal-style(\n  $bg:false,\n  $padding:false,\n  $border:false,\n  $border-style:$reveal-border-style,\n  $border-width:$reveal-border-width,\n  $border-color:$reveal-border-color,\n  $box-shadow:false,\n  $radius:false,\n  $top-offset:false) {\n\n  @if $bg { background-color: $bg; }\n  @if $padding != false { padding: $padding; }\n\n  @if $border { border: $border-style $border-width $border-color; }\n\n  // We can choose whether or not to include the default box-shadow.\n  @if $box-shadow {\n    box-shadow: $reveal-box-shadow;\n  }\n\n  // We can control how much radius is used on the modal\n  @if $radius == true { @include radius($reveal-radius); }\n  @else if $radius { @include radius($radius); }\n\n  @if $top-offset {\n    @media #{$medium-up} {\n      top: $top-offset;\n    }\n  }\n}\n\n// We use this to create a close button for the reveal modal\n//\n// $color - Default: $reveal-close-color || $base\n@mixin reveal-close($color:$reveal-close-color) {\n  font-size: $reveal-close-font-size;\n  line-height: 1;\n  position: absolute;\n  top: $reveal-close-top;\n  #{$opposite-direction}: $reveal-close-side;\n  color: $color;\n  font-weight: $reveal-close-weight;\n  cursor: $cursor-pointer-value;\n}\n\n@include exports(\"reveal\") {\n  @if $include-html-reveal-classes {\n\n    // Reveal Modals\n    .reveal-modal-bg { @include reveal-bg; }\n\n    .#{$reveal-modal-class} {\n      @include reveal-modal-base;\n      @include reveal-modal-style(\n        $bg:$reveal-modal-bg,\n        $padding:$reveal-modal-padding,\n        $border:true,\n        $box-shadow:true,\n        $radius:false,\n        $top-offset:$reveal-position-top\n      );\n      @include reveal-modal-style($padding:$reveal-modal-padding * 1.5);\n\n      &.radius { @include reveal-modal-style($radius:true); }\n      &.round  { @include reveal-modal-style($radius:$reveal-round); }\n      &.collapse { @include reveal-modal-style($padding:0); }\n      &.tiny  { @include reveal-modal-base(false, 30%); }\n      &.small { @include reveal-modal-base(false, 40%); }\n      &.medium  { @include reveal-modal-base(false, 60%); }\n      &.large { @include reveal-modal-base(false, 70%); }\n      &.xlarge { @include reveal-modal-base(false, 95%); }\n      &.full {\n        @include reveal-modal-base(false, 100vw);\n        top:0;\n        left:0;\n        height:100%;\n        height: 100vh;\n        min-height:100vh;\n        max-width: none !important;\n        margin-left: 0 !important;\n      }\n\n      .#{$close-reveal-modal-class} { @include reveal-close; }\n    }\n\n    dialog {\n      @extend .#{$reveal-modal-class};\n      display: none;\n\n      &::backdrop, & + .backdrop {\n        @include reveal-bg(false);\n      }\n\n      &[open]{\n        display: block;\n      }\n    }\n\n    // Reveal Print Styles: It should be invisible, adds no value being printed.\n    @media print {\n      dialog, .#{$reveal-modal-class} { \n        display: none;\n        background: $white !important;\n      }\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n\n$include-html-nav-classes: $include-html-classes !default;\n\n// We use this to control padding.\n$side-nav-padding: rem-calc(14 0) !default;\n\n// We use these to control list styles.\n$side-nav-list-type: none !default;\n$side-nav-list-position: outside !default;\n$side-nav-list-margin: rem-calc(0 0 7 0) !default;\n\n// We use these to control link styles.\n$side-nav-link-color: $primary-color !default;\n$side-nav-link-color-active: scale-color($side-nav-link-color, $lightness: 30%) !default;\n$side-nav-link-color-hover: scale-color($side-nav-link-color, $lightness: 30%) !default;\n$side-nav-link-bg-hover: hsla(0deg, 0%, 0%, 0.025) !default;\n$side-nav-link-margin: 0 !default;\n$side-nav-link-padding: rem-calc(7 14) !default;\n$side-nav-font-size: rem-calc(14) !default;\n$side-nav-font-weight: $font-weight-normal !default;\n$side-nav-font-weight-active: $side-nav-font-weight !default;\n$side-nav-font-family: $body-font-family !default;\n$side-nav-font-family-active: $side-nav-font-family !default;\n\n// We use these to control heading styles.\n$side-nav-heading-color: $side-nav-link-color !default;\n$side-nav-heading-font-size: $side-nav-font-size !default;\n$side-nav-heading-font-weight: bold !default;\n$side-nav-heading-text-transform: uppercase !default;\n\n// We use these to control border styles\n$side-nav-divider-size: 1px !default;\n$side-nav-divider-style: solid !default;\n$side-nav-divider-color: scale-color($white, $lightness: 10%) !default;\n\n\n//\n// @mixins\n//\n\n\n// We use this to style the side-nav\n//\n// $divider-color - Border color of divider. Default: $side-nav-divider-color.\n// $font-size - Font size of nav items. Default: $side-nav-font-size.\n// $link-color - Color of navigation links. Default: $side-nav-link-color.\n// $link-color-hover - Color of navigation links when hovered. Default: $side-nav-link-color-hover.\n@mixin side-nav($divider-color: $side-nav-divider-color,\n  $font-size: $side-nav-font-size,\n  $link-color: $side-nav-link-color,\n  $link-color-hover: $side-nav-link-color-hover,\n  $link-bg-hover: $side-nav-link-bg-hover) {\n  display: block;\n  margin: 0;\n  padding: $side-nav-padding;\n  list-style-type: $side-nav-list-type;\n  list-style-position: $side-nav-list-position;\n  font-family: $side-nav-font-family;\n\n  li {\n    margin: $side-nav-list-margin;\n    font-size: $font-size;\n    font-weight: $side-nav-font-weight;\n\n    a:not(.button) {\n      display: block;\n      color: $link-color;\n      margin: $side-nav-link-margin;\n      padding: $side-nav-link-padding;\n\n      &:hover,\n      &:focus {\n        background: $link-bg-hover;\n        color: $link-color-hover;\n      }\n    }\n\n    &.active>a:first-child:not(.button) {\n      color: $side-nav-link-color-active;\n      font-weight: $side-nav-font-weight-active;\n      font-family: $side-nav-font-family-active;\n    }\n\n    &.divider {\n      border-top: $side-nav-divider-size $side-nav-divider-style;\n      height: 0;\n      padding: 0;\n      list-style: none;\n      border-top-color: $divider-color;\n    }\n\n    &.heading {\n      color: $side-nav-heading-color;\n\n      font: {\n        size: $side-nav-heading-font-size;\n        weight: $side-nav-heading-font-weight;\n      }\n\n      text-transform: $side-nav-heading-text-transform;\n    }\n  }\n}\n\n@include exports(\"side-nav\") {\n  @if $include-html-nav-classes {\n    .side-nav {\n      @include side-nav;\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @name _sub-nav.scss\n// @dependencies _global.scss\n//\n\n//\n// @variables\n//\n\n$include-html-nav-classes: $include-html-classes !default;\n\n// We use these to control margin and padding\n$sub-nav-list-margin: rem-calc(-4 0 18) !default;\n$sub-nav-list-padding-top: rem-calc(4) !default;\n\n// We use this to control the definition\n$sub-nav-font-family: $body-font-family !default;\n$sub-nav-font-size: rem-calc(14) !default;\n$sub-nav-font-color: $aluminum !default;\n$sub-nav-font-weight: $font-weight-normal !default;\n$sub-nav-text-decoration: none !default;\n$sub-nav-padding: rem-calc(3 16) !default;\n$sub-nav-border-radius: 3px !default;\n$sub-nav-font-color-hover: scale-color($sub-nav-font-color, $lightness: -25%) !default;\n\n\n// We use these to control the active item styles\n\n$sub-nav-active-font-weight: $font-weight-normal !default;\n$sub-nav-active-bg: $primary-color !default;\n$sub-nav-active-bg-hover: scale-color($sub-nav-active-bg, $lightness: -14%) !default;\n$sub-nav-active-color: $white !default;\n$sub-nav-active-padding: $sub-nav-padding !default;\n$sub-nav-active-cursor: default !default;\n\n$sub-nav-item-divider: \"\" !default;\n$sub-nav-item-divider-margin: rem-calc(12) !default;\n\n//\n// @mixins\n//\n\n\n// Create a sub-nav item\n//\n// $font-color - Font color. Default: $sub-nav-font-color.\n// $font-size - Font size. Default: $sub-nav-font-size.\n// $active-bg - Background of active nav item. Default: $sub-nav-active-bg.\n// $active-bg-hover - Background of active nav item, when hovered. Default: $sub-nav-active-bg-hover.\n@mixin sub-nav(\n  $font-color: $sub-nav-font-color,\n  $font-size: $sub-nav-font-size,\n  $active-bg: $sub-nav-active-bg,\n  $active-bg-hover: $sub-nav-active-bg-hover) {\n  display: block;\n  width: auto;\n  overflow: hidden;\n  margin: $sub-nav-list-margin;\n  padding-top: $sub-nav-list-padding-top;\n\n  dt {\n    text-transform: uppercase;\n  }\n\n  dt,\n  dd,\n  li {\n    float: $default-float;\n    display: inline;\n    margin-#{$default-float}: rem-calc(16);\n    margin-bottom: 0;\n    font-family: $sub-nav-font-family;\n    font-weight: $sub-nav-font-weight;\n    font-size: $font-size;\n    color: $font-color;\n\n    a {\n      text-decoration: $sub-nav-text-decoration;\n      color: $sub-nav-font-color;\n      padding: $sub-nav-padding;\n      &:hover {\n        color: $sub-nav-font-color-hover;\n      }\n    }\n\n    &.active a {\n      @include radius($sub-nav-border-radius);\n      font-weight: $sub-nav-active-font-weight;\n      background: $active-bg;\n      padding: $sub-nav-active-padding;\n      cursor: $sub-nav-active-cursor;\n      color: $sub-nav-active-color;\n      &:hover {\n        background: $active-bg-hover;\n      }\n    }\n    @if $sub-nav-item-divider != \"\" {\n      margin-#{$default-float}: 0;\n\n      &:before {\n        content: \"#{$sub-nav-item-divider}\";\n        margin: 0 $sub-nav-item-divider-margin;\n      }\n\n      &:first-child:before {\n        content: \"\";\n        margin: 0;\n      }\n    }\n  }\n}\n\n@include exports(\"sub-nav\") {\n  @if $include-html-nav-classes {\n    .sub-nav { @include sub-nav; }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @name _tables.scss\n// @dependencies _global.scss\n//\n\n//\n// @variables\n//\n\n$include-html-table-classes: $include-html-classes !default;\n\n// These control the background color for the table and even rows\n$table-bg: $white !default;\n$table-even-row-bg: $snow !default;\n\n// These control the table cell border style\n$table-border-style: solid !default;\n$table-border-size: 1px !default;\n$table-border-color: $gainsboro !default;\n\n// These control the table head styles\n$table-head-bg: $white-smoke !default;\n$table-head-font-size: rem-calc(14) !default;\n$table-head-font-color: $jet !default;\n$table-head-font-weight: $font-weight-bold !default;\n$table-head-padding: rem-calc(8 10 10) !default;\n\n// These control the table foot styles\n$table-foot-bg: $table-head-bg !default;\n$table-foot-font-size: $table-head-font-size !default;\n$table-foot-font-color: $table-head-font-color !default;\n$table-foot-font-weight: $table-head-font-weight !default;\n$table-foot-padding: $table-head-padding !default;\n\n// These control the caption\n$table-caption-bg: transparent !default;\n$table-caption-font-color: $table-head-font-color !default;\n$table-caption-font-size: rem-calc(16) !default;\n$table-caption-font-weight: bold !default;\n\n// These control the row padding and font styles\n$table-row-padding: rem-calc(9 10) !default;\n$table-row-font-size: rem-calc(14) !default;\n$table-row-font-color: $jet !default;\n$table-line-height: rem-calc(18) !default;\n\n// These are for controlling the layout, display and margin of tables\n$table-layout: auto !default;\n$table-display: table-cell !default;\n$table-margin-bottom: rem-calc(20) !default;\n\n\n//\n// @mixins\n//\n\n@mixin table {\n  background: $table-bg;\n  margin-bottom: $table-margin-bottom;\n  border: $table-border-style $table-border-size $table-border-color;\n  table-layout: $table-layout;\n\n  caption {\n    background: $table-caption-bg;\n    color: $table-caption-font-color;\n    font: {\n      size: $table-caption-font-size;\n      weight: $table-caption-font-weight;\n    }\n  }\n\n  thead {\n    background: $table-head-bg;\n\n    tr {\n      th,\n      td {\n        padding: $table-head-padding;\n        font-size: $table-head-font-size;\n        font-weight: $table-head-font-weight;\n        color: $table-head-font-color;\n      }\n    }\n  }\n\n  tfoot {\n    background: $table-foot-bg;\n\n    tr {\n      th,\n      td {\n        padding: $table-foot-padding;\n        font-size: $table-foot-font-size;\n        font-weight: $table-foot-font-weight;\n        color: $table-foot-font-color;\n      }\n    }\n  }\n\n  tr {\n    th,\n    td {\n      padding: $table-row-padding;\n      font-size: $table-row-font-size;\n      color: $table-row-font-color;\n      text-align: $default-float;\n    }\n\n    &.even,\n    &.alt,\n    &:nth-of-type(even) { background: $table-even-row-bg; }\n  }\n\n  thead tr th,\n  tfoot tr th,\n  tfoot tr td,\n  tbody tr th,\n  tbody tr td,\n  tr td { display: $table-display; line-height: $table-line-height; }\n}\n\n\n@include exports(\"table\") {\n  @if $include-html-table-classes {\n    table {\n      @include table;\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @name _thumbs.scss\n// @dependencies _globals.scss\n//\n\n//\n// @variables\n//\n\n$include-html-media-classes: $include-html-classes !default;\n\n// We use these to control border styles\n$thumb-border-style: solid !default;\n$thumb-border-width: 4px !default;\n$thumb-border-color: $white !default;\n$thumb-box-shadow: 0 0 0 1px rgba($black,.2) !default;\n$thumb-box-shadow-hover: 0 0 6px 1px rgba($primary-color,0.5) !default;\n\n// Radius and transition speed for thumbs\n$thumb-radius: $global-radius !default;\n$thumb-transition-speed: 200ms !default;\n\n//\n// @mixins\n//\n\n// We use this to create image thumbnail styles.\n//\n// $border-width - Width of border around thumbnail. Default: $thumb-border-width.\n// $box-shadow - Box shadow to apply to thumbnail. Default: $thumb-box-shadow.\n// $box-shadow-hover - Box shadow to apply on hover. Default: $thumb-box-shadow-hover.\n@mixin thumb(\n  $border-width:$thumb-border-width, \n  $box-shadow:$thumb-box-shadow, \n  $box-shadow-hover:$thumb-box-shadow-hover) {\n  line-height: 0;\n  display: inline-block;\n  border: $thumb-border-style $border-width $thumb-border-color;\n  max-width: 100%;\n  box-shadow: $box-shadow;\n\n  &:hover,\n  &:focus {\n    box-shadow: $box-shadow-hover;\n  }\n}\n\n\n@include exports(\"thumb\") {\n  @if $include-html-media-classes {\n\n    /* Image Thumbnails */\n    .th {\n      @include thumb;\n      @include single-transition(all,$thumb-transition-speed,ease-out);\n\n      &.radius { @include radius($thumb-radius); }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n$include-html-type-classes: $include-html-classes !default;\n\n// We use these to control header font styles\n$header-font-family: $body-font-family !default;\n$header-font-weight: $font-weight-normal !default;\n$header-font-style: $font-weight-normal !default;\n$header-font-color: $jet !default;\n$header-line-height: 1.4 !default;\n$header-top-margin: .2rem !default;\n$header-bottom-margin: .5rem !default;\n$header-text-rendering: optimizeLegibility !default;\n\n// We use these to control header font sizes\n$h1-font-size: rem-calc(44) !default;\n$h2-font-size: rem-calc(37) !default;\n$h3-font-size: rem-calc(27) !default;\n$h4-font-size: rem-calc(23) !default;\n$h5-font-size: rem-calc(18) !default;\n$h6-font-size: 1rem !default;\n\n// We use these to control header size reduction on small screens\n$h1-font-reduction: rem-calc(10) !default;\n$h2-font-reduction: rem-calc(10) !default;\n$h3-font-reduction: rem-calc(5) !default;\n$h4-font-reduction: rem-calc(5) !default;\n$h5-font-reduction: 0 !default;\n$h6-font-reduction: 0 !default;\n\n// These control how subheaders are styled.\n$subheader-line-height: 1.4 !default;\n$subheader-font-color: scale-color($header-font-color, $lightness: 35%) !default;\n$subheader-font-weight: $font-weight-normal !default;\n$subheader-top-margin: .2rem !default;\n$subheader-bottom-margin: .5rem !default;\n\n// A general <small> styling\n$small-font-size: 60% !default;\n$small-font-color: scale-color($header-font-color, $lightness: 35%) !default;\n\n// We use these to style paragraphs\n$paragraph-font-family: inherit !default;\n$paragraph-font-weight: $font-weight-normal !default;\n$paragraph-font-size: 1rem !default;\n$paragraph-line-height: 1.6 !default;\n$paragraph-margin-bottom: rem-calc(20) !default;\n$paragraph-aside-font-size: rem-calc(14) !default;\n$paragraph-aside-line-height: 1.35 !default;\n$paragraph-aside-font-style: italic !default;\n$paragraph-text-rendering: optimizeLegibility !default;\n\n// We use these to style <code> tags\n$code-color: $oil !default;\n$code-font-family: $font-family-monospace !default;\n$code-font-weight: $font-weight-normal !default;\n$code-background-color: scale-color($secondary-color, $lightness: 70%) !default;\n$code-border-size: 0px !default;\n$code-border-style: solid !default;\n$code-border-color: scale-color($code-background-color, $lightness: -10%) !default;\n$code-padding: rem-calc(2) rem-calc(5) rem-calc(1) !default;\n\n// We use these to style anchors\n$anchor-text-decoration: none !default;\n$anchor-text-decoration-hover: none !default;\n$anchor-font-color: $primary-color !default;\n$anchor-font-color-hover: scale-color($anchor-font-color, $lightness: -14%) !default;\n\n// We use these to style the <hr> element\n$hr-border-width: 1px !default;\n$hr-border-style: solid !default;\n$hr-border-color: $gainsboro !default;\n$hr-margin: rem-calc(20) !default;\n\n// We use these to style lists\n$list-font-family: $paragraph-font-family !default;\n$list-font-size: $paragraph-font-size !default;\n$list-line-height: $paragraph-line-height !default;\n$list-margin-bottom: $paragraph-margin-bottom !default;\n$list-style-position: outside !default;\n$list-side-margin: 1.1rem !default;\n$list-ordered-side-margin: 1.4rem !default;\n$list-side-margin-no-bullet: 0 !default;\n$list-nested-margin: rem-calc(20) !default;\n$definition-list-header-weight: $font-weight-bold !default;\n$definition-list-header-margin-bottom: .3rem !default;\n$definition-list-margin-bottom: rem-calc(12) !default;\n\n// We use these to style blockquotes\n$blockquote-font-color: scale-color($header-font-color, $lightness: 35%) !default;\n$blockquote-padding: rem-calc(9 20 0 19) !default;\n$blockquote-border: 1px solid $gainsboro !default;\n$blockquote-cite-font-size: rem-calc(13) !default;\n$blockquote-cite-font-color: scale-color($header-font-color, $lightness: 23%) !default;\n$blockquote-cite-link-color: $blockquote-cite-font-color !default;\n\n// Acronym styles\n$acronym-underline: 1px dotted $gainsboro !default;\n\n// We use these to control padding and margin\n$microformat-padding: rem-calc(10 12) !default;\n$microformat-margin: rem-calc(0 0 20 0) !default;\n\n// We use these to control the border styles\n$microformat-border-width: 1px !default;\n$microformat-border-style: solid !default;\n$microformat-border-color: $gainsboro !default;\n\n// We use these to control full name font styles\n$microformat-fullname-font-weight: $font-weight-bold !default;\n$microformat-fullname-font-size: rem-calc(15) !default;\n\n// We use this to control the summary font styles\n$microformat-summary-font-weight: $font-weight-bold !default;\n\n// We use this to control abbr padding\n$microformat-abbr-padding: rem-calc(0 1) !default;\n\n// We use this to control abbr font styles\n$microformat-abbr-font-weight: $font-weight-bold !default;\n$microformat-abbr-font-decoration: none !default;\n\n// Text alignment class names\n$align-class-names:\n  small-only,\n  small,\n  medium-only,\n  medium,\n  large-only,\n  large,\n  xlarge-only,\n  xlarge,\n  xxlarge-only,\n  xxlarge;\n\n// Text alignment breakpoints\n$align-class-breakpoints:\n  $small-only,\n  $small-up,\n  $medium-only,\n  $medium-up,\n  $large-only,\n  $large-up,\n  $xlarge-only,\n  $xlarge-up,\n  $xxlarge-only,\n  $xxlarge-up;\n\n// Generates text align and justify classes\n@mixin align-classes{\n  .text-left    { text-align: left !important; }\n  .text-right   { text-align: right !important; }\n  .text-center  { text-align: center !important; }\n  .text-justify { text-align: justify !important; }\n\n  @for $i from 1 through length($align-class-names) {\n    @media #{(nth($align-class-breakpoints, $i))} {\n      .#{(nth($align-class-names, $i))}-text-left { text-align: left !important; }\n      .#{(nth($align-class-names, $i))}-text-right   { text-align: right !important; }\n      .#{(nth($align-class-names, $i))}-text-center  { text-align: center !important; }\n      .#{(nth($align-class-names, $i))}-text-justify { text-align: justify !important; }\n    }\n  }\n}\n\n//\n// Typography Placeholders\n//\n\n// These will throw a deprecation warning if used within a media query.\n@mixin lead {\n  font-size: $paragraph-font-size + rem-calc(3.5);\n  line-height: 1.6;\n}\n\n@mixin subheader {\n  line-height: $subheader-line-height;\n  color: $subheader-font-color;\n  font-weight: $subheader-font-weight;\n  margin-top: $subheader-top-margin;\n  margin-bottom: $subheader-bottom-margin;\n}\n@include exports(\"type\") {\n  @if $include-html-type-classes {\n    // Responsive Text alignment\n    @include align-classes;\n\n    /* Typography resets */\n    div,\n    dl,\n    dt,\n    dd,\n    ul,\n    ol,\n    li,\n    h1,\n    h2,\n    h3,\n    h4,\n    h5,\n    h6,\n    pre,\n    form,\n    p,\n    blockquote,\n    th,\n    td {\n      margin:0;\n      padding:0;\n    }\n\n    /* Default Link Styles */\n    a {\n      color: $anchor-font-color;\n      text-decoration: $anchor-text-decoration;\n      line-height: inherit;\n\n      &:hover,\n      &:focus {\n        color: $anchor-font-color-hover;\n        @if $anchor-text-decoration-hover != $anchor-text-decoration {\n        \ttext-decoration: $anchor-text-decoration-hover;\n        }\n      }\n\n      img { border:none; }\n    }\n\n    /* Default paragraph styles */\n    p {\n      font-family: $paragraph-font-family;\n      font-weight: $paragraph-font-weight;\n      font-size: $paragraph-font-size;\n      line-height: $paragraph-line-height;\n      margin-bottom: $paragraph-margin-bottom;\n      text-rendering: $paragraph-text-rendering;\n\n      &.lead { @include lead; }\n\n      & aside {\n        font-size: $paragraph-aside-font-size;\n        line-height: $paragraph-aside-line-height;\n        font-style: $paragraph-aside-font-style;\n      }\n    }\n\n    /* Default header styles */\n    h1, h2, h3, h4, h5, h6 {\n      font-family: $header-font-family;\n      font-weight: $header-font-weight;\n      font-style: $header-font-style;\n      color: $header-font-color;\n      text-rendering: $header-text-rendering;\n      margin-top: $header-top-margin;\n      margin-bottom: $header-bottom-margin;\n      line-height: $header-line-height;\n\n      small {\n        font-size: $small-font-size;\n        color: $small-font-color;\n        line-height: 0;\n      }\n    }\n\n    h1 { font-size: $h1-font-size - $h1-font-reduction; }\n    h2 { font-size: $h2-font-size - $h2-font-reduction; }\n    h3 { font-size: $h3-font-size - $h3-font-reduction; }\n    h4 { font-size: $h4-font-size - $h4-font-reduction; }\n    h5 { font-size: $h5-font-size - $h5-font-reduction; }\n    h6 { font-size: $h6-font-size - $h6-font-reduction; }\n\n    .subheader { @include subheader; }\n\n    hr {\n      border: $hr-border-style $hr-border-color;\n      border-width: $hr-border-width 0 0;\n      clear: both;\n      margin: $hr-margin 0 ($hr-margin - rem-calc($hr-border-width));\n      height: 0;\n    }\n\n    /* Helpful Typography Defaults */\n    em,\n    i {\n      font-style: italic;\n      line-height: inherit;\n    }\n\n    strong,\n    b {\n      font-weight: $font-weight-bold;\n      line-height: inherit;\n    }\n\n    small {\n      font-size: $small-font-size;\n      line-height: inherit;\n    }\n\n    code {\n      font-family: $code-font-family;\n      font-weight: $code-font-weight;\n      color: $code-color;\n      background-color: $code-background-color;\n      border-width: $code-border-size;\n      border-style: $code-border-style;\n      border-color: $code-border-color;\n      padding: $code-padding;\n    }\n\n    /* Lists */\n    ul,\n    ol,\n    dl {\n      font-size: $list-font-size;\n      line-height: $list-line-height;\n      margin-bottom: $list-margin-bottom;\n      list-style-position: $list-style-position;\n      font-family: $list-font-family;\n    }\n\n    ul {\n      margin-#{$default-float}: $list-side-margin;\n      &.no-bullet {\n        margin-#{$default-float}: $list-side-margin-no-bullet;\n        li {\n          ul,\n          ol {\n            margin-#{$default-float}: $list-nested-margin;\n            margin-bottom: 0;\n            list-style: none;\n          }\n        }\n      }\n    }\n\n    /* Unordered Lists */\n    ul {\n      li {\n        ul,\n        ol {\n          margin-#{$default-float}: $list-nested-margin;\n          margin-bottom: 0;\n        }\n      }\n      &.square,\n      &.circle,\n      &.disc {\n        li ul { list-style: inherit; }\n      }\n\n      &.square { list-style-type: square; margin-#{$default-float}: $list-side-margin;}\n      &.circle { list-style-type: circle; margin-#{$default-float}: $list-side-margin;}\n      &.disc { list-style-type: disc; margin-#{$default-float}: $list-side-margin;}\n      &.no-bullet { list-style: none; }\n    }\n\n    /* Ordered Lists */\n    ol {\n      margin-#{$default-float}: $list-ordered-side-margin;\n      li {\n        ul,\n        ol {\n          margin-#{$default-float}: $list-nested-margin;\n          margin-bottom: 0;\n        }\n      }\n    }\n\n    /* Definition Lists */\n    dl {\n      dt {\n        margin-bottom: $definition-list-header-margin-bottom;\n        font-weight: $definition-list-header-weight;\n      }\n      dd { margin-bottom: $definition-list-margin-bottom; }\n    }\n\n    /* Abbreviations */\n    abbr,\n    acronym {\n      text-transform: uppercase;\n      font-size: 90%;\n      color: $body-font-color;\n      cursor: $cursor-help-value;\n    }\n    abbr {\n      text-transform: none;\n      &[title] {\n        border-bottom: $acronym-underline;\n      }\n    }\n\n    /* Blockquotes */\n    blockquote {\n      margin: 0 0 $paragraph-margin-bottom;\n      padding: $blockquote-padding;\n      border-#{$default-float}: $blockquote-border;\n\n      cite {\n        display: block;\n        font-size: $blockquote-cite-font-size;\n        color: $blockquote-cite-font-color;\n        &:before {\n          content: \"\\2014 \\0020\";\n        }\n\n        a,\n        a:visited {\n          color: $blockquote-cite-link-color;\n        }\n      }\n    }\n    blockquote,\n    blockquote p {\n      line-height: $paragraph-line-height;\n      color: $blockquote-font-color;\n    }\n\n    /* Microformats */\n    .vcard {\n      display: inline-block;\n      margin: $microformat-margin;\n      border: $microformat-border-width $microformat-border-style $microformat-border-color;\n      padding: $microformat-padding;\n\n      li {\n        margin: 0;\n        display: block;\n      }\n      .fn {\n        font-weight: $microformat-fullname-font-weight;\n        font-size: $microformat-fullname-font-size;\n      }\n    }\n\n    .vevent {\n      .summary { font-weight: $microformat-summary-font-weight; }\n\n      abbr {\n        cursor: $cursor-default-value;\n        text-decoration: $microformat-abbr-font-decoration;\n        font-weight: $microformat-abbr-font-weight;\n        border: none;\n        padding: $microformat-abbr-padding;\n      }\n    }\n\n\n    @media #{$medium-up} {\n      h1,h2,h3,h4,h5,h6 { line-height: $header-line-height; }\n      h1 { font-size: $h1-font-size; }\n      h2 { font-size: $h2-font-size; }\n      h3 { font-size: $h3-font-size; }\n      h4 { font-size: $h4-font-size; }\n      h5 { font-size: $h5-font-size; }\n      h6 { font-size: $h6-font-size; }\n    }\n\n    // Only include these styles if you want them.\n    @if $include-print-styles {\n      /*\n       * Print styles.\n       *\n       * Inlined to avoid required HTTP connection: www.phpied.com/delay-loading-your-print-css/\n       * Credit to Paul Irish and HTML5 Boilerplate (html5boilerplate.com)\n      */\n      .print-only { display: none !important; }\n      @media print {\n        * {\n          background: transparent !important;\n          color: $black !important; /* Black prints faster: h5bp.com/s */\n          box-shadow: none !important;\n          text-shadow: none !important;\n        }\n\n        a,\n        a:visited { text-decoration: underline;}\n        a[href]:after { content: \" (\" attr(href) \")\"; }\n\n        abbr[title]:after { content: \" (\" attr(title) \")\"; }\n\n        // Don't show links for images, or javascript/internal links\n        .ir a:after,\n        a[href^=\"javascript:\"]:after,\n        a[href^=\"#\"]:after { content: \"\"; }\n\n        pre,\n        blockquote {\n          border: 1px solid $aluminum;\n          page-break-inside: avoid;\n        }\n\n        thead { display: table-header-group; /* h5bp.com/t */ }\n\n        tr,\n        img { page-break-inside: avoid; }\n\n        img { max-width: 100% !important; }\n\n        @page { margin: 0.5cm; }\n\n        p,\n        h2,\n        h3 {\n          orphans: 3;\n          widows: 3;\n        }\n\n        h2,\n        h3 { page-break-after: avoid; }\n\n        .hide-on-print { display: none !important; }\n        .print-only { display: block !important; }\n        .hide-for-print { display: none !important; }\n        .show-for-print { display: inherit !important; }\n      }\n    }\n\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// Foundation Visibility Classes\n//\n$include-html-visibility-classes: $include-html-classes !default;\n$include-accessibility-classes: true !default;\n$include-table-visibility-classes: true !default;\n$include-legacy-visibility-classes: true !default;\n\n//\n// Media Class Names\n//\n// Visibility Breakpoints\n$visibility-breakpoint-sizes:\n  small,\n  medium,\n  large,\n  xlarge,\n  xxlarge;\n\n$visibility-breakpoint-queries:\n  unquote($small-up),\n  unquote($medium-up),\n  unquote($large-up),\n  unquote($xlarge-up),\n  unquote($xxlarge-up);\n\n@mixin visibility-loop {\n  @each $current-visibility-breakpoint in $visibility-breakpoint-sizes {\n    $visibility-inherit-list: ();\n    $visibility-none-list: ();\n\n    $visibility-visible-list: ();\n    $visibility-hidden-list: ();\n\n    $visibility-table-list: ();\n    $visibility-table-header-group-list: ();\n    $visibility-table-row-group-list: ();\n    $visibility-table-row-list: ();\n    $visibility-table-cell-list: ();\n\n    @each $visibility-comparison-breakpoint in $visibility-breakpoint-sizes {\n      @if index($visibility-breakpoint-sizes, $visibility-comparison-breakpoint) < index($visibility-breakpoint-sizes, $current-visibility-breakpoint) {\n        // Smaller than current breakpoint\n\n        $visibility-inherit-list: append($visibility-inherit-list, unquote(\n          '.hide-for-#{$visibility-comparison-breakpoint}-only, .show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-none-list: append($visibility-none-list, unquote(\n          '.show-for-#{$visibility-comparison-breakpoint}-only, .hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-visible-list: append($visibility-visible-list, unquote(\n          '.hidden-for-#{$visibility-comparison-breakpoint}-only, .visible-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-hidden-list: append($visibility-hidden-list, unquote(\n          '.visible-for-#{$visibility-comparison-breakpoint}-only, .hidden-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-list: append($visibility-table-list, unquote(\n          'table.hide-for-#{$visibility-comparison-breakpoint}-only, table.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n          'thead.hide-for-#{$visibility-comparison-breakpoint}-only, thead.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n          'tbody.hide-for-#{$visibility-comparison-breakpoint}-only, tbody.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-list: append($visibility-table-row-list, unquote(\n          'tr.hide-for-#{$visibility-comparison-breakpoint}-only, tr.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n          'th.hide-for-#{$visibility-comparison-breakpoint}-only, td.hide-for-#{$visibility-comparison-breakpoint}-only, th.show-for-#{$visibility-comparison-breakpoint}-up, td.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n\n        // Foundation 4 compatibility:\n        // Include .show/hide-for-[size] and .show/hide-for-[size]-down classes\n        // for small, medium, and large breakpoints only\n        @if $include-legacy-visibility-classes and index((small, medium, large), $visibility-comparison-breakpoint) != false {\n          $visibility-inherit-list: append($visibility-inherit-list, unquote(\n            '.hide-for-#{$visibility-comparison-breakpoint}, .hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-none-list: append($visibility-none-list, unquote(\n            '.show-for-#{$visibility-comparison-breakpoint}, .show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-visible-list: append($visibility-visible-list, unquote(\n            '.hidden-for-#{$visibility-comparison-breakpoint}, .hidden-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-hidden-list: append($visibility-hidden-list, unquote(\n            '.visible-for-#{$visibility-comparison-breakpoint}, .visible-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-list: append($visibility-table-list, unquote(\n            'table.hide-for-#{$visibility-comparison-breakpoint}, table.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n            'thead.hide-for-#{$visibility-comparison-breakpoint}, thead.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n            'tbody.hide-for-#{$visibility-comparison-breakpoint}, tbody.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-list: append($visibility-table-row-list, unquote(\n            'tr.hide-for-#{$visibility-comparison-breakpoint}, tr.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n            'th.hide-for-#{$visibility-comparison-breakpoint}, td.hide-for-#{$visibility-comparison-breakpoint}, th.hide-for-#{$visibility-comparison-breakpoint}-down, td.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n        }\n\n      } @else if index($visibility-breakpoint-sizes, $visibility-comparison-breakpoint) > index($visibility-breakpoint-sizes, $current-visibility-breakpoint) {\n        // Larger than current breakpoint\n\n        $visibility-inherit-list: append($visibility-inherit-list, unquote(\n          '.hide-for-#{$visibility-comparison-breakpoint}-only, .hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-none-list: append($visibility-none-list, unquote(\n          '.show-for-#{$visibility-comparison-breakpoint}-only, .show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-visible-list: append($visibility-visible-list, unquote(\n          '.hidden-for-#{$visibility-comparison-breakpoint}-only, .hidden-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-hidden-list: append($visibility-hidden-list, unquote(\n          '.visible-for-#{$visibility-comparison-breakpoint}-only, .visible-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-list: append($visibility-table-list, unquote(\n          'table.hide-for-#{$visibility-comparison-breakpoint}-only, table.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n          'thead.hide-for-#{$visibility-comparison-breakpoint}-only, thead.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n          'tbody.hide-for-#{$visibility-comparison-breakpoint}-only, tbody.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-list: append($visibility-table-row-list, unquote(\n          'tr.hide-for-#{$visibility-comparison-breakpoint}-only, tr.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n          'th.hide-for-#{$visibility-comparison-breakpoint}-only, td.hide-for-#{$visibility-comparison-breakpoint}-only, th.hide-for-#{$visibility-comparison-breakpoint}-up, td.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n\n        // Foundation 4 compatibility:\n        // Include .show/hide-for-[size] and .show/hide-for-[size]-down classes\n        // for small, medium, and large breakpoints only\n        @if $include-legacy-visibility-classes and index((small, medium, large), $visibility-comparison-breakpoint) != false {\n          $visibility-inherit-list: append($visibility-inherit-list, unquote(\n            '.hide-for-#{$visibility-comparison-breakpoint}, .show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-none-list: append($visibility-none-list, unquote(\n            '.show-for-#{$visibility-comparison-breakpoint}, .hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-visible-list: append($visibility-visible-list, unquote(\n            '.hidden-for-#{$visibility-comparison-breakpoint}, .visible-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-hidden-list: append($visibility-hidden-list, unquote(\n            '.visible-for-#{$visibility-comparison-breakpoint}, .hidden-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-list: append($visibility-table-list, unquote(\n            'table.hide-for-#{$visibility-comparison-breakpoint}, table.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n            'thead.hide-for-#{$visibility-comparison-breakpoint}, thead.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n            'tbody.hide-for-#{$visibility-comparison-breakpoint}, tbody.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-list: append($visibility-table-row-list, unquote(\n            'tr.hide-for-#{$visibility-comparison-breakpoint}, tr.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n            'th.hide-for-#{$visibility-comparison-breakpoint}, td.hide-for-#{$visibility-comparison-breakpoint}, th.show-for-#{$visibility-comparison-breakpoint}-down, td.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n        }\n\n      } @else {\n        // Current breakpoint\n\n        $visibility-inherit-list: append($visibility-inherit-list, unquote(\n          '.show-for-#{$visibility-comparison-breakpoint}-only, .show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-none-list: append($visibility-none-list, unquote(\n          '.hide-for-#{$visibility-comparison-breakpoint}-only, .hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-visible-list: append($visibility-visible-list, unquote(\n          '.visible-for-#{$visibility-comparison-breakpoint}-only, .visible-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-hidden-list: append($visibility-hidden-list, unquote(\n          '.hidden-for-#{$visibility-comparison-breakpoint}-only, .hidden-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-list: append($visibility-table-list, unquote(\n          'table.show-for-#{$visibility-comparison-breakpoint}-only, table.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n          'thead.show-for-#{$visibility-comparison-breakpoint}-only, thead.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n          'tbody.show-for-#{$visibility-comparison-breakpoint}-only, tbody.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-list: append($visibility-table-row-list, unquote(\n          'tr.show-for-#{$visibility-comparison-breakpoint}-only, tr.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n          'th.show-for-#{$visibility-comparison-breakpoint}-only, td.show-for-#{$visibility-comparison-breakpoint}-only, th.show-for-#{$visibility-comparison-breakpoint}-up, td.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n\n        // Foundation 4 compatibility:\n        // Include .show/hide-for-[size] and .show/hide-for-[size]-down classes\n        // for small, medium, and large breakpoints only\n        @if $include-legacy-visibility-classes and index((small, medium, large), $visibility-comparison-breakpoint) != false {\n          $visibility-inherit-list: append($visibility-inherit-list, unquote(\n            '.show-for-#{$visibility-comparison-breakpoint}, .show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-none-list: append($visibility-none-list, unquote(\n            '.hide-for-#{$visibility-comparison-breakpoint}, .hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-visible-list: append($visibility-visible-list, unquote(\n            '.visible-for-#{$visibility-comparison-breakpoint}, .visible-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-hidden-list: append($visibility-hidden-list, unquote(\n            '.hidden-for-#{$visibility-comparison-breakpoint}, .hidden-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-list: append($visibility-table-list, unquote(\n            'table.show-for-#{$visibility-comparison-breakpoint}, table.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n            'thead.show-for-#{$visibility-comparison-breakpoint}, thead.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n            'tbody.show-for-#{$visibility-comparison-breakpoint}, tbody.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-list: append($visibility-table-row-list, unquote(\n            'tr.show-for-#{$visibility-comparison-breakpoint}, tr.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n            'th.show-for-#{$visibility-comparison-breakpoint}, td.show-for-#{$visibility-comparison-breakpoint}, th.show-for-#{$visibility-comparison-breakpoint}-down, td.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n        }\n      }\n    }\n\n    /* #{$current-visibility-breakpoint} displays */\n    @media #{nth($visibility-breakpoint-queries, index($visibility-breakpoint-sizes, $current-visibility-breakpoint))} {\n      #{$visibility-inherit-list} {\n        display: inherit !important;\n      }\n      #{$visibility-none-list} {\n        display: none !important;\n      }\n      @if $include-accessibility-classes != false {\n        #{$visibility-visible-list} {\n          @include element-invisible-off;\n        }\n        #{$visibility-hidden-list} {\n          @include element-invisible;\n        }\n      }\n      @if $include-table-visibility-classes != false {\n        #{$visibility-table-list} {\n          display: table !important;\n        }\n        #{$visibility-table-header-group-list} {\n          display: table-header-group !important;\n        }\n        #{$visibility-table-row-group-list} {\n          display: table-row-group !important;\n        }\n        #{$visibility-table-row-list} {\n          display: table-row !important;\n        }\n        #{$visibility-table-cell-list} {\n          display: table-cell !important;\n        }\n      }\n    }\n  }\n}\n\n\n@if $include-html-visibility-classes != false {\n\n  @include visibility-loop;\n\n  /* Orientation targeting */\n  .show-for-landscape,\n  .hide-for-portrait { display: inherit !important; }\n  .hide-for-landscape,\n  .show-for-portrait { display: none !important; }\n\n  /* Specific visibility for tables */\n  table {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table !important; }\n  }\n  thead {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table-header-group !important; }\n  }\n  tbody {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table-row-group !important; }\n  }\n  tr {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table-row !important; }\n  }\n  td,\n  th {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table-cell !important; }\n  }\n\n  @media #{$landscape} {\n    .show-for-landscape,\n    .hide-for-portrait { display: inherit !important; }\n    .hide-for-landscape,\n    .show-for-portrait { display: none !important; }\n\n    /* Specific visibility for tables */\n    table {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table !important; }\n    }\n    thead {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table-header-group !important; }\n    }\n    tbody {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table-row-group !important; }\n    }\n    tr {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table-row !important; }\n    }\n    td,\n    th {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table-cell !important; }\n    }\n  }\n\n  @media #{$portrait} {\n    .show-for-portrait,\n    .hide-for-landscape { display: inherit !important; }\n    .hide-for-portrait,\n    .show-for-landscape { display: none !important; }\n\n    /* Specific visibility for tables */\n    table {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table !important; }\n    }\n    thead {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table-header-group !important; }\n    }\n    tbody {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table-row-group !important; }\n    }\n    tr {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table-row !important; }\n    }\n    td,\n    th {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table-cell !important; }\n    }\n  }\n\n  /* Touch-enabled device targeting */\n  .show-for-touch { display: none !important; }\n  .hide-for-touch { display: inherit !important; }\n  .touch .show-for-touch { display: inherit !important; }\n  .touch .hide-for-touch { display: none !important; }\n\n  /* Specific visibility for tables */\n  table.hide-for-touch { display: table !important; }\n  .touch table.show-for-touch { display: table !important; }\n  thead.hide-for-touch { display: table-header-group !important; }\n  .touch thead.show-for-touch { display: table-header-group !important; }\n  tbody.hide-for-touch { display: table-row-group !important; }\n  .touch tbody.show-for-touch { display: table-row-group !important; }\n  tr.hide-for-touch { display: table-row !important; }\n  .touch tr.show-for-touch { display: table-row !important; }\n  td.hide-for-touch { display: table-cell !important; }\n  .touch td.show-for-touch { display: table-cell !important; }\n  th.hide-for-touch { display: table-cell !important; }\n  .touch th.show-for-touch { display: table-cell !important; }\n\n\n  /* Print visibility */\n  @media print {\n    .show-for-print { display: block; }\n    .hide-for-print { display: none; }\n\n    table.show-for-print { display: table !important; }\n    thead.show-for-print { display: table-header-group !important; }\n    tbody.show-for-print { display: table-row-group !important; }\n    tr.show-for-print { display: table-row !important; }\n    td.show-for-print { display: table-cell !important; }\n    th.show-for-print { display: table-cell !important; }\n\n  }\n\n}\n","@charset \"utf-8\";\n/* TOC – Typography\n\nCheck typography variables › _3_typography_settings.scss\n\n- Links\n- Customize Foundation Typography\n- Headlines\n- Images\n- Lists\n- Tables\n- Code\n- Quotes\n- Typography for Articles\n- Smaller Fontsize for Bigteaser on small devices\n- Additional typographical elements\n- Footnotes\n- Icon Font\n\n*/\n\n\n\n/* Links\n------------------------------------------------------------------- */\n\na,\na:link {\n    transition: all .4s;\n    color: $link-unvisited;\n}\n\na:visited {\n    border-bottom: $grey-2;\n    color: $link-visited;\n}\n\na:hover {\n    color: $link-hover;\n}\n\na:focus {\n    color: $link-focus;\n}\n\na:active {\n    color: $link-active;\n}\n\n\n\n/* Customize Foundation Typography\n------------------------------------------------------------------- */\n\np {\n    -webkit-hyphens: auto;\n    -moz-hyphens: auto;\n    -ms-hyphens: auto;\n    hyphens: auto;\n    -ms-word-break: normal;\n    /* Non standard for webkit */\n    word-break: normal;\n}\np a,\narticle a {\n    font-weight: bold;\n    border-bottom: 1px dotted;\n}\np a:hover,\narticle a:hover {\n    border-bottom: 2px solid;\n}\np a.button,\n.button,\n.button:hover {\n    border: 0;\n    color: #fff;\n}\np.button a {\n    border: 0;\n    color: #fff;\n    text-shadow: 0 1px 3px rgba(0, 0, 0, 0.5);\n}\n\n\n\n/* Headlines\n   The hK::before logic is to accomodate a vert. offset for persistent\n   top of page menu. The logic is copied from\n   https://css-tricks.com/hash-tag-links-padding/\n------------------------------------------------------------------- */\n\nh1, h2, h3, h4, h5, h6 {\n    font-family: $header-font-family;\n    font-weight: normal;\n    padding: 0;\n}\nh1 {\n    font-size: $font-size-h1;\n    margin-top: 0;\n}\nh2 {\n    font-size: $font-size-h2;\n    margin: 1.563em 0 0 0;\n}\n    .blog-index h2 {\n        margin-top: 0;\n    }\nh3 {\n    font-size: $font-size-h3;\n    margin: 1.152em 0 0 0;\n}\nh4 {\n    font-size: $font-size-h4;\n    margin: 1.152em 0 0 0;\n}\nh5 {\n    font-size: $font-size-h5;\n    margin: 1em 0 0 0;\n}\n\n\n\n/* Images\n------------------------------------------------------------------- */\n\nimg { border-radius: $global-radius;}\n    img.alignleft,\n    img.left        { float: left; margin:5px 15px 5px 0; }\n    img.alignright,\n    img.right       { float: right; margin:5px 0 5px 15px; }\n    img.aligncenter,\n    img.center      { display: block; margin:0 auto 10px; }\n\nfigure {\n    margin: 0 0 rem-calc(30) 0;\n}\n#masthead-with-background-color figure,\n#masthead-with-pattern figure {\n    margin: 0;\n}\nfigcaption,\n.masthead-caption {\n    color: $grey-10;\n    font-family: $font-family-sans-serif;\n    font-size: rem-calc(13);\n    padding-top: rem-calc(2);\n}\nfigcaption a,\n.masthead-caption a {\n    border-bottom: 1px dotted $grey-4;\n    color: $grey-10;\n}\nfigcaption a:hover,\n.masthead-caption a:hover {\n    border-bottom: 2px solid $primary-color;\n    color: $primary-color;\n}\n.masthead-caption {\n    padding-right: 10px;\n    text-align: right;\n}\n\n\n\n/* Tables\n------------------------------------------------------------------- */\n\ntd {\n    vertical-align: top;\n}\n\n\n\n/* Code\n------------------------------------------------------------------- */\n\npre {\n    overflow: auto;\n    margin-bottom: rem-calc(20);\n    padding: 5px;\n    background-color: $code-background-color;\n    border-radius: $global-radius;\n}\npre code {\n    padding: rem-calc(2) rem-calc(5) rem-calc(1) rem-calc(0);\n    border: 0;\n}\n\ncode {\n    font-size: rem-calc(14);\n    line-height: 1.5;\n}\n\n\n\n/* Lists\n------------------------------------------------------------------- */\n\nul, ol {\n    margin-left: 20px;\n    padding: 0;\n}\nli {\n    margin-left: 0;\n}\n\n.no-bullet {\n    list-style: none;\n    margin-left: 0;\n}\n\nli {\n    > ul,\n    > ol {\n         margin-bottom: 0;\n    }\n}\n\ndl {\n\n}\ndt:first-child {\n    padding-top: 0px;\n}\ndt {\n    font-weight: bold;\n    padding-top: 30px;\n}\ndd {\n}\narticle dl dt   { line-height: 1.3; }\narticle dl dd   { line-height: 1.6; margin-bottom: rem-calc(12); margin-left: rem-calc(24); }\n\n\n\n/* Quotes\n------------------------------------------------------------------- */\n\nblockquote {\n    font-style: italic;\n    position: relative;\n    border: none;\n    margin: 0 30px 30px 30px;\n    color:  $grey-11;\n}\n\n    blockquote p {font-style: italic; color: $grey-10; }\n\n    blockquote:before {\n        display:block;content:\"\\00BB\";\n        font-size:80px;\n        line-height: 0;\n        position:absolute;\n        left:-25px;\n        top: auto;\n        color: $grey-11;\n    }\n    blockquote:after {\n        display:block;\n        content:\"\\00AB\";\n        font-size:80px;\n        line-height: 0;\n        position:absolute;\n        right:-10px;\n        bottom: 20px;\n        color: $grey-11;\n    }\n    blockquote cite:before {\n        content:\"\\2014 \\0020\"\n    }\n    blockquote cite a,blockquote cite a:visited {\n        color: $grey-10;\n    }\ncite {\n    padding-top: 5px;\n}\n\nbutton, .button {\n    letter-spacing: 1px;\n}\n\nmark {\n    background-color: scale-color($warning-color, $lightness: 60%);\n}\n\n\n\n/* Typography for Articles\n------------------------------------------------------------------- */\n\n.subheadline {\n    font-size: rem-calc(16);\n    margin: 0;\n    text-transform: uppercase;\n}\n.teaser {\n    font-size: rem-calc(20);\n}\n.big-teaser {\n    font-style: italic; font-weight: 300;\n}\n.big-teaser a {\n    font-style: italic; font-weight: 400;\n}\n\n/* Smaller Fontsize for Bigteaser on small devices */\n@media only screen {\n    .big-teaser {\n        font-size: rem-calc(20);\n    }\n}\n@media only screen and (min-width: 40.063em) {\n    .big-teaser         {\n        font-size: rem-calc(29);\n    }\n}\n\n\n\n/* Additional typographical elements\n------------------------------------------------------------------- */\n\n.sans           { font-family: $font-family-sans-serif; }\n.serif          { font-family: $font-family-serif; }\n\n.font-size-h1   { font-size: $font-size-h1; }\n.font-size-h2   { font-size: $font-size-h2; }\n.font-size-h3   { font-size: $font-size-h3; }\n.font-size-h4   { font-size: $font-size-h4; }\n.font-size-h5   { font-size: $font-size-h5; }\n.font-size-p    { font-size: $font-size-p; }\n\n\n\n/* Footnotes\n------------------------------------------------------------------- */\n\n.footnotes:before {\n    content: \"\";\n    position: absolute;\n    height: 1px;\n    width: 60px;\n    margin-top: -10px;\n    border-bottom: 1px solid $grey-2;\n}\n.footnotes {\n    margin-top: 60px;\n}\n.footnotes ol {\n    font-size: $font-size-small;\n}\n.footnotes p {\n    font-size: inherit;\n    margin-bottom: 0;\n}\n\n\n\n\n/* Icon Font\n   See the icon-set/preview in /assets/fonts/iconfont-preview.html\n------------------------------------------------------------------- */\n\n@font-face {\n  font-family: 'iconfont';\n  src: url('../fonts/iconfont.eot'); /* IE9 Compat Modes */\n  src: url('../fonts/iconfont.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */\n       url('../fonts/iconfont.woff') format('woff'), /* Pretty Modern Browsers */\n       url('../fonts/iconfont.ttf')  format('truetype'), /* Safari, Android, iOS */\n       url('../fonts/iconfont.svg#svgFontName') format('svg'); /* Legacy iOS */\n}\n\n.iconfont       { font-family: iconfont; }\n.iconfont-48    { font-size: 48px; }\n\n\n[data-icon]:before { content: attr(data-icon); }\n\n[data-icon]:before,\n.icon-archive:before,\n.icon-browser:before,\n.icon-calendar:before,\n.icon-camera:before,\n.icon-chat:before,\n.icon-check:before,\n.icon-chevron-down:before,\n.icon-chevron-left:before,\n.icon-chevron-right:before,\n.icon-chevron-up:before,\n.icon-circle-with-cross:before,\n.icon-circle-with-minus:before,\n.icon-circle-with-plus:before,\n.icon-cloud:before,\n.icon-code:before,\n.icon-cog:before,\n.icon-dropbox:before,\n.icon-edit:before,\n.icon-export:before,\n.icon-eye:before,\n.icon-facebook:before,\n.icon-feather:before,\n.icon-github:before,\n.icon-globe:before,\n.icon-googleplus:before,\n.icon-heart:before,\n.icon-heart-outlined:before,\n.icon-home:before,\n.icon-instagram:before,\n.icon-lab-flask:before,\n.icon-leaf:before,\n.icon-linkedin:before,\n.icon-mail:before,\n.icon-message:before,\n.icon-mic:before,\n.icon-network:before,\n.icon-paper-plane:before,\n.icon-pinterest:before,\n.icon-price-tag:before,\n.icon-rocket:before,\n.icon-rss:before,\n.icon-soundcloud:before,\n.icon-star:before,\n.icon-star-outlined:before,\n.icon-thumbs-down:before,\n.icon-thumbs-up:before,\n.icon-tree:before,\n.icon-tumblr:before,\n.icon-twitter:before,\n.icon-upload-to-cloud:before,\n.icon-video:before,\n.icon-vimeo:before,\n.icon-warning:before,\n.icon-xing:before,\n.icon-youtube:before {\n  display: inline-block;\nfont-family: \"iconfont\";\nfont-style: normal;\nfont-weight: normal;\nfont-variant: normal;\nline-height: 1;\ntext-decoration: inherit;\ntext-rendering: optimizeLegibility;\ntext-transform: none;\n-moz-osx-font-smoothing: grayscale;\n-webkit-font-smoothing: antialiased;\nfont-smoothing: antialiased;\n}\n\n.icon-archive:before { content: \"\\f100\"; }\n.icon-browser:before { content: \"\\f101\"; }\n.icon-calendar:before { content: \"\\f133\"; }\n.icon-camera:before { content: \"\\f102\"; }\n.icon-chat:before { content: \"\\f103\"; }\n.icon-check:before { content: \"\\f104\"; }\n.icon-chevron-down:before { content: \"\\f105\"; }\n.icon-chevron-left:before { content: \"\\f106\"; }\n.icon-chevron-right:before { content: \"\\f107\"; }\n.icon-chevron-up:before { content: \"\\f108\"; }\n.icon-circle-with-cross:before { content: \"\\f109\"; }\n.icon-circle-with-minus:before { content: \"\\f10a\"; }\n.icon-circle-with-plus:before { content: \"\\f10b\"; }\n.icon-cloud:before { content: \"\\f10c\"; }\n.icon-code:before { content: \"\\f10d\"; }\n.icon-cog:before { content: \"\\f10e\"; }\n.icon-dropbox:before { content: \"\\f10f\"; }\n.icon-edit:before { content: \"\\f110\"; }\n.icon-export:before { content: \"\\f111\"; }\n.icon-eye:before { content: \"\\f112\"; }\n.icon-facebook:before { content: \"\\f113\"; }\n.icon-feather:before { content: \"\\f114\"; }\n.icon-github:before { content: \"\\f115\"; }\n.icon-globe:before { content: \"\\f116\"; }\n.icon-googleplus:before { content: \"\\f136\"; }\n.icon-heart:before { content: \"\\f117\"; }\n.icon-heart-outlined:before { content: \"\\f118\"; }\n.icon-home:before { content: \"\\f119\"; }\n.icon-instagram:before { content: \"\\f11a\"; }\n.icon-lab-flask:before { content: \"\\f11b\"; }\n.icon-leaf:before { content: \"\\f11c\"; }\n.icon-linkedin:before { content: \"\\f11d\"; }\n.icon-mail:before { content: \"\\f11e\"; }\n.icon-message:before { content: \"\\f11f\"; }\n.icon-mic:before { content: \"\\f120\"; }\n.icon-network:before { content: \"\\f121\"; }\n.icon-paper-plane:before { content: \"\\f122\"; }\n.icon-pinterest:before { content: \"\\f123\"; }\n.icon-price-tag:before { content: \"\\f124\"; }\n.icon-rocket:before { content: \"\\f125\"; }\n.icon-rss:before { content: \"\\f126\"; }\n.icon-soundcloud:before { content: \"\\f127\"; }\n.icon-star:before { content: \"\\f128\"; }\n.icon-star-outlined:before { content: \"\\f129\"; }\n.icon-thumbs-down:before { content: \"\\f12a\"; }\n.icon-thumbs-up:before { content: \"\\f12b\"; }\n.icon-tree:before { content: \"\\f134\"; }\n.icon-tumblr:before { content: \"\\f12c\"; }\n.icon-twitter:before { content: \"\\f12d\"; }\n.icon-upload-to-cloud:before { content: \"\\f12e\"; }\n.icon-video:before { content: \"\\f12f\"; }\n.icon-vimeo:before { content: \"\\f130\"; }\n.icon-warning:before { content: \"\\f131\"; }\n.icon-xing:before { content: \"\\f135\"; }\n.icon-youtube:before { content: \"\\f132\"; }\n","@charset \"utf-8\";\n/* TOC\n\n- Adjustments: Video Layout\n- Navigation\n- Search\n- Masthead\n- Masthead › small-only\n- Masthead › medium-only\n- Masthead › large-only\n- Masthead › xlarge-up\n- Breadcrumb\n- Meta\n- Jump to top\n- Footer\n- Subfooter\n- CSS-Classes to add margin at top or bottom\n\n*/\n\n\n\n/* Adjustments: Video Layout\n------------------------------------------------------------------- */\n\nbody.video,\nbody.video #masthead-no-image-header { background: #000; }\nbody.video #masthead-no-image-header { margin-bottom: 60px; }\nbody.video h1,\nbody.video h2,\nbody.video h3,\nbody.video h4,\nbody.video h5,\nbody.video h6,\nbody.video p,\nbody.video a,\nbody.video blockquote:before,\nbody.video blockquote:after,\nbody.video cite a, { color: #fff; }\nbody.video cite a:visited, { color: #fff; }\nbody.video cite { color: #fff; }\n\n\n\n/* Navigation\n------------------------------------------------------------------- */\n\n#navigation {\n    -webkit-box-shadow: 0 2px 2px 0 rgba(0,0,0,.2);\n    box-shadow: 0 2px 3px 0 rgba(0,0,0,.2);\n\n    [class^='icon-']:before, [class*=' icon-']:before {\n        margin-right: rem-calc(8);\n    }\n}\n\n\n\n/* Search\n------------------------------------------------------------------- */\n\n.no-js form#search {\n  display: none;\n}\n\n\n\n/* Masthead\n------------------------------------------------------------------- */\n\n#masthead {\n    background-color: $primary-color;\n}\n#masthead-no-image-header {\n    background-color: $primary-color;\n}\n#masthead-with-text {\n    text-align: center;\n    font-size: rem-calc(54);\n    font-family: $header-font-family;\n    color: #fff;\n    text-transform: uppercase;\n    text-shadow: 0 2px 3px rgba(0,0,0,.4);\n}\n#masthead-no-image-header {\n    height: 100px;\n    background-color: rgba(63,175,70,1);\n}\n#masthead-no-image-header #logo img {\n    margin-top: 10px;\n}\n\n// Made height/margin-top smaller for what wanted and half on small screen.\n\n/* Masthead › small-only\n------------------------------------------------------------------- */\n\n// Wanted to keep logo even on small screen so disable.\n@media #{$small-only} {\n    // #logo img {\n        // display: none;\n    // }\n    #logo img {\n        margin-top: 30px;\n    }\n    #masthead {\n        height: 100px;\n    }\n    #masthead-with-pattern {\n        padding: 15px 0;\n    }\n    #masthead-with-background-color {\n        padding: 15px 0;\n    }\n    #masthead-with-text {\n        height: 220px;\n        padding: 30px 0;\n        font-size: rem-calc(36);\n    }\n    // #masthead-no-image-header {\n    //     display: none;\n    // }\n    #masthead-no-image-header #logo img {\n        margin-top: 35px;\n    }\n}\n\n\n/* Masthead › medium-only\n------------------------------------------------------------------- */\n\n@media #{$medium-only} {\n    #logo img {\n        margin-top: 60px;\n    }\n    #masthead {\n        height: 200px;\n    }\n    #masthead-with-pattern {\n        padding: 20px 0;\n    }\n    #masthead-with-background-color {\n        padding: 20px 0;\n    }\n    #masthead-with-text {\n        padding: 60px 0;\n        height: 300px;\n    }\n    #masthead-no-image-header #logo img {\n        margin-top: 20px;\n    }\n}\n\n\n/* Masthead › large-only\n------------------------------------------------------------------- */\n\n@media #{$large-only} {\n    #logo img {\n        margin-top: 60px;\n    }\n    #masthead {\n        height: 200px;\n    }\n    #masthead-with-pattern {\n        padding: 30px 0;\n    }\n    #masthead-with-background-color {\n        padding: 30px 0;\n    }\n    #masthead-with-text {\n        height: 330px;\n        padding: 60px 0;\n    }\n}\n\n\n/* Masthead › xlarge-up\n------------------------------------------------------------------- */\n\n@media #{$xlarge-up} {\n    #logo img {\n        margin-top: 60px;\n    }\n    #masthead {\n        height: 200px;\n    }\n    #masthead-with-pattern {\n        padding: 45px 0;\n    }\n    #masthead-with-background-color {\n        padding: 45px 0;\n    }\n    #masthead-with-text {\n        padding: 95px 0;\n        height: 400px;\n    }\n}\n\n\n#title-image-small {\n    height: 240px;\n}\n#title-image-large {\n    height: 520px;\n}\n#title-image-index-small {\n    height: 120px;\n}\n#title-image-index-large {\n    height: 260px;\n}\n\n\n\n/* Breadcrumb\n------------------------------------------------------------------- */\n\n#breadcrumb {\n    background: scale-color($grey-1, $lightness: 55%);\n    border-top: 1px solid scale-color($grey-1, $lightness: 45%);\n    border-bottom: 1px solid scale-color($grey-1, $lightness: 45%);\n}\n.breadcrumbs>.current {\n  font-weight: bold;\n}\n\n\n/* Meta\n------------------------------------------------------------------- */\n\n#page-meta, #page-meta a {\n    color: $grey-5;\n}\n\n#page-meta .button {\n    background: $grey-5;\n    border: 0;\n}\n#page-meta .button {\n    color: #fff;\n}\n#page-meta .button:hover {\n    background: $primary-color;\n}\n.meta-info p {\n  font-size: rem-calc(13);\n  color: scale-color($grey-1, $lightness: 40%);\n}\n  .meta-info a {\n    text-decoration: underline;\n    color: scale-color($grey-1, $lightness: 40%);\n  }\n  .meta-info a:hover {\n    text-decoration: none;\n    color: $secondary-color;\n  }\n\n\n\n/* Jump to top\n------------------------------------------------------------------- */\n\n#up-to-top {\n    padding: 30px 0 10px 0;\n}\n#up-to-top a {\n    font-size: 24px;\n    padding: 5px;\n    border-radius: 3px;\n}\n#up-to-top a:hover {\n    background: $grey-2;\n}\n\n\n\n/* Footer\n------------------------------------------------------------------- */\n\n#footer-content p,\n#footer-content li {\n    font-size: rem-calc(13);\n    font-weight: 300;\n}\n\n#footer {\n    padding-top: 30px;\n    padding-bottom: 20px;\n    background: $footer-bg;\n    color: $footer-color;\n    }\n\n    #footer a {\n        color: $footer-link-color;\n    }\n    #footer h4,\n    #footer h5 {\n        letter-spacing: 1px;\n        color: #fff;\n        text-transform: uppercase;\n    }\n\n\n\n/* Subfooter\n------------------------------------------------------------------- */\n\n#subfooter {\n    background: $subfooter-bg;\n    color: $subfooter-color;\n    padding-top: 30px;\n}\n\n#subfooter-left ul.inline-list {\n    float: left;\n}\n\n.credits a {\n    color: $subfooter-link-color;\n    border: 0;\n    text-transform: uppercase;\n    &:hover {\n        color: #fff;\n  }\n}\n\n.social-icons {\n    margin-bottom: 10px !important;\n\n// Beware of SCSS-Syntax here\n  li {\n    padding: 0 0 20px 0;\n  }\n  a {\n    font-size: rem-calc(23);\n    display: block;\n    width: 36px;\n    border-radius: 50%;\n    color: $subfooter-bg;\n    background: $subfooter-color;\n    text-align: center;\n    &:hover {\n      background: $subfooter-bg;\n      color: #fff;\n    }\n  }\n}\n\n\n\n/* CSS-Classes to add margin at top or bottom\n------------------------------------------------------------------- */\n\n.t10 { margin-top: 10px !important; }\n.t15 { margin-top: 15px !important; }\n.t20 { margin-top: 20px !important; }\n.t30 { margin-top: 30px !important; }\n.t50 { margin-top: 50px !important; }\n.t60 { margin-top: 60px !important; }\n.t70 { margin-top: 70px !important; }\n.t80 { margin-top: 80px !important; }\n.t90 { margin-top: 90px !important; }\n\n.b15 { margin-bottom: 15px !important; }\n.b20 { margin-bottom: 20px !important; }\n.b30 { margin-bottom: 30px !important; }\n.b60 { margin-bottom: 60px !important; }\n\n.l15 { margin-left: 15px !important; }\n.r15 { margin-right: 15px !important; }\n\n.pl20 { padding-left: 20px !important; }\n.pr5  { padding-right: 5px !important; }\n.pr10 { padding-right: 10px !important; }\n.pr20 { padding-right: 20px !important; }\n","@charset \"utf-8\";\n/* TOC\n\n- Table of Contents (Index)\n- Panel\n- Shadows\n- Alerts\n- Breadcrumb\n- Button\n- Side-Nav\n- Accordion\n- Lazy Load XT\n- Frontpage Widget\n\n*/\n\n\n\n/* Table of Contents (Index)\n------------------------------------------------------------------- */\n\n#toc ul,\n#toc ul ul,\n#toc ul ul ul, {\n    list-style: none;\n    margin-left: 30px;\n}\n#toc ul {\n    margin-left: 0;\n    margin-top: $spacing-unit;\n}\n\n\n\n/* Panel\n------------------------------------------------------------------- */\n\n.border-dotted {\n  border: 1px dotted $grey-5;\n  padding: rem-calc(20);\n  border-radius: $global-radius;\n}\n\n\n\n/* Shadows\n------------------------------------------------------------------- */\n\n.shadow-no      {text-shadow: rgba(0, 0, 0, 0) 0 0 0;}\n.shadow-black   {text-shadow: rgba(0, 0, 0, 0.498039) 0px 1px 2px;}\n.shadow-white   {text-shadow: rgba(255, 255, 255, 0.498039) 0px 1px 2px;}\n\n\n\n/* Alerts\n------------------------------------------------------------------- */\n\n.alert-box {\n  font-family: $font-family-sans-serif;\n  text-shadow: 0px 1px 1px rgba(0,0,0,0.9);\n}\n  .alert-box p {\n    margin-bottom: 0;\n  }\n  .alert-box a {\n    text-shadow: 1px 1px 0px rgba(0, 0, 0, 1);\n    color: #fff;\n    border-bottom: 1px dotted #fff;\n  }\n  .alert-box a:hover {\n    border-bottom: 1px solid #fff;\n  }\n  .alert-box.terminal {\n    background: $grey-12; \n    color: #fff; \n    border-color: scale-color($grey-12, $lightness: -14%);\n    font-family: $font-family-monospace;\n  }\n  .alert-box.terminal::before {\n    content: \"$ \";\n    color: $ci-6;\n    float: left;\n    margin: .25em .5em 0 0;\n  }\n  .alert-box.text {\n    background-color: $grey-2;\n    text-shadow: 0px 0px 0px rgba(0,0,0,0.9);\n    border-color: scale-color($grey-2, $lightness: -14%);\n    color: $grey-12;\n  }\n\n\n\n/* Button\n------------------------------------------------------------------- */\n\nbutton, .button         { letter-spacing: 1px; }\n  button.grey, .button.grey { background: $grey-10; }\n  button.grey:hover,\n  button.grey:focus,\n  .button.grey:hover,\n  .button.grey:focus      { background-color: $grey-16; }\n\n\n\n/* Side-Nav\n------------------------------------------------------------------- */\n\n.side-nav li.title { text-transform: uppercase;}\n.side-nav li { border-top: 1px solid $grey-3;}\n.side-nav li a:not(.button) { border-bottom: 0; padding: 0.4375rem 0rem; }\n.side-nav li a:not(.button):hover, .side-nav li a:not(.button):focus { background: $grey-1; }\n\n.homepage p { margin: 0; padding: 0; color: $grey-10; }\n\n\n\n/* Accordion\n------------------------------------------------------------------- */\n\ndl.accordion  { border-top: 1px solid $grey-2;  }\n.accordion dd   { border-bottom: 1px solid $grey-2;  }\ndd.accordion-navigation span { padding-right: 12px; }\ndd.accordion-navigation span:before { content: \"\\F107\" }\ndd.accordion-navigation.active span:before { content: \"\\F105\" }\ndd.accordion-navigation.active span:before { content: \"\\F105\" }\n\n\n\n/* Lazy Load XT\n------------------------------------------------------------------- */\n\n/*! Lazy Load XT v1.0.6 2014-11-19\n * http://ressio.github.io/lazy-load-xt\n * (C) 2014 RESS.io\n * Licensed under MIT */\nimg.lazy {\n  display: none;\n}\n.lazy-hidden {\n    opacity: 0;\n}\n.lazy-loaded {\n    -webkit-transition: opacity 0.7s;\n    -moz-transition: opacity 0.7s;\n    -ms-transition: opacity 0.7s;\n    -o-transition: opacity 0.7s;\n    transition: opacity 0.7s;\n    opacity: 1;\n}\n\n*:target:not([id^='fn:']):not([id^='fnref:']) {\n  &::before {\n    content: \" \";\n    width: 0;\n    height: 0;\n\n    display: block;\n    padding-top: 50px;\n    margin-top: -50px;\n  }\n}\n","@charset \"utf-8\";\n/* Syntax highlighting styles\n------------------------------------------------------------------- */\n\n.highlight {\n    background: #fff;\n    [data-lang]::before {\n    content: attr(data-lang);\n    display: block;\n    text-align: right;\n    margin-right: 5px;\n    text-transform: uppercase;\n    }\n    .c     { color: #998; font-style: italic } // Comment\n    .err   { color: #a61717; background-color: #e3d2d2 } // Error\n    .k     { font-weight: bold } // Keyword\n    .o     { font-weight: bold } // Operator\n    .cm    { color: #998; font-style: italic } // Comment.Multiline\n    .cp    { color: #999; font-weight: bold } // Comment.Preproc\n    .c1    { color: #998; font-style: italic } // Comment.Single\n    .cs    { color: #999; font-weight: bold; font-style: italic } // Comment.Special\n    .gd    { color: #000; background-color: #fdd } // Generic.Deleted\n    .gd .x { color: #000; background-color: #faa } // Generic.Deleted.Specific\n    .ge    { font-style: italic } // Generic.Emph\n    .gr    { color: #a00 } // Generic.Error\n    .gh    { color: #999 } // Generic.Heading\n    .gi    { color: #000; background-color: #dfd } // Generic.Inserted\n    .gi .x { color: #000; background-color: #afa } // Generic.Inserted.Specific\n    .go    { color: #888 } // Generic.Output\n    .gp    { color: #555 } // Generic.Prompt\n    .gs    { font-weight: bold } // Generic.Strong\n    .gu    { color: #aaa } // Generic.Subheading\n    .gt    { color: #a00 } // Generic.Traceback\n    .kc    { font-weight: bold } // Keyword.Constant\n    .kd    { font-weight: bold } // Keyword.Declaration\n    .kp    { font-weight: bold } // Keyword.Pseudo\n    .kr    { font-weight: bold } // Keyword.Reserved\n    .kt    { color: #458; font-weight: bold } // Keyword.Type\n    .m     { color: #099 } // Literal.Number\n    .s     { color: #d14 } // Literal.String\n    .na    { color: #008080 } // Name.Attribute\n    .nb    { color: #0086B3 } // Name.Builtin\n    .nc    { color: #458; font-weight: bold } // Name.Class\n    .no    { color: #008080 } // Name.Constant\n    .ni    { color: #800080 } // Name.Entity\n    .ne    { color: #900; font-weight: bold } // Name.Exception\n    .nf    { color: #900; font-weight: bold } // Name.Function\n    .nn    { color: #555 } // Name.Namespace\n    .nt    { color: #000080 } // Name.Tag\n    .nv    { color: #008080 } // Name.Variable\n    .ow    { font-weight: bold } // Operator.Word\n    .w     { color: #bbb } // Text.Whitespace\n    .mf    { color: #099 } // Literal.Number.Float\n    .mh    { color: #099 } // Literal.Number.Hex\n    .mi    { color: #099 } // Literal.Number.Integer\n    .mo    { color: #099 } // Literal.Number.Oct\n    .sb    { color: #d14 } // Literal.String.Backtick\n    .sc    { color: #d14 } // Literal.String.Char\n    .sd    { color: #d14 } // Literal.String.Doc\n    .s2    { color: #d14 } // Literal.String.Double\n    .se    { color: #d14 } // Literal.String.Escape\n    .sh    { color: #d14 } // Literal.String.Heredoc\n    .si    { color: #d14 } // Literal.String.Interpol\n    .sx    { color: #d14 } // Literal.String.Other\n    .sr    { color: #009926 } // Literal.String.Regex\n    .s1    { color: #d14 } // Literal.String.Single\n    .ss    { color: #990073 } // Literal.String.Symbol\n    .bp    { color: #999 } // Name.Builtin.Pseudo\n    .vc    { color: #008080 } // Name.Variable.Class\n    .vg    { color: #008080 } // Name.Variable.Global\n    .vi    { color: #008080 } // Name.Variable.Instance\n    .il    { color: #099 } // Literal.Number.Integer.Long\n}\n"],"file":"styles_feeling_responsive.css"}
\ No newline at end of file
+{"version":3,"sourceRoot":"","sources":["../../_sass/_02_settings_typography.scss","../../_sass/_03_settings_mixins_media_queries.scss","../../_sass/_01_settings_colors.scss","../../_sass/_05_normalize.scss","../../_sass/foundation-components/_grid.scss","../../_sass/foundation-components/_global.scss","../../_sass/foundation-components/_buttons.scss","../../_sass/_04_settings_global.scss","../../_sass/foundation-components/_forms.scss","../../_sass/foundation-components/_top-bar.scss","../../_sass/foundation-components/_accordion.scss","../../_sass/foundation-components/_alert-boxes.scss","../../_sass/foundation-components/_breadcrumbs.scss","../../_sass/foundation-components/_block-grid.scss","../../_sass/foundation-components/_button-groups.scss","../../_sass/foundation-components/_clearing.scss","../../_sass/foundation-components/_dropdown.scss","../../_sass/foundation-components/_dropdown-buttons.scss","../../_sass/foundation-components/_flex-video.scss","../../_sass/foundation-components/_inline-lists.scss","../../_sass/foundation-components/_keystrokes.scss","../../_sass/foundation-components/_panels.scss","../../_sass/foundation-components/_reveal.scss","../../_sass/foundation-components/_side-nav.scss","../../_sass/foundation-components/_sub-nav.scss","../../_sass/foundation-components/_tables.scss","../../_sass/foundation-components/_thumbs.scss","../../_sass/foundation-components/_type.scss","../../_sass/foundation-components/_visibility.scss","../../_sass/_06_typography.scss","../../_sass/_07_layout.scss","../../_sass/_09_elements.scss","../../_sass/_11_syntax-highlighting.scss"],"names":[],"mappings":"CAuDA,wBAPoB,QAQpB,wBAPoB,QAQpB,wBAPoB,QAQpB,wBAPoB,OAQpB,wBAPoB,QC8RlB,wBACE,sBAGF,yBACE,4BACA,UAGF,8BACE,kDACA,UAGF,0BACE,qDACA,eAGF,+BACE,0EACA,eAGF,yBACE,qDACA,eAGF,8BACE,0EACA,eAGF,0BACE,qDACA,eAGF,+BACE,2EACA,eAGF,2BACE,sDACA,gBAGF,yCACE,kBAMA,UAEE,YAIF,mBA3TF,mBA8TwB,WA7TxB,gBA6TwB,WA5TxB,WA4TwB,WAGtB,UAEE,UDtYW,KC0Yb,KACE,WCzYgB,QD0YhB,MC5YgB,KD6YhB,UACA,SACA,YDzYmB,mDC0YnB,YDrYa,OCsYb,WDrYY,OCsYZ,YD/Ya,ICgZb,kBACA,OAlGc,KAqGhB,QACE,OAnGiB,QAuGnB,IACE,eACA,YAGF,IACE,+BAMA,0GAGE,0BAKJ,MACE,sBAGF,OACE,uBA/QJ,iCAEE,YACA,cAGF,gBACE,WAgRA,MACE,wBACA,kBAIF,WACE,kBAOF,aACE,mCACA,kCAIF,IACE,qBACA,sBAQF,SACE,YACA,gBAIF,OACE,WEnfN,4DAQA,KACE,uBACA,0BACA,8BAOF,KACE,SAaF,2FAaE,cAQF,4BAIE,qBACA,wBAQF,sBACE,aACA,SAQF,kBAEE,aAUF,EACE,+BAOF,iBAEE,UAUF,YACE,yBAOF,SAEE,iBAOF,IACE,kBAQF,GACE,cACA,eAOF,KACE,gBACA,WAOF,MACE,cAOF,QAEE,cACA,cACA,kBACA,wBAGF,IACE,WAGF,IACE,eAUF,IACE,SAOF,eACE,gBAUF,OACE,gBAOF,GACE,4BACA,uBACA,SAOF,IACE,cAOF,kBAIE,gCACA,cAkBF,sCAKE,cACA,aACA,SAOF,OACE,iBAUF,cAEE,oBAWF,oEAIE,0BACA,eAOF,sCAEE,eAOF,iDAEE,SACA,UAQF,MACE,mBAWF,uCAEE,sBACA,UASF,4FAEE,YASF,mBACE,6BACA,4BACA,+BACA,uBASF,+FAEE,wBAOF,SACE,wBACA,aACA,2BAQF,OACE,SACA,UAOF,SACE,cAQF,SACE,iBAUF,MACE,yBACA,iBAGF,MAEE,UChKE,KApMA,WACA,iBACA,kBACA,aACA,gBACA,UA/DQ,SC6KV,uBAEE,YACA,cAGF,WACE,WD+EI,6CAjKJ,eACA,gBAqKI,mBACE,cACA,eAIJ,UA5OF,WACA,uBACA,wBACA,aACA,gBACA,eCsIF,iCAEE,YACA,cAGF,gBACE,WD6FI,mBA9NJ,WACA,SACA,eCwHF,mDAEE,YACA,cAGF,yBACE,WDmGA,iBA9KA,sBACA,uBAKA,WAqBE,MCwJY,gDDCZ,YAGF,oCACE,MCLY,KDQd,mBAhIA,cAvEA,kBA4BA,QACA,WA8CA,cA3EA,kBAiCA,SACA,UAqCA,cAvEA,kBA4BA,mBACA,WA8CA,cA3EA,kBAiCA,oBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UA8CF,iBAhFE,kBAYA,sBACA,uBA0BE,MCwJY,KDxGd,SArEA,oBAqEA,SArEA,qBAqEA,SArEA,UAqEA,SArEA,qBAqEA,SArEA,qBAqEA,SArEA,UAqEA,SArEA,qBAqEA,SArEA,qBAqEA,SArEA,UAqEA,UArEA,qBAqEA,UArEA,qBAqEA,UArEA,WA2EA,gBAjCA,0BAiCA,gBAjCA,qCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,gBAjCA,sCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,gBAjCA,sCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,iBAjCA,sCAiCA,iBAjCA,sCAsCF,mBACE,cACA,eACA,UACA,WACA,MCwFc,KDrFhB,+CArDE,iBACA,kBACA,WAwDF,mDAEE,cACA,eACA,MC4Ec,KDxEhB,qEAEE,WAIF,yEAEE,MCgEc,KD7DhB,qEAEE,MC4DmB,MDtDjB,yDArIF,eACA,gBAyIE,yBACE,cACA,eAMF,6DA3IF,sBACA,uBA0BE,MCwJY,MDYd,4CApIA,eAvEA,kBA4BA,QACA,WA8CA,eA3EA,kBAiCA,SACA,UAqCA,eAvEA,kBA4BA,mBACA,WA8CA,eA3EA,kBAiCA,oBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,SACA,WA8CA,eA3EA,kBAiCA,UACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,SACA,WA8CA,eA3EA,kBAiCA,UACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,SACA,WA8CA,eA3EA,kBAiCA,UACA,UAqCA,gBAvEA,kBA4BA,oBACA,WA8CA,gBA3EA,kBAiCA,qBACA,UAqCA,gBAvEA,kBA4BA,oBACA,WA8CA,gBA3EA,kBAiCA,qBACA,UA8CF,iBAhFE,kBAYA,sBACA,uBA0BE,MCwJY,KDxGd,UArEA,oBAqEA,UArEA,qBAqEA,UArEA,UAqEA,UArEA,qBAqEA,UArEA,qBAqEA,UArEA,UAqEA,UArEA,qBAqEA,UArEA,qBAqEA,UArEA,UAqEA,WArEA,qBAqEA,WArEA,qBAqEA,WArEA,WA2EA,iBAjCA,0BAiCA,iBAjCA,qCAiCA,iBAjCA,sCAiCA,iBAjCA,2BAiCA,iBAjCA,sCAiCA,iBAjCA,sCAiCA,iBAjCA,2BAiCA,iBAjCA,sCAiCA,iBAjCA,sCAiCA,iBAjCA,2BAiCA,kBAjCA,sCAiCA,kBAjCA,sCAsCF,oBACE,cACA,eACA,UACA,WACA,MCwFc,KDrFhB,iDArDE,iBACA,kBACA,WAwDF,qDAEE,cACA,eACA,MC4Ec,KDxEhB,uEAEE,WAIF,2EAEE,MCgEc,KD7DhB,uEAEE,MC4DmB,MDtDjB,2DArIF,eACA,gBAyIE,0BACE,cACA,eAMF,+DA3IF,sBACA,uBA0BE,MCwJY,KDiBV,QAhNJ,kBA4BA,QACA,WAuLI,QApNJ,kBAiCA,SACA,UA8KI,QAhNJ,kBA4BA,mBACA,WAuLI,QApNJ,kBAiCA,oBACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,SACA,WAuLI,QApNJ,kBAiCA,UACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,SACA,WAuLI,QApNJ,kBAiCA,UACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,oBACA,WAuLI,QApNJ,kBAiCA,qBACA,UA8KI,QAhNJ,kBA4BA,SACA,WAuLI,QApNJ,kBAiCA,UACA,UA8KI,SAhNJ,kBA4BA,oBACA,WAuLI,SApNJ,kBAiCA,qBACA,UA8KI,SAhNJ,kBA4BA,oBACA,WAuLI,SApNJ,kBAiCA,qBACA,WAwLA,4CAnJA,cAvEA,kBA4BA,QACA,WA8CA,cA3EA,kBAiCA,SACA,UAqCA,cAvEA,kBA4BA,mBACA,WA8CA,cA3EA,kBAiCA,oBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,oBACA,WA8CA,cA3EA,kBAiCA,qBACA,UAqCA,cAvEA,kBA4BA,SACA,WA8CA,cA3EA,kBAiCA,UACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UAqCA,eAvEA,kBA4BA,oBACA,WA8CA,eA3EA,kBAiCA,qBACA,UA8CF,iBAhFE,kBAYA,sBACA,uBA0BE,MCwJY,KDxGd,SArEA,oBAqEA,SArEA,qBAqEA,SArEA,UAqEA,SArEA,qBAqEA,SArEA,qBAqEA,SArEA,UAqEA,SArEA,qBAqEA,SArEA,qBAqEA,SArEA,UAqEA,UArEA,qBAqEA,UArEA,qBAqEA,UArEA,WA2EA,gBAjCA,0BAiCA,gBAjCA,qCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,gBAjCA,sCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,gBAjCA,sCAiCA,gBAjCA,sCAiCA,gBAjCA,2BAiCA,iBAjCA,sCAiCA,iBAjCA,sCAsCF,mBACE,cACA,eACA,UACA,WACA,MCwFc,KDrFhB,+CArDE,iBACA,kBACA,WAwDF,mDAEE,cACA,eACA,MC4Ec,KDxEhB,qEAEE,WAIF,yEAEE,MCgEc,KD7DhB,qEAEE,MC4DmB,MDtDjB,yDArIF,eACA,gBAyIE,yBACE,cACA,eAMF,6DA3IF,sBACA,uBA0BE,MCwJY,KD+BV,QA9NJ,kBA4BA,QACA,WAqMI,QAlOJ,kBAiCA,SACA,UA4LI,QA9NJ,kBA4BA,mBACA,WAqMI,QAlOJ,kBAiCA,oBACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,SACA,WAqMI,QAlOJ,kBAiCA,UACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,SACA,WAqMI,QAlOJ,kBAiCA,UACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,oBACA,WAqMI,QAlOJ,kBAiCA,qBACA,UA4LI,QA9NJ,kBA4BA,SACA,WAqMI,QAlOJ,kBAiCA,UACA,UA4LI,SA9NJ,kBA4BA,oBACA,WAqMI,SAlOJ,kBAiCA,qBACA,UA4LI,SA9NJ,kBA4BA,oBACA,WAqMI,SAlOJ,kBAiCA,qBACA,WE4EA,eAhJA,aAlCkB,MAmClB,aApCkB,EAqClB,OL8PmB,QK7PnB,YNlDqB,mDMmDrB,YNpCiB,OMqCjB,mBACA,mBACA,kBACA,qBACA,WAlDgB,OAmDhB,wBACA,gBAEa,QAlEA,aAiFb,YArFS,KAsFT,mBACA,yBACA,kBAGmC,UA9ErB,KAmId,iBJlIkB,QImIlB,aARiB,QAajB,WDrFF,2CCiFE,sDACU,iBAdG,QAmBb,sDAEE,WAsDA,mCAhEF,iBJ7HkB,QI8HlB,aAtHwB,QA2HxB,WAJA,8FACU,iBAxHc,QA6HxB,8FAEE,WAuDA,+BAjEF,iBJ7HkB,QI8HlB,aApHsB,QAyHtB,WAJA,sFACU,iBAtHY,QA2HtB,sFAEE,WAwDA,2BAlEF,iBJ9HkB,QI+HlB,aAlHoB,QAuHpB,WAJA,8EACU,iBApHU,QAyHpB,8EAEE,WAyDA,+BAnEF,iBJ/HkB,QIgIlB,aAhHsB,QAqHtB,WAJA,sFACU,iBAlHY,QAuHtB,sFAEE,WA0DA,yBApEF,iBJlIkB,QImIlB,aA9GmB,QAmHnB,WAJA,0EACU,iBAhHS,QAqHnB,0EAEE,WA4DA,2BAjIF,YApFS,SAqFT,sBACA,yBACA,qBAMmC,UAhFrB,QAyMZ,2BAlIF,YAtFS,QAuFT,sBACA,wBACA,qBAKmC,UAjFrB,SA4MZ,yBAnIF,YAvFS,QAwFT,sBACA,wBACA,qBAImC,UAjFrB,SA8MZ,6BA9GF,gBACA,eACA,WA8GE,wEACA,6EAEA,6BD1MF,cEqHY,IDsFV,2BD3MF,cAiRa,OCpEX,oEAjFF,iBJlIkB,QImIlB,aAxHc,QA6Hd,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wLACU,iBA1HI,QA+Hd,wLAEE,WASF,wLACU,iBJtJQ,QIoNd,4GAlFJ,iBJ7HkB,QI8HlB,aAtHwB,QA2HxB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wQACU,iBAxHc,QA6HxB,wQAEE,WASF,wQACU,iBJjJQ,QIgNd,oGAnFJ,iBJ7HkB,QI8HlB,aApHsB,QAyHtB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wPACU,iBAtHY,QA2HtB,wPAEE,WASF,wPACU,iBJjJQ,QIiNd,4FApFJ,iBJ9HkB,QI+HlB,aAlHoB,QAuHpB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wOACU,iBApHU,QAyHpB,wOAEE,WASF,wOACU,iBJlJQ,QImNd,oGArFJ,iBJ/HkB,QIgIlB,aAhHsB,QAqHtB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,wPACU,iBAlHY,QAuHtB,wPAEE,WASF,wPACU,iBJnJQ,QIqNd,wFAtFJ,iBJlIkB,QImIlB,aA9GmB,QAmHnB,WAUA,OLwJmB,QKvJnB,QAtHsB,GAuHtB,gBAhBA,gOACU,iBAhHS,QAqHnB,gOAEE,WASF,gOACU,iBJtJQ,QI6NlB,4CAEA,4CACE,eAxKW,QAyKmC,cEyKhD,KACE,gBAjVJ,eACE,iBAEA,+CAEE,gBAIF,wBACE,SAEA,iEAEE,UAGF,8BH3DF,mCG4D8C,EH3D9C,gCG2D8C,EH1D9C,2BG0D8C,EHzD9C,wBGyD8C,EAMhD,oGAIE,mBA8TA,MA/PA,UAhKmB,QAiKnB,MA9JoB,QA+JpB,OAnKiB,QAoKjB,cACA,YR9IiB,OQ+IjB,YAnKqB,IAoKrB,cAjKuB,EA6ZrB,YAvPF,sBACA,iBA0PE,aAtPF,kBACA,mBA0PE,YACE,eAxaqB,WAyarB,cAKJ,iBA3PF,cACA,kBACA,UACA,kBACA,WACA,cACA,iBACA,aAzJyB,MA0JzB,aA3JyB,IA4JzB,SA1JsB,OA2JtB,UAjMqB,QAkMrB,iBACA,sBAqPE,gBAjLA,eACA,gBACA,cACA,iBACA,kBACA,YAiLA,eA3NA,eACA,gBACA,cACA,iBACA,kBACA,YA2NA,sBHjbA,cGkbkB,EHxalB,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,ICiUZ,uBHtbA,cGubkB,EH7alB,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,ICsUZ,qBH3bA,cG4bkB,EHlblB,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OG+Kb,sBHhcA,cGickB,EHvblB,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,OGqLb,yBAvQA,WA9Kc,QA+Kd,kBAIE,MH6BC,KGpBH,aA3LwB,KAybxB,2BAvOA,WAnNc,QAoNd,iBAIE,MHRC,KGiBH,aAhOwB,KA+bxB,8QACE,wBACA,gBA3XJ,iBHyHO,KGxHP,YApGkB,QAuGhB,aAhGiB,MAiGjB,aAhGiB,IAiGjB,aApGiB,KAuGnB,WAhGiB,+BAiGjB,MA5GiB,gBA6GjB,cACA,UA7GgB,QA8GhB,kBACA,cACA,iBACA,WHpDA,mBGqDoB,WHpDpB,gBGoDoB,WHnDpB,WGmDoB,WHgEpB,yDAEA,wWACE,wBACA,aGlLuB,KAqHzB,wWACE,WAxHmB,QAyHnB,aAvHuB,KAwHvB,aAIF,qZACE,iBHgGS,KG/FT,OP2KmB,QOvKrB,m3CAGE,iBHwFS,KGvFT,OPmKmB,QOsLjB,uXH1dF,cEqHY,IC8WN,wIHneN,cGsewB,EH5dxB,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,ICqXN,8CH1eN,cG2ewB,EHjexB,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,IC6XN,2IHlfN,cGqfwB,EH3exB,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,ICoYN,gDHzfN,cG0fwB,EHhfxB,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,IC4YN,qIHjgBN,cGogBwB,EH1fxB,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,OGuPP,6CHxgBN,cGygBwB,EH/fxB,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OG+PP,wIHhhBN,cGmhBwB,EHzgBxB,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OGsQP,+CHvhBN,cGwhBwB,EH9gBxB,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,OG8Qb,mBACE,wBACA,gBAIF,eACE,YAIF,SACE,eAIF,OA5OF,mCACA,gBACA,iBHnHO,QG4HP,qVAGA,gCAEA,4BAGE,aA1ViB,MA2VjB,aA1ViB,IA2VjB,aA9ViB,KAiWnB,cACA,UArWgB,QAsWhB,YRvWuB,mDQwWvB,MAxWiB,gBAyWjB,mBH/VE,cGgWc,EAiNZ,iBAzOJ,mBACE,aAyBF,cHlWE,cEqHY,ICiPd,aACE,iBA3ToB,QA4TpB,aA7WuB,KAiXzB,gBACE,iBHrJS,KGsJT,OP1EmB,QOiRnB,+DAIE,kBAGF,mDAEE,qBACA,kBACA,aArlBS,KAslBT,gBACA,wBAIF,iBACE,WAcF,SAnVF,sBACA,QA3PiB,QA4PjB,OA3PgB,WA8PhB,gBACE,YRlQe,KQmQf,WHxDK,KGyDL,QA5Pa,WA6Pb,SACA,uBAiVE,gHAjTJ,cACA,QAhR4B,0BAiR5B,WAhRwB,KAiRxB,cApUa,KAqUb,UAjR8B,OAkR9B,YR5SmB,OQ6SnB,WAjR+B,OAqR/B,WNxToB,QM2TlB,MHxGK,KGmZH,iDAEE,aAIJ,uBA9TF,cACA,QAhR4B,0BAiR5B,WAhRwB,KAiRxB,cApUa,KAqUb,UAjR8B,OAkR9B,YR5SmB,OQ6SnB,WAjR+B,OAqR/B,WNxToB,QM2TlB,MHxGK,KGgaH,2CAGE,gBAGF,qDAEE,cA9oBO,KAipBT,gCAxVJ,MNtSoB,QMmoBhB,mBArVJ,cACA,QAhR4B,0BAiR5B,WAhRwB,KAiRxB,cApUa,KAqUb,UAjR8B,OAkR9B,YR5SmB,OQ6SnB,WAjR+B,OAqR/B,WNxToB,QM2TlB,MHxGK,KGqbD,mBACE,cACA,yBACA,UACA,eAvpBmB,WAwpBnB,kBACA,cACA,SACA,eAIJ,0BACE,cAIJ,wCAGE,gBAGF,YAzXF,MNtSoB,QO+ElB,0BACE,sDACA,MFuyCc,SEnyChB,iBACE,WACA,WPnGgB,QOqGhB,0BACE,cAtGe,EA2GnB,OACE,WACA,OACA,eACA,MACA,WAEA,8BACE,gBACA,YACA,WACA,gBAEA,0CACE,eACA,WACA,WAIF,+CACE,WACA,WF2sCM,SEtsCZ,SACE,gBACA,OFosCU,SEnsCV,YFmsCU,SElsCV,kBACA,WP3IgB,QO4IhB,cA5IiB,EA+IjB,YACE,gBACA,gBAGF,cACE,eAGF,6BAEE,gBAGF,eACE,OAlGc,QAmGd,mBACA,sBACA,UAzIkB,OA4IpB,iCAEE,qBACA,wBACA,gBACA,UAjJkB,OAsJlB,yCAVF,iCAWI,kBACA,UAKJ,qBACE,kBACA,SAGF,eACE,OFipCQ,SEhpCR,SACA,UFzIS,KE2IT,6GAME,YFuoCM,SEtoCN,UF2oCe,UE1oCf,SAEA,yHACE,YTtLO,KSuLP,MP/IU,KOgJV,UACA,cACA,0BAMN,wBACE,kBACA,QACA,MAEA,0BACE,MP9JY,KO+JZ,eF8pCmB,UE7pCnB,UA9KmB,SA+KnB,YTzMS,KS0MT,kBACA,cACA,0BACA,OF2mCM,SE1mCN,YF0mCM,SEtmCR,kCACE,QACA,iBAEA,oCAKE,YACA,iBACA,4CACA,MPnKa,KOoKb,kBJ9HV,gDACE,WACA,kBACA,cACA,SAsBE,QACA,gBACA,MI5HgB,gBJ+HlB,6DAGA,MI0G6B,KJvG/B,qDACE,WACE,4CI4GA,kBACE,YACA,yBAEA,8BACE,WP7QY,QOiRZ,mCACE,MPrQU,QOuQV,+CAGE,sEAUV,iBACE,OACA,kBACA,WJzOJ,+BI4OI,oBACE,UACA,WACA,YACA,cACA,UFxPS,KEyPT,SAGF,4DAEE,WFulCoB,kBEtlCpB,WACA,WACA,WAGF,uBACE,WP5Sc,QO8Sd,yBACE,cACA,WACA,MPlQY,KOmQZ,sBACA,aA3SY,gBA4SZ,YT7Te,mDS8Tf,UFgiCc,SE/hCd,YThTW,OSiTX,eFsiCmB,UEpiCnB,gCACE,UF2hCY,SE1hCZ,cAnTU,gBAoTV,aApTU,gBHqHlB,iBJlIkB,QImIlB,aARiB,QAajB,WAJA,4EACU,iBAdG,QAmBb,4EAEE,WGyLI,0CHnMN,iBJ7HkB,QI8HlB,aARiB,QAajB,WAJA,gGACU,iBAdG,QAmBb,gGAEE,WG6LI,wCHvMN,iBJ7HkB,QI8HlB,aARiB,QAajB,WAJA,4FACU,iBAdG,QAmBb,4FAEE,WGiMI,sCH3MN,iBJ9HkB,QI+HlB,aARiB,QAajB,WAJA,wFACU,iBAdG,QAmBb,wFAEE,WGqMI,wCH/MN,iBJ/HkB,QIgIlB,aARiB,QAajB,WAJA,4FACU,iBAdG,QAmBb,4FAEE,WG0ME,8BACE,UFmgCc,SElgCd,cA3UY,gBA4UZ,aA5UY,gBHqHlB,iBJlIkB,QImIlB,aARiB,QAajB,WAJA,wEACU,iBAdG,QAmBb,wEAEE,WGgNI,wCH1NN,iBJ7HkB,QI8HlB,aARiB,QAajB,WAJA,4FACU,iBAdG,QAmBb,4FAEE,WGoNI,sCH9NN,iBJ7HkB,QI8HlB,aARiB,QAajB,WAJA,wFACU,iBAdG,QAmBb,wFAEE,WGwNI,oCHlON,iBJ9HkB,QI+HlB,aARiB,QAajB,WAJA,oFACU,iBAdG,QAmBb,oFAEE,WG4NI,sCHtON,iBJ/HkB,QIgIlB,aARiB,QAajB,WAJA,wFACU,iBAdG,QAmBb,wFAEE,WGkOE,8CACE,iBJ1IE,KI6IA,WP7WU,QOgXZ,MPhUgB,KOoUlB,gCACE,WPrXY,QOsXZ,MPrUiB,KOuUjB,sCACE,WP7XU,QO8XV,MPxUqB,KO8U3B,2BACE,QAzXc,gBA6XhB,+BACE,kBAGE,uCJxUR,WACA,cACA,QACA,SACA,iBAaE,yEACA,wBI2TQ,aAtYU,gBAuYV,kBACA,kBACA,QACA,QAIJ,qCACE,gBAEA,+CAvVR,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,6BAuVU,WAGF,6CACE,aAMN,2BACE,UACA,kBACA,UACA,MACA,WA7WN,cJmIA,6BACA,WACA,UACA,gBACA,8BIyOM,8BACE,WACA,YAEA,gCACE,YT5aS,OS6aT,4BAEA,4CACE,YThbO,OSobX,iFAGE,gBACA,aACA,UAtbY,SAwbZ,qFACE,MPnZQ,KOqZR,cAEA,iGACE,gBAKN,uCACE,4BAGF,2EAEE,SAIJ,iCACE,gCACA,gBACA,eA/b6B,UAgc7B,MP9dY,QO+dZ,YTpdS,KSqdT,UAhcwB,QAqc9B,cACE,cAKF,6CACE,SACE,WPtfc,QOwfd,iBJnVN,+BAEE,YACA,cAGF,eACE,WI8UI,wBACE,aAGF,qBACE,MJ3OQ,KI8OV,oBACE,WAGF,gDAGE,kBACA,kBACA,OA/cY,QAgdZ,aAGF,kBACE,WPhhBY,QOohBhB,0BACE,UL7hBI,SK8hBJ,cACA,cAvhBe,EA0hBjB,iBJ/dJ,oBIieM,kBAEA,oBACE,WACA,uBACA,eAEA,uBACE,MJhRM,KIkRN,qCACE,aAOF,yCACE,iBJlUF,KIqUI,WPriBM,QOwiBR,MPxfY,KO6fd,kDACE,0BACA,YFgxBE,SE/wBF,WP7jBQ,QO+jBR,wDACE,iBJnVJ,KIsVM,WPtjBI,QO6jBV,yDACE,0BACA,YFgwBE,SE/vBF,MP/gBa,KOghBb,WPjkBQ,QOmkBR,+DACE,WPxkBM,QOykBN,MPnhBiB,KO2hBrB,iCACE,yCAEA,uCJ/gBZ,WACA,cACA,QACA,SACA,iBAGE,yEACA,uBIygBY,kBACA,cAKN,qCACE,kBAEA,+CA9hBV,cJmIA,6BACA,WACA,UACA,gBACA,8BI8ZU,wGAhiBV,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,6BAmiBQ,iDAriBR,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,6BA0iBc,iEACE,YACA,YACA,SACA,gBACA,UACA,gBAOV,2BACE,OACA,SACA,yBACA,eAGE,gCACE,MPtkBe,KOukBf,YF2rBE,SE1rBF,mBACA,6BACA,WP3oBQ,QO+oBR,yEACE,MP/kBa,KOglBb,WPjpBM,QOopBR,+EACE,MPjmBU,KOkmBV,iBJlbJ,KIqbM,WPrpBI,QO0pBV,oCACE,mBACA,WJ1bP,KI8bK,wCACE,UACA,MAKN,kEAEE,mBACA,gBACA,aFgtBqB,kBE/sBrB,WACA,OFkpBM,SEjpBN,QAGF,2BACE,WP/rBY,QOgsBZ,0BACA,OF2oBM,SEtoBN,qCACE,UACA,QAEA,kDACE,WAMJ,oCACE,WACA,OAEA,iDACE,UAYJ,sCACE,iBJtfA,KIyfE,WPztBQ,QO4tBV,MP5qBc,KOgrBhB,uCACE,WPjuBU,QOkuBV,MPjrBe,KOurBf,sDAtqBV,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,6BAyqBQ,wDA3qBR,cJyIA,2BACA,YACA,WACA,iBACA,UI3IA,8BC+CE,WAEE,gBLmCJ,mCAEE,YACA,cAGF,iBACE,WKxCE,+CAEE,cACA,2BAEA,iEACE,WA/I6B,QAkJ/B,mDACE,WLsFA,QKrFA,MLiGH,KKhGG,QHoKqB,OGnKrB,cACA,YV9Ie,mDU+If,UAtJuB,KAwJvB,+DACE,WA5J0B,QAgK9B,iEACE,aACA,QA5JkB,SA8JlB,+EACE,cACA,WRhKU,QSmGlB,WAjEF,aA3BmB,MA4BnB,aA3BmB,IA4BnB,cACA,YXlBmB,OWmBnB,cA5BoB,QA6BpB,kBACA,uCACA,UJmSgB,SFjRhB,kCMLA,iBT9CoB,QS+CpB,qBAQE,MNgKK,KMzHH,kBAhCJ,UAtDsB,SAuDtB,QApDoB,YAqDpB,cACA,kBACA,IA5DgB,IA6DhB,sBACA,MA7DqB,OA8DrB,MNkKK,KMjKL,QA7DoB,GA8DpB,WA3DuB,QA6DvB,gDAEE,QAjEwB,GAwFtB,kBN5FF,cEqHY,IIrBV,iBNhGF,cAiRa,OM7KX,mBA5DJ,iBTzCoB,QS0CpB,qBAQE,MNgKK,KMzGH,iBAhEJ,iBT1CoB,QS2CpB,qBAQE,MNgKK,KMrGH,qBApEJ,iBTzCoB,QS0CpB,qBAQE,MNgKK,KMjGH,mBAxEJ,iBT3CoB,QS4CpB,qBAQE,MNgKK,KM7FH,gBA5EJ,iBT9CoB,QS+CpB,qBAQE,MNgKK,KMzFH,uBACE,UCtCJ,aA1EF,cACA,QA7Bc,0BA8Bd,gBACA,cACA,gBACA,aA3BmB,MA4BnB,aLwWkB,EKrWlB,yBACA,aVDoB,QGlBlB,cE0XW,EKnST,eA7DJ,SACA,MP2OgB,KO1OhB,UApCgB,SAqChB,YArCgB,SAsChB,eAlCqB,UAmCrB,MVrCoB,QUuCpB,8DApCiB,UAsCjB,iBACE,MV1CkB,QU8CpB,uBACE,OX2PmB,QW1PnB,MPuLG,KOtLH,yBACE,OXwPiB,QWvPjB,MPoLC,KOjLH,wHACqB,qBAIvB,2BACE,MPqKQ,KOpKR,mCPoKQ,KOlKR,wIAIE,qBACA,MP6JM,KO5JN,OXqOiB,QWjOrB,sBACE,YACA,MPqJI,KOpJJ,gBACA,kBACA,QAGF,kCACE,YACA,SAkBJ,kDACE,YCVE,qBAhFA,cACA,UAOE,mBRyIJ,uDAEE,YACA,cAGF,2BACE,WQ3IA,wBACE,cACA,YACA,MRgPY,KQ7OV,0BAkEF,mBA5DF,uBACE,WAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,YAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,2CACE,WAdJ,wBACE,oBAMA,gBAEA,wCACE,WAGF,2CACE,WAdJ,wBACE,oBAMA,gBAEA,wCACE,WAGF,2CACE,YAkDF,4CAhEF,wBACE,WAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,qBAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,qBAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,qBAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,YAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,wBACE,qBAMA,gBAEA,wCACE,WAGF,0CACE,WAdJ,yBACE,UAMA,gBAEA,yCACE,WAGF,4CACE,WAdJ,yBACE,oBAMA,gBAEA,yCACE,WAGF,4CACE,WAdJ,yBACE,oBAMA,gBAEA,yCACE,WAGF,4CACE,YAsDF,4CApEF,uBACE,WAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,UAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,YAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,uBACE,qBAMA,gBAEA,uCACE,WAGF,yCACE,WAdJ,wBACE,UAMA,gBAEA,wCACE,WAGF,2CACE,WAdJ,wBACE,oBAMA,gBAEA,wCACE,WAGF,2CACE,WAdJ,wBACE,oBAMA,gBAEA,wCACE,WAGF,2CACE,YCsGJ,cA9JA,gBACA,SACA,OTgKF,yCAEE,YACA,cAGF,oBACE,WSRE,iBAnHF,cACA,qBA5BF,iDAEE,sBACA,kCAKA,yEAEE,cAyIE,uBAxHJ,cACA,qBAIA,cACA,SAoHM,WArJR,6DAEE,sBACA,kCAKA,qFAEE,cAyBF,6DAEE,qBACA,kCACA,oBACA,SACA,cAKA,qFAEE,aA0GA,iCA/HJ,cACA,qBA5BF,iFAEE,sBACA,kCAKA,yGAEE,cAmJI,yCAHF,iCA/HJ,cACA,qBAIA,cACA,SAjCF,iFAEE,sBACA,kCAKA,yGAEE,cAyBF,iFAEE,qBACA,kCACA,oBACA,SACA,cAKA,yGAEE,cAmHF,uBAxIF,cACA,qBA5BF,6DAEE,sBACA,kCAKA,qFAEE,cAkFF,6GTpGA,cSwGkB,EAGlB,6JTjGA,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,IOGZ,yJT9GA,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,IO0DV,6BA5IF,cACA,qBAIA,cACA,SAjCF,yEAEE,sBACA,kCAKA,iGAEE,cAyBF,yEAEE,qBACA,kCACA,oBACA,SACA,cAKA,iGAEE,aA4CJ,qITpGA,cSwGkB,EAGlB,qLT1FA,wBEoGY,IFnGZ,yBEmGY,IFlGZ,uBEkGY,IFjGZ,wBEiGY,IOGZ,iLTvGA,2BEoGY,IFnGZ,4BEmGY,IFlGZ,0BEkGY,IFjGZ,2BEiGY,IO+DR,4CADF,uCAhJF,cACA,qBA5BF,6FAEE,sBACA,kCAKA,qHAEE,cAkFF,6KTpGA,cSwGkB,EAGlB,6NTjGA,kCE2GY,IF1GZ,+BE0GY,IFzGZ,0BEyGY,IFxGZ,uBEwGY,IOGZ,yNT9GA,mCE2GY,IF1GZ,gCE0GY,IFzGZ,2BEyGY,IFxGZ,wBEwGY,KOmER,yCALF,uCAhJF,cACA,qBAIA,cACA,SAjCF,6FAEE,sBACA,kCAKA,qHAEE,cAyBF,6FAEE,qBACA,kCACA,oBACA,SACA,cAKA,qHAEE,aA4CJ,6KTpGA,cSwGkB,EAGlB,6NT1FA,wBEoGY,IFnGZ,yBEmGY,IFlGZ,uBEkGY,IFjGZ,wBEiGY,IOGZ,yNTvGA,2BEoGY,IFnGZ,4BEmGY,IFlGZ,0BEkGY,IFjGZ,2BEiGY,KOwEV,sBA1JF,cACA,qBA5BF,2DAEE,sBACA,kCAKA,mFAEE,cAkFF,yGTpGA,cSwGkB,EAGlB,yJTjGA,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OSzJb,qJT9GA,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,OShFX,4BA9JF,cACA,qBAIA,cACA,SAjCF,uEAEE,sBACA,kCAKA,+FAEE,cAyBF,uEAEE,qBACA,kCACA,oBACA,SACA,cAKA,+FAEE,aA4CJ,iITpGA,cSwGkB,EAGlB,iLT1FA,wBCrCS,KDsCT,yBCtCS,KDuCT,uBCvCS,KDwCT,wBCxCS,KQ4IT,6KTvGA,2BCrCS,KDsCT,4BCtCS,KDuCT,0BCvCS,KDwCT,2BCxCS,KQ0NL,4CADF,sCAlKF,cACA,qBA5BF,2FAEE,sBACA,kCAKA,mHAEE,cAkFF,yKTpGA,cSwGkB,EAGlB,yNTjGA,kCAuQa,OAtQb,+BAsQa,OArQb,0BAqQa,OApQb,uBAoQa,OSzJb,qNT9GA,mCAuQa,OAtQb,gCAsQa,OArQb,2BAqQa,OApQb,wBAoQa,QSvET,yCALF,sCAlKF,cACA,qBAIA,cACA,SAjCF,2FAEE,sBACA,kCAKA,mHAEE,cAyBF,2FAEE,qBACA,kCACA,oBACA,SACA,cAKA,mHAEE,aA4CJ,yKTpGA,cSwGkB,EAGlB,yNT1FA,wBCrCS,KDsCT,yBCtCS,KDuCT,uBCvCS,KDwCT,wBCxCS,KQ4IT,qNTvGA,2BCrCS,KDsCT,4BCtCS,KDuCT,0BCvCS,KDwCT,2BCxCS,MQoOL,wBA7KJ,cACA,qBAoGA,UAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,qBAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,UAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,UAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,qBAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,qBAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WAoEE,wBA7KJ,cACA,qBAoGA,YAhIF,+DAEE,sBACA,kCAKA,uFAEE,cAwHF,+DAEE,WTWJ,qCAEE,YACA,cAGF,kBACE,WS2DE,0BA7NF,WACA,aAlByB,QAoBzB,8BACE,gBCSF,iCAEE,gBACA,cACA,gBV0IJ,4FAEE,YACA,cAGF,6CACE,WU/IE,uCACE,MVsPU,KUrPV,kBAGF,+EACE,eAIJ,mBACE,WVuMC,KUtMD,eACA,WACA,YACA,MACA,OACA,YAEA,iDAGF,oBACE,kBACA,YACA,YACA,gBACA,SAGF,sBACE,kBACA,QACA,SACA,MVyKE,KUxKF,eAGF,aACE,WACA,kBAEA,iBACE,kBACA,SACA,QACA,iBACA,gBACA,eAIJ,kBACE,MVqJE,KUpJF,UA5EuB,OA6EvB,gBACA,gBACA,kBACA,SACA,WVuJC,KUtJD,WACA,QAlFqB,eAmFrB,kBACA,OAGF,gBACE,YACA,kBACA,iBACA,UApGgB,KAqGhB,cACA,MVkIE,KUjIF,aAEA,4CACU,MV8HR,KU3HJ,oDACE,kEAIF,qBACE,aACA,2CACE,cAKJ,4CACE,wCAEE,kBACA,YACA,WACA,MACA,kDACE,kBACA,QACA,cACA,QACA,SACA,kBACA,yEAGJ,oBACE,OACA,yBACE,SACA,2BACA,mBVwFF,KUrFF,oBACE,QACA,yBACE,2BACA,kBViFF,KU7EF,0DAC+B,WAI7B,kDACE,WAtKa,kBAuKb,OArJiB,MAsJjB,gBACA,kBAEA,qDACE,qBACA,YACA,YACA,kBACA,WAEA,wDACE,cACA,MAjKkB,MAkKlB,mBACA,MVoGI,KUnGJ,gBACA,eACA,UACA,kBACA,Od8HS,Qc7HT,WACA,WAGE,uEACE,YACA,eAIJ,6DACE,YACA,gBACA,cAGF,4DACA,0BACA,sBAGA,0EACA,yEAKN,qDACE,WV6BH,KU5BG,gBACA,OAzMmB,IA6MvB,gBACE,kBACA,SACA,WACA,eACA,eCjBJ,YA9JF,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAME,WACA,WA/DoB,KAgEpB,OAjEgB,KAkEhB,WXoKK,KWnKL,sBACA,UArCmB,QAsCnB,WAcA,WA/EoB,IA+KL,UApLI,MA4DrB,uCACA,yCAyBE,8BXCF,cACA,QACA,SACA,iBAQE,4DACA,0BWXE,kBACA,UACA,KA/D4B,KAgE5B,WAEF,kBXPF,WACA,cACA,QACA,SACA,iBAQE,4DACA,0BWJE,kBACA,UACA,SACA,WAGF,yBACE,UACA,MA5E4B,KA8E9B,wBACE,UACA,UA4GA,uBAjKJ,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAME,WACA,WA/DoB,KAgEpB,OAjEgB,KAkEhB,WXoKK,KWnKL,sBACA,UArCmB,QAsCnB,WA0CA,aACA,YA5GoB,IA+KL,UApLI,MA4DrB,kDACA,oDAsDE,8BX7BF,WACA,cACA,QACA,SACA,iBAkBE,4DACA,yBWQE,kBACA,IA3F4B,KA4F5B,WACA,WAEF,6BXpCF,WACA,cACA,QACA,SACA,iBAkBE,4DACA,yBWeE,kBACA,QACA,WACA,WA4FA,sBArKJ,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAME,WACA,WA/DoB,KAgEpB,OAjEgB,KAkEhB,WXoKK,KWnKL,sBACA,UArCmB,QAsCnB,WA+DA,aACA,iBA8Ce,UApLI,MA4DrB,iDACA,mDA2EE,6BXlDF,WACA,cACA,QACA,SACA,iBAaE,4DACA,wBWkCE,kBACA,IAhH4B,KAiH5B,YACA,UACA,WAEF,4BX1DF,WACA,cACA,QACA,SACA,iBAaE,4DACA,wBW0CE,kBACA,QACA,YACA,UACA,WAyEA,qBAzKJ,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAME,WACA,WA/DoB,KAgEpB,OAjEgB,KAkEhB,WXoKK,KWnKL,sBACA,UArCmB,QAsCnB,WAsFA,gBACA,cAuBe,UApLI,MA4DrB,gDACA,kDAkGE,4BXzEF,WACA,cACA,QACA,SACA,iBAGE,4DACA,uBWmEE,kBACA,SACA,aACA,KAzI4B,KA0I5B,WACA,WAEF,2BXlFF,WACA,cACA,QACA,SACA,iBAGE,4DACA,uBW4EE,kBACA,SACA,aACA,SACA,WACA,WAqDA,eAtCJ,UA9JqB,QA+JrB,Of4HqB,Qe1HrB,YA/JuB,SAgKvB,SAEA,0CACU,WXwCH,KWtCP,sBXjLE,cEqHY,IS8Dd,iBACE,cACA,QA1KsB,MA2KtB,MXyCQ,KWdN,oBAjLJ,kBACA,aACA,WA1BsB,KA2BtB,cACA,aAeE,QAlCyB,QAmCzB,WACA,OA1EgB,KA2EhB,WA1EoB,KA2EpB,WX0JK,KWzJL,sBACA,UA/CmB,QAgDnB,WAoGe,UApLI,MA4DrB,+CACA,iDA6KI,iCACA,kCACA,mCACA,kCACA,iBACE,sBACA,0BAEA,sBACE,kBC9HN,iCAvEA,kBACA,aAuCA,cAjE0B,UA6B1B,+CACE,kBACA,WACA,QACA,SACA,cACA,mBACA,4DACA,QA8BF,+CACE,aAnEyB,QAoEzB,MAnE6B,WAoE7B,WAnEwB,YAoF1B,+CACE,4DAYA,2CAzDF,cAvD0B,SAyD1B,uDACE,aAhEW,QAiEX,MAzD6B,SA0D7B,WAzDwB,UAgG1B,yDACE,4DAgBA,6CAlDF,cA5D0B,UA8D1B,2DACE,aA1EW,SA2EX,MA9D6B,UA+D7B,WA9DwB,YA0F1B,2DACE,4DAoBA,6CAhCF,cAtE0B,SAwE1B,2DACE,aAxEyB,SAyEzB,MAxE6B,WAyE7B,WAxEwB,YA8E1B,2DACE,4DAwBA,iEACE,4DClGJ,YAxBF,kBACA,YAbuB,UAcvB,eAb0B,MAc1B,SACA,cAdyB,KAezB,gBAEA,sCAdqC,OAerC,gCAEA,0EAIE,kBACA,MACA,OACA,WACA,YCUA,aAlBF,6BACA,YApBiC,UAqBjC,aAvB4B,EAwB5B,QAnBoB,EAoBpB,gBACA,SAlBqB,OAoBrB,gBACE,gBACA,Md6Pc,Kc5Pd,YA5BoC,SA6BpC,QArBkB,MAsBlB,0BAnB2B,MC2B3B,eAjBF,iBAfa,QAgBb,kBAG0B,Mf2NrB,KexNL,aArBuB,MAsBvB,aArBuB,IAsBvB,SACA,YAnCe,uCAoCf,UAnCoB,QAoCpB,QA9BkB,iBfehB,cEqHY,Ic3BZ,OAhFA,aA/BiB,MAgCjB,aA/BgB,IAgChB,qBACA,cA1BkB,QA2BlB,QA1BY,QA4BZ,WnBEkB,QmBChB,MhB8MC,KgBtMH,oBACE,aAGF,mBACE,gBAQE,yFASE,MhBgLH,KgB5JD,4DAME,cACA,sBAEA,wHACE,gBAcJ,eAnFF,aA/BiB,MAgCjB,aA/BgB,IAgChB,qBACA,cA1BkB,QA2BlB,QA1BY,QA4BZ,WA8EmB,QA3EjB,MhB8MC,KgBtMH,4BACE,aAGF,2BACE,gBAQE,iKASE,MhBgLH,KgB5JD,4GAME,cACA,sBAEA,wKACE,gBAiBF,8BACE,MnBvGY,QmByGZ,wEAEE,MAzGqB,QA8G3B,chB1GF,cEqHY,IecZ,iBAjHF,kBACA,MACA,SACA,OACA,QACA,WjB4MO,KiB3MP,WA3CkB,gBA4ClB,aACA,aACA,OA0GE,qBAhGA,kBACA,aACA,kBACA,aACA,YACA,MACA,cf0EY,IezEZ,OAgDQ,iBjBqHH,KiBpHiB,QAxGH,QA0GP,sBAIZ,WA7GgB,wBAuGM,QAkDiB,SAjGvC,yCAuFA,qBAtFE,kBAIF,wFAGA,4DAEA,6DAIA,4CAyEA,qBAxEE,MA1EiB,IA2EjB,UlBpFM,SkBqFN,OACA,QACA,eA0CF,4CA0BA,qBAzBE,IA1HgB,WA+JhB,mCjBjJF,cEqHY,Ie6BV,iCjBlJF,cAiRa,OiB9HX,uCAtDoB,QAsD8B,EAvFpD,4CAwFE,+BAvFA,MAuF4C,IAtF5C,UlBpFM,SkBqFN,OACA,QACA,eALF,4CAyFE,iCAxFA,MAwF4C,IAvF5C,UlBpFM,SkBqFN,OACA,QACA,eALF,4CA0FE,mCAzFA,MAyF8C,IAxF9C,UlBpFM,SkBqFN,OACA,QACA,eALF,4CA2FE,iCA1FA,MA0F4C,IAzF5C,UlBpFM,SkBqFN,OACA,QACA,eALF,4CA4FE,mCA3FA,MA2F6C,IA1F7C,UlBpFM,SkBqFN,OACA,QACA,eAwFA,+BAEE,MACA,OACA,YACA,aACA,iBACA,0BACA,yBArGJ,4CA6FE,+BA5FA,MA6FoC,MA5FpC,UlBpFM,SkBqFN,OACA,QACA,eAmGA,6DA/CJ,UA5HuB,OA6HvB,cACA,kBACA,IA9HiB,QA+HjB,MA9HkB,SA+HlB,MjBgGM,KiB/FN,YtBrHiB,KsBsHjB,OrByKqB,QqB9HnB,OAEE,aAEA,kCAzJJ,kBACA,MACA,SACA,OACA,QACA,WjB4MO,KiB3MP,WA3CkB,gBA4ClB,aACA,aACA,OAoJI,aACE,cAKJ,aACE,qBACE,aACA,4BCvGJ,UAtDF,cACA,SACA,QhB8iCiB,QgB7iCjB,gBAhDmB,KAiDnB,oBAhDuB,QAiDvB,YvB1CuB,mDuB4CvB,aACE,OhB6iCmB,QgB5iCnB,UhBkjCiB,KgBjjCjB,YvBhCiB,OuBkCjB,4BACE,cACA,MrB/CgB,QqBgDhB,OAnDiB,EAoDjB,QAnDkB,iBAqDlB,oEAEE,WAzDiB,iBA0DjB,MhBqiCoB,QgBjiCxB,+CACE,MhB+hCuB,QgB9hCvB,YvBjDe,OuBkDf,YvBjEmB,mDuBoErB,qBACE,qBACA,SACA,UACA,gBACA,iBrB7CgB,QqBgDlB,qBACE,MrBzEgB,QqB4Ed,UhBghCa,KgB/gCb,YArEuB,KAwEzB,eAvE4B,UCmF9B,SA5DF,cACA,WACA,gBACA,OA7CoB,oBA8CpB,YA7CyB,OA+CzB,YACE,yBAGF,oCAGE,MnB+Nc,KmB9Nd,eACA,iBACA,gBACA,YxBrDqB,mDwBsDrB,YxBvCiB,OwBwCjB,UAxDgB,QAyDhB,MnB6KQ,KmB3KR,0CACE,gBAzDoB,KA0DpB,MnByKM,KmBxKN,QA1DY,cA2DZ,4DACE,MA1DmB,QA8DvB,+DnBzDA,cmBNoB,IAiElB,YxBtDe,OwBuDf,WtBlEgB,QsBmEhB,QApEY,cAqEZ,OAzDkB,QA0DlB,MnBkJG,KmBjJH,iFACE,WA/DkB,QC8FtB,MAnEF,WpBoLO,KoBnLP,cAToB,QAUpB,sBACA,aAba,KAeb,cACE,WA5Be,cA6Bf,MpB8LG,KoB5LD,UA7BoB,KA8BpB,YA7BsB,KAiC1B,YACE,WvBzBkB,QuB4BhB,oCAEE,QApDa,sBAqDb,UAxDe,QAyDf,YzB7CW,KyB8CX,MpB8KD,KoBzKL,YACE,WvBvCkB,QuB0ChB,oCAEE,QAlEa,sBAmEb,UAtEe,QAuEf,YzB3DW,KyB4DX,MpBgKD,KoB1JH,wBAEE,QA7Dc,iBA8Dd,UA7DgB,QA8DhB,MpBsJC,KoBrJD,WpByLY,KoBtLd,sDAEsB,WvBhEJ,QuBmEpB,sGAKQ,QAtEM,WAsEmB,YA1Ef,SCQhB,IAjBF,cACA,qBACA,sBACA,eACA,WAxBiB,yBrB0DjB,8BqBhCA,oBAEE,WA3BqB,8BAwCnB,WrB5BF,cEqHY,IoBGd,sCACA,wCACA,0CACA,4CAGE,yCACE,iDACA,mDACA,qDACA,wDAJF,mBACE,4CACA,8CACA,gDACA,mDAJF,gEACE,kDACA,oDACA,sDACA,yDAJF,4CACE,6CACA,+CACA,iDACA,oDAJF,gEACE,iDACA,mDACA,qDACA,wDAJF,4CACE,4CACA,8CACA,gDACA,mDAJF,iEACE,kDACA,oDACA,sDACA,yDAJF,4CACE,6CACA,+CACA,iDACA,oDAJF,uEACE,mDACA,qDACA,uDACA,0DAJF,6CACE,8CACA,gDACA,kDACA,qDA4BF,oEAmBE,SACA,UAIF,EACE,MzB7LgB,QyB8LhB,gBAvJmB,KAwJnB,oBAEA,gBAEE,MAzJkB,QA+JpB,kBAIF,EACE,YA5LkB,QA6LlB,Y3BpMe,O2BqMf,UA5LgB,KA6LhB,YA5LkB,IA6LlB,cA5LoB,QA6LpB,eAzLqB,mBA2LrB,OAlEJ,qBACA,gBAmEI,QACE,UAjMoB,QAkMpB,YAjMsB,KAkMtB,WAjMqB,OAsMzB,kBACE,Y3BnOc,8B2BoOd,Y3BtNe,O2BuNf,W3BvNe,O2BwNf,MtBKC,KsBJD,eAhPkB,mBAiPlB,WAnPc,MAoPd,cAnPiB,MAoPjB,YAtPe,IAwPf,sDACE,UA5NU,IA6NV,MA5NW,QA6NX,cAIJ,sBACA,uBACA,sBACA,sBACA,sBACA,kBAEA,WA/FF,YAjJsB,IAkJtB,MAjJqB,QAkJrB,Y3B/ImB,O2BgJnB,WAjJqB,MAkJrB,cAjJwB,MA8OtB,GACE,qBACA,qBACA,WACA,2BACA,SAIF,KAEE,kBACA,oBAGF,SAEE,Y3B9Pa,K2B+Pb,oBAGF,MACE,UAjQY,IAkQZ,oBAGF,KACE,Y3BtRkB,kC2BuRlB,Y3B1Qe,O2B2Qf,MtB/CC,KsBgDD,iBzBxLkB,QyByLlB,aAvPa,IAwPb,aAvPc,MAwPd,aAvPc,QAwPd,QAvPS,0BA2PX,SAGE,UA9QgB,KA+QhB,YA9QkB,IA+QlB,cA9QoB,QA+QpB,oBA9OgB,QA+OhB,YApRkB,QAuRpB,GACE,YpB7Ca,OoB8Cb,aACE,YAlPqB,EAoPnB,sCAEE,YArPS,QAsPT,gBACA,gBASJ,kBAEE,YAlQW,QAmQX,gBAMF,iEAGF,6CpB1Ea,OoB2Eb,6CpB3Ea,OoB4Eb,yCpB5Ea,OoB6Eb,6BAIF,GACE,YAtRqB,OAwRnB,kBAEE,YAxRW,QAyRX,gBAOJ,MACE,cA/R+B,MAgS/B,Y3BjVW,K2BmVb,oBAjS0B,OAqS5B,aAEE,yBACA,cACA,MzBjXgB,KyBkXhB,O1B5Dc,K0B8DhB,KACE,oBACA,YACE,cApSY,gBAyShB,WACE,mBACA,QAlTe,6BAmTf,YAlTc,eAoTd,gBACE,cACA,UArToB,SAsTpB,MArTqB,KAsTrB,uBACE,aAGF,4CAEE,MA5TmB,KAgUzB,wBAEE,YAlXkB,IAmXlB,MAvUkB,QA2UpB,OACE,qBACA,OAjUe,cAkUf,sBACA,QApUgB,eAsUhB,UACE,SACA,cAEF,WACE,Y3B3YW,K2B4YX,UAlUyB,SAuU3B,6B3BjZa,K2BmZb,aACE,O1BtHe,Q0BuHf,gBAjU2B,KAkU3B,Y3BtZW,K2BuZX,YACA,QAxUmB,WA6UvB,4CACE,8BAzbe,IA0bf,aApbS,QAqbT,aApbS,UAqbT,aApbS,UAqbT,aApbS,UAqbT,aApbS,SAqbT,aApbS,MA+bT,oCACA,aACE,EACE,oCACA,sBACA,2BACA,4BAGF,YACY,0BACZ,0CAEA,+CAGA,4DAEqB,WAErB,eAEE,sBACA,wBAGF,iCAEA,OACM,wBAEN,8BAEA,kBAEA,QAGE,UACA,SAGF,MACK,uBAEL,uCACA,qCACA,wCACA,4CCrRJ,mBACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BA7BN,4CACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BA7BN,4CACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BA7BN,4CACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BA7BN,6CACE,iZACE,2BAEF,iZACE,wBAGA,icvBdN,2BACA,YACA,WACA,iBACA,UuBaM,qcvB5BN,6BACA,WACA,UACA,gBACA,8BuB6BM,qfACE,yBAEF,qfACE,sCAEF,qfACE,mCAEF,ybACE,6BAEF,k3BACE,+BAaR,uCACqB,2BACrB,uCACqB,wBAInB,iDACsB,yBAGtB,iDACsB,sCAGtB,iDACsB,mCAGtB,2CACsB,6BAItB,sFACsB,8BAGxB,gDACE,uCACqB,2BACrB,uCACqB,wBAInB,iDACsB,yBAGtB,iDACsB,sCAGtB,iDACsB,mCAGtB,2CACsB,6BAItB,sFACsB,+BAI1B,+CACE,uCACsB,2BACtB,uCACsB,wBAIpB,iDACuB,yBAGvB,iDACuB,sCAGvB,iDACuB,mCAGvB,2CACuB,6BAIvB,sFACuB,+BAK3B,wCACA,2CACA,kDACA,+CAGA,8CACA,qDACA,2DACA,kEACA,wDACA,+DACA,+CACA,sDACA,gDACA,uDACA,gDACA,uDAIA,aACE,8BACA,6BAEA,8CACA,2DACA,wDACA,+CACA,gDACA,iDCzXJ,SAEI,mBACA,M3BgIa,Q2B7HjB,UACI,c3BoBkB,Q2BnBlB,M3B4HW,Q2BzHf,QACI,M3ByHS,Q2BtHb,QACI,M3BsHS,Q2BnHb,SACI,M3BmHU,Q2B3Gd,EACI,qBACA,kBACA,iBACA,aACA,sBAEA,kBAEJ,cAEI,iBACA,yBAEJ,0BAEI,wBAEJ,iCAGI,SACA,WAEJ,WACI,SACA,WACA,qCAWJ,kBACI,Y7BpEgB,8B6BqEhB,mBACA,UAEJ,GACI,U7BlDgB,Q6BmDhB,aAEJ,GACI,U7BrDgB,Q6BsDhB,qBAEA,eACI,aAER,GACI,U7B3DgB,Q6B4DhB,qBAEJ,GACI,U7B9DgB,O6B+DhB,qBAEJ,GACI,U7BjEgB,Q6BkEhB,iBAQJ,kBtByBgB,IsBxBZ,uBACkB,iCAClB,yBACkB,kCAClB,2BACkB,iCAEtB,OACI,sBAEJ,qEAEI,SAEJ,6BAEI,M3BlFkB,Q2BmFlB,Y7BxHqB,mD6ByHrB,mBACA,oBAEJ,iCAEI,iCACA,M3B1FkB,Q2B4FtB,6CAEI,gCACA,M3BhIkB,Q2BkItB,kBACI,mBACA,iBAQJ,GACI,mBAQJ,IACI,cACA,sBACA,YACA,iB3B1DoB,Q2B2DpB,ctB/BY,IsBiChB,SACI,oCACA,SAGJ,KACI,kBACA,gBAQJ,MACI,iBACA,UAEJ,GACI,cAGJ,WACI,gBACA,cAIA,YAEK,gBAOT,eACI,gBAEJ,GACI,iBACA,iBAIJ,8BACA,sEAOA,WACI,kBACA,kBACA,YACA,wBACA,M3BtLkB,Q2ByLlB,qC3B1LkB,Q2B4LlB,kBACI,0BACA,eACA,cACA,kBACA,WACA,SACA,M3BlMc,Q2BoMlB,iBACI,cACA,YACA,eACA,cACA,kBACA,YACA,YACA,M3B5Mc,Q2B8MlB,uBACI,aAEJ,4CACI,M3BnNc,Q2BqNtB,KACI,gBAGJ,eACI,mBAGJ,KACI,yBAQJ,aACI,eACA,SACA,yBAEJ,QACI,kBAEJ,YACI,kCAEJ,cACI,kCAIJ,mBACI,YACI,mBAGR,6CACI,YACI,qBASR,kB7B3SyB,mD6B4SzB,mB7B3SoB,8B6B6SpB,wB7BtRoB,Q6BuRpB,wB7BtRoB,Q6BuRpB,wB7BtRoB,Q6BuRpB,wB7BtRoB,O6BuRpB,wB7BtRoB,Q6BuRpB,uB7BzTiB,K6BgUjB,kBACI,WACA,kBACA,WACA,WACA,iBACA,gCAEJ,WACI,gBAEJ,cACI,U7BzSgB,K6B2SpB,aACI,kBACA,gBAUJ,WACE,uBACA,iCACA,wNAMF,+BACA,4BAGA,2CAEA,0rCAwDE,qBACF,uBACA,kBACA,mBACA,oBACA,cACA,wBACA,kCACA,oBACA,kCACA,mCACA,2BAGA,iCACA,iCACA,kCACA,gCACA,8BACA,+BACA,sCACA,sCACA,uCACA,oCACA,2CACA,2CACA,0CACA,+BACA,8BACA,6BACA,iCACA,8BACA,gCACA,6BACA,kCACA,iCACA,gCACA,+BACA,oCACA,+BACA,wCACA,8BACA,mCACA,mCACA,8BACA,kCACA,8BACA,iCACA,6BACA,iCACA,qCACA,mCACA,mCACA,gCACA,6BACA,oCACA,8BACA,uCACA,qCACA,mCACA,8BACA,gCACA,iCACA,yCACA,+BACA,+BACA,iCACA,8BACA,iCC9dA,gDACuC,gBACvC,wDACA,yLAUqB,WACrB,qCACA,2BAOA,YACI,8CACA,sCAEA,uEACI,mBASR,mBACE,aAQF,UACI,iB5B3CkB,Q4B6CtB,0BACI,iB5B9CkB,Q4BgDtB,oBACI,kBACA,mBACA,Y9BtDgB,8B8BuDhB,WACA,yBACA,qCAEJ,0BACI,aACA,yBAEJ,oCACI,gBASJ,yCAII,UACI,gBAEJ,UACI,aAEJ,uBACI,eAEJ,gCACI,eAEJ,oBACI,aACA,eACA,kBAKJ,oCACI,iBAQR,gEACI,UACI,gBAEJ,UACI,aAEJ,uBACI,eAEJ,gCACI,eAEJ,oBACI,eACA,aAEJ,oCACI,iBAQR,gEACI,UACI,gBAEJ,UACI,aAEJ,uBACI,eAEJ,gCACI,eAEJ,oBACI,aACA,gBAQR,4CACI,UACI,gBAEJ,UACI,aAEJ,uBACI,eAEJ,gCACI,eAEJ,oBACI,eACA,cAKR,mBACI,aAEJ,mBACI,aAEJ,yBACI,aAEJ,yBACI,aAQJ,YACI,mBACA,6BACA,gCAEJ,sBACE,iBAOF,wBACI,M5BhLkB,Q4BmLtB,mBACI,W5BpLkB,Q4BqLlB,SAEJ,mBACI,WAEJ,yBACI,W5BvNkB,Q4ByNtB,aACE,mBACA,cAEA,aACE,0BACA,cAEF,mBACE,qBACA,M5B9NkB,Q4BsOtB,WACI,sBAEJ,aACI,eACA,YACA,kBAEJ,mBACI,W5B3NkB,Q4BmOtB,qCAEI,mBACA,gBAGJ,QACI,iBACA,oBACA,W5BtOkB,Q4BuOlB,M5BpLkB,K4BuLlB,UACI,M5BrQc,Q4BuQlB,sBAEI,mBACA,WACA,yBAQR,WACI,W5BrPkB,Q4BsPlB,M5B3PkB,Q4B4PlB,iBAGJ,+BACI,WAGJ,WACI,M5BpQkB,Q4BqQlB,SACA,yBACA,iBACI,WAIR,cACI,8BAGF,iBACE,mBAEF,gBACE,oBACA,cACA,WACA,kBACA,M5BnRkB,Q4BoRlB,W5BzRkB,Q4B0RlB,kBACA,sBACE,W5BvRgB,Q4BwRhB,WAUN,gCACA,gCACA,gCACA,gCACA,gCACA,gCACA,gCACA,gCACA,gCAEA,mCACA,mCACA,mCACA,mCAEA,iCACA,kCAEA,mCACA,kCACA,oCACA,oCClWA,iCAGI,gBACA,iBAEJ,QACI,cACA,WxB3BW,KwBmCf,eACE,0BACA,gBACA,cxB+Gc,IwBvGhB,2CACA,0DACA,gEAOA,WACE,Y/BlCuB,mD+BmCvB,uCAEA,aACE,gBAEF,aACE,6BACA,WACA,8BAEF,mBACE,6BAEF,oBACE,W7BVkB,Q6BWlB,WACA,qBACA,Y/BlDoB,kC+BoDtB,4BACE,aACA,M7B/CkB,Q6BgDlB,WACA,sBAEF,gBACE,iB7BhCkB,Q6BiClB,uCACA,qBACA,M7BzBkB,Q6B2BpB,qBpBhBA,iBoBiBuB,QpBhBvB,qBAQE,MNgKK,K0BtJP,6BACE,iCACA,M7BhEkB,Q6BuEtB,kCACE,oC7B1CoB,Q6B2CpB,0EAG0B,iB7BxCN,Q6B+CtB,4CACA,0CACA,kEACA,+E7BjEsB,Q6BmEtB,qC7B1DsB,Q6BiEtB,0CACA,8CACA,gDACA,gDACA,uDACA,uDAOA;AAAA;AAAA;AAAA,wBAIA,SACE,aAEF,aACI,UAEJ,aACI,+BACA,4BACA,2BACA,0BACA,uBACA,UAIF,sDACE,YACA,QACA,SAEA,cACA,iBACA,iBCjKJ,WACI,gBACA,+BACA,wBACA,cACA,iBACA,iBACA,yBAEA,2CACA,uDACA,+BACA,+BACA,4CACA,2CACA,4CACA,6DACA,gDACA,mDACA,iCACA,0BACA,0BACA,gDACA,mDACA,0BACA,0BACA,gCACA,0BACA,0BACA,gCACA,gCACA,gCACA,gCACA,2CACA,yBACA,yBACA,0BACA,6BACA,2CACA,0BACA,4BACA,2CACA,2CACA,0BACA,0BACA,0BACA,gCACA,yBACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,0BACA,6BACA,0BACA,6BACA,0BACA,0BACA,0BACA,0BACA","sourcesContent":["@charset \"utf-8\";\n/* TOC – Typography variables\n\nModular Scale › http://www.modularscale.com//?16,36&px&1.25&web&table\n\n- Fonts\n- Font Weight\n- Font Size Variables\n\n*/\n\n@import \"functions\"; // Allows the use of rem-calc() or lower-bound() in your settings\n\n\n\n/* Fonts\n------------------------------------------------------------------- */\n\n$base-font-size: 16px;\n$rem-base: $base-font-size;\n// $base-line-height is 24px while $base-font-size is 16px\n$base-line-height: 1.5 !default;\n\n\n$font-family-sans-serif: \"Lato\", \"Helvetica Neue\", Helvetica, Arial, sans-serif;\n$font-family-serif: \"Volkhov\", Georgia, Times, serif;\n$font-family-monospace: \"Lucida Console\", Monaco, monospace;\n\n$body-font-family: $font-family-sans-serif;\n$body-font-weight: normal;\n$body-font-style: normal;\n\n$header-font-family: $font-family-serif;\n\n\n\n/* Font Weight\n------------------------------------------------------------------- */\n\n$font-weight-normal: normal;\n$font-weight-bold: bold;\n\n\n\n/* Font Size Variables\n------------------------------------------------------------------- */\n\n$font-size-p:    \t$base-font-size;\n$font-size-h1:      2.441em;\n$font-size-h2:      1.953em;\n$font-size-h3:      1.563em;\n$font-size-h4:      1.25em;\n$font-size-h5:      1.152em;\n$font-size-small:   0.8em;\n\n.font-size-h1   { font-size: $font-size-h1; }\n.font-size-h2   { font-size: $font-size-h2; }\n.font-size-h3   { font-size: $font-size-h3; }\n.font-size-h4   { font-size: $font-size-h4; }\n.font-size-h5   { font-size: $font-size-h5; }\n","@charset \"utf-8\";\n// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n//\n// Foundation Variables\n//\n\n// Data attribute namespace\n// styles get applied to [data-mysite-plugin], etc\n$namespace: false !default;\n\n// The default font-size is set to 100% of the browser style sheet (usually 16px)\n// for compatibility with browser-based text zoom or user-set defaults.\n\n// Since the typical default browser font-size is 16px, that makes the calculation for grid size.\n// If you want your base font-size to be different and not have it affect the grid breakpoints,\n// set $rem-base to $base-font-size and make sure $base-font-size is a px value.\n$base-font-size: 100% !default;\n\n\n\n//\n// Global Foundation Mixins\n//\n\n// @mixins\n//\n// We use this to control border radius.\n// $radius - Default: $global-radius || 4px\n@mixin radius($radius: $global-radius) {\n  @if $radius {\n    border-radius: $radius;\n  }\n}\n\n// @mixins\n//\n// We use this to create equal side border radius on elements.\n// $side - Options: left, right, top, bottom\n@mixin side-radius($side, $radius: $global-radius) {\n  @if ($side ==left or $side ==right) {\n    -webkit-border-bottom-#{$side}-radius: $radius;\n    -webkit-border-top-#{$side}-radius: $radius;\n    border-bottom-#{$side}-radius: $radius;\n    border-top-#{$side}-radius: $radius;\n  }\n\n  @else {\n    -webkit-#{$side}-left-radius: $radius;\n    -webkit-#{$side}-right-radius: $radius;\n    border-#{$side}-left-radius: $radius;\n    border-#{$side}-right-radius: $radius;\n  }\n}\n\n// @mixins\n//\n// We can control whether or not we have inset shadows edges.\n// $active - Default: true, Options: false\n@mixin inset-shadow($active: true) {\n  box-shadow: $shiny-edge-size $shiny-edge-color inset;\n\n  @if $active {\n    &:active {\n      box-shadow: $shiny-edge-size $shiny-edge-active-color inset;\n    }\n  }\n}\n\n// @mixins\n//\n// We use this to add transitions to elements\n// $property - Default: all, Options: http://www.w3.org/TR/css3-transitions/#animatable-properties\n// $speed - Default: 300ms\n// $ease - Default:ease-out, Options: http://css-tricks.com/almanac/properties/t/transition-timing-function/\n@mixin single-transition($property: all, $speed: 300ms, $ease: ease-out) {\n  transition: $property $speed $ease;\n}\n\n// @mixins\n//\n// We use this to add box-sizing across browser prefixes\n@mixin box-sizing($type: border-box) {\n  -webkit-box-sizing: $type; // Android < 2.3, iOS < 4\n  -moz-box-sizing: $type; // Firefox < 29\n  box-sizing: $type; // Chrome, IE 8+, Opera, Safari 5.1\n}\n\n// @mixins\n//\n// We use this to create isosceles triangles\n// $triangle-size - Used to set border-size. No default, set a px or em size.\n// $triangle-color - Used to set border-color which makes up triangle. No default\n// $triangle-direction - Used to determine which direction triangle points. Options: top, bottom, left, right\n@mixin css-triangle($triangle-size, $triangle-color, $triangle-direction) {\n  content: \"\";\n  display: block;\n  width: 0;\n  height: 0;\n  border: inset $triangle-size;\n\n  @if ($triangle-direction ==top) {\n    border-color: $triangle-color transparent transparent transparent;\n    border-top-style: solid;\n  }\n\n  @if ($triangle-direction ==bottom) {\n    border-color: transparent transparent $triangle-color transparent;\n    border-bottom-style: solid;\n  }\n\n  @if ($triangle-direction ==left) {\n    border-color: transparent transparent transparent $triangle-color;\n    border-left-style: solid;\n  }\n\n  @if ($triangle-direction ==right) {\n    border-color: transparent $triangle-color transparent transparent;\n    border-right-style: solid;\n  }\n}\n\n// @mixins\n//\n// We use this to create the icon with three lines aka the hamburger icon, the menu-icon or the navicon\n// $width - Width of hamburger icon in rem\n// $left - If false, icon will be centered horizontally || explicitly set value in rem\n// $top - If false, icon will be centered vertically || explicitly set value in rem\n// $thickness - thickness of lines in hamburger icon, set value in px\n// $gap - spacing between the lines in hamburger icon, set value in px\n// $color - icon color\n// $hover-color - icon color during hover\n// $offcanvas - Set to true of @include in offcanvas\n@mixin hamburger($width, $left, $top, $thickness, $gap, $color, $hover-color, $offcanvas) {\n  span::after {\n    content: \"\";\n    position: absolute;\n    display: block;\n    height: 0;\n\n    @if $offcanvas {\n      @if $top {\n        top: $top;\n      }\n\n      @else {\n        top: 50%;\n        margin-top: (-$width/2);\n      }\n\n      @if $left {\n        left: $left;\n      }\n\n      @else {\n        left: ($tabbar-menu-icon-width - $width)/2;\n      }\n    }\n\n    @else {\n      top: 50%;\n      margin-top: -($width/2);\n      #{$opposite-direction}: $topbar-link-padding;\n    }\n\n    box-shadow: 0 0 0 $thickness $color,\n    0 ($gap + $thickness) 0 $thickness $color,\n    0 (2 * $gap + 2*$thickness) 0 $thickness $color;\n    width: $width;\n  }\n\n  span:hover:after {\n    box-shadow:\n      0 0 0 $thickness $hover-color,\n      0 $gap + $thickness 0 $thickness $hover-color,\n      0 (2 * $gap + 2*$thickness) 0 $thickness $hover-color;\n  }\n}\n\n// We use this to do clear floats\n@mixin clearfix {\n\n  &:before,\n  &:after {\n    content: \" \";\n    display: table;\n  }\n\n  &:after {\n    clear: both;\n  }\n}\n\n// @mixins\n//\n// We use this to add a glowing effect to block elements\n// $selector - Used for selector state. Default: focus, Options: hover, active, visited\n// $fade-time - Default: 300ms\n// $glowing-effect-color - Default: fade-out($primary-color, .25)\n@mixin block-glowing-effect($selector: focus, $fade-time: 300ms, $glowing-effect-color: fade-out($primary-color, .25)) {\n  transition: box-shadow $fade-time, border-color $fade-time ease-in-out;\n\n  &:#{$selector} {\n    box-shadow: 0 0 5px $glowing-effect-color;\n    border-color: $glowing-effect-color;\n  }\n}\n\n// @mixins\n//\n// We use this to translate elements in 2D\n// $horizontal: Default: 0\n// $vertical: Default: 0\n@mixin translate2d($horizontal: 0, $vertical: 0) {\n  transform: translate($horizontal, $vertical)\n}\n\n// @mixins\n//\n// Makes an element visually hidden, but accessible.\n// @see http://snook.ca/archives/html_and_css/hiding-content-for-accessibility\n@mixin element-invisible {\n  position: absolute !important;\n  height: 1px;\n  width: 1px;\n  overflow: hidden;\n  clip: rect(1px, 1px, 1px, 1px);\n}\n\n// @mixins\n//\n// Turns off the element-invisible effect.\n@mixin element-invisible-off {\n  position: static !important;\n  height: auto;\n  width: auto;\n  overflow: visible;\n  clip: auto;\n}\n\n\n// We use these to control text direction settings\n$text-direction: ltr !default;\n$default-float: left !default;\n$opposite-direction: right !default;\n\n@if $text-direction ==ltr {\n  $default-float: left;\n  $opposite-direction: right;\n}\n\n@else {\n  $default-float: right;\n  $opposite-direction: left;\n}\n\n// We use these to control inset shadow shiny edges and depressions.\n$shiny-edge-size: 0 1px 0 !default;\n$shiny-edge-color: rgba(#fff, .5) !default;\n$shiny-edge-active-color: rgba(#000, .2) !default;\n\n// We use this to control whether or not CSS classes come through in the gem files.\n$include-html-classes: true !default;\n$include-print-styles: true !default;\n$include-html-global-classes: $include-html-classes !default;\n\n$column-gutter: rem-calc(30) !default;\n\n\n\n\n// d. Media Query Ranges\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n$small-range: (\n  0em,\n  40em\n);\n$medium-range: (\n  40.063em,\n  64em\n);\n$large-range: (\n  64.063em,\n  90em\n);\n$xlarge-range: (\n  90.063em,\n  120em\n);\n$xxlarge-range: (\n  120.063em,\n  99999999em\n);\n\n\n$screen: \"only screen\" !default;\n\n$landscape: \"#{$screen} and (orientation: landscape)\" !default;\n$portrait: \"#{$screen} and (orientation: portrait)\" !default;\n\n$small-up: $screen !default;\n$small-only: \"#{$screen} and (max-width: #{upper-bound($small-range)})\";\n\n$medium-up: \"#{$screen} and (min-width:#{lower-bound($medium-range)})\" !default;\n$medium-only: \"#{$screen} and (min-width:#{lower-bound($medium-range)}) and (max-width:#{upper-bound($medium-range)})\" !default;\n\n$large-up: \"#{$screen} and (min-width:#{lower-bound($large-range)})\" !default;\n$large-only: \"#{$screen} and (min-width:#{lower-bound($large-range)}) and (max-width:#{upper-bound($large-range)})\" !default;\n\n$xlarge-up: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)})\" !default;\n$xlarge-only: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)}) and (max-width:#{upper-bound($xlarge-range)})\" !default;\n\n$xxlarge-up: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)})\" !default;\n$xxlarge-only: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)}) and (max-width:#{upper-bound($xxlarge-range)})\" !default;\n\n// Legacy\n$small: $medium-up;\n$medium: $medium-up;\n$large: $large-up;\n\n//We use this as cursors values for enabling the option of having custom cursors in the whole site's stylesheet\n$cursor-auto-value: auto !default;\n$cursor-crosshair-value: crosshair !default;\n$cursor-default-value: default !default;\n$cursor-pointer-value: pointer !default;\n$cursor-help-value: help !default;\n$cursor-text-value: text !default;\n\n\n@include exports(\"global\") {\n\n  // Meta styles are included in all builds, as they are a dependency of the Javascript.\n  // Used to provide media query values for javascript components.\n  // Forward slash placed around everything to convince PhantomJS to read the value.\n\n  meta.foundation-version {\n    font-family: \"/5.5.0/\";\n  }\n\n  meta.foundation-mq-small {\n    font-family: \"/\" + unquote($small-up) + \"/\";\n    width: lower-bound($small-range);\n  }\n\n  meta.foundation-mq-small-only {\n    font-family: \"/\" + unquote($small-only) + \"/\";\n    width: lower-bound($small-range);\n  }\n\n  meta.foundation-mq-medium {\n    font-family: \"/\" + unquote($medium-up) + \"/\";\n    width: lower-bound($medium-range);\n  }\n\n  meta.foundation-mq-medium-only {\n    font-family: \"/\" + unquote($medium-only) + \"/\";\n    width: lower-bound($medium-range);\n  }\n\n  meta.foundation-mq-large {\n    font-family: \"/\" + unquote($large-up) + \"/\";\n    width: lower-bound($large-range);\n  }\n\n  meta.foundation-mq-large-only {\n    font-family: \"/\" + unquote($large-only) + \"/\";\n    width: lower-bound($large-range);\n  }\n\n  meta.foundation-mq-xlarge {\n    font-family: \"/\" + unquote($xlarge-up) + \"/\";\n    width: lower-bound($xlarge-range);\n  }\n\n  meta.foundation-mq-xlarge-only {\n    font-family: \"/\" + unquote($xlarge-only) + \"/\";\n    width: lower-bound($xlarge-range);\n  }\n\n  meta.foundation-mq-xxlarge {\n    font-family: \"/\" + unquote($xxlarge-up) + \"/\";\n    width: lower-bound($xxlarge-range);\n  }\n\n  meta.foundation-data-attribute-namespace {\n    font-family: #{$namespace};\n  }\n\n  @if $include-html-global-classes {\n\n    // Must be 100% for off canvas to work\n    html,\n    body {\n      height: 100%;\n    }\n\n    // Set box-sizing globally to handle padding and border widths\n    *,\n    *:before,\n    *:after {\n      @include box-sizing(border-box);\n    }\n\n    html,\n    body {\n      font-size: $base-font-size;\n    }\n\n    // Default body styles\n    body {\n      background: $body-bg;\n      color: $body-font-color;\n      padding: 0;\n      margin: 0;\n      font-family: $body-font-family;\n      font-weight: $body-font-weight;\n      font-style: $body-font-style;\n      line-height: $base-line-height; // Set to $base-line-height to take on browser default of 150%\n      position: relative;\n      cursor: $cursor-auto-value;\n    }\n\n    a:hover {\n      cursor: $cursor-pointer-value;\n    }\n\n    // Grid Defaults to get images and embeds to work properly\n    img {\n      max-width: 100%;\n      height: auto;\n    }\n\n    img {\n      -ms-interpolation-mode: bicubic;\n    }\n\n    #map_canvas,\n    .map_canvas {\n\n      img,\n      embed,\n      object {\n        max-width: none !important;\n      }\n    }\n\n    // Miscellaneous useful HTML classes\n    .left {\n      float: left !important;\n    }\n\n    .right {\n      float: right !important;\n    }\n\n    .clearfix {\n      @include clearfix;\n    }\n\n    // Hide visually and from screen readers\n    .hide {\n      display: none !important;\n      visibility: hidden;\n    }\n\n    // Hide visually and from screen readers, but maintain layout\n    .invisible {\n      visibility: hidden;\n    }\n\n    // Font smoothing\n    // Antialiased font smoothing works best for light text on a dark background.\n    // Apply to single elements instead of globally to body.\n    // Note this only applies to webkit-based desktop browsers and Firefox 25 (and later) on the Mac.\n    .antialiased {\n      -webkit-font-smoothing: antialiased;\n      -moz-osx-font-smoothing: grayscale;\n    }\n\n    // Get rid of gap under images by making them display: inline-block; by default\n    img {\n      display: inline-block;\n      vertical-align: middle;\n    }\n\n    //\n    // Global resets for forms\n    //\n\n    // Make sure textarea takes on height automatically\n    textarea {\n      height: auto;\n      min-height: 50px;\n    }\n\n    // Make select elements 100% width by default\n    select {\n      width: 100%;\n    }\n  }\n}","@charset \"utf-8\";\n/* TOC – Color Variables\n\n- Basics\n- Corporate Identity Colorpalette\n- Foundation Color Variables\n- Grey Scale\n- Topbar-Navigation\n- Footer\n- Code\n\n*/\n\n\n\n/* Basics\n------------------------------------------------------------------- */\n\n$text-color         : #111;\n$body-font-color    : $text-color;\n$body-bg            : #fdfdfd;\n\n\n\n/* Corporate Identity Colorpalette\n   https://color.adobe.com/de/Flat-Design-Colors-v2-color-theme-4341903/\n------------------------------------------------------------------- */\n\n$ci-1               : #334D5C; // dark turquoise\n$ci-2               : #45B29D; // turquoise\n$ci-3               : #EFC94C; // yellow\n$ci-4               : #be6409; // dark orange\n$ci-5               : #DF4949; // red\n$ci-6               : #A1D044; // green\n\n\n\n/* Foundation Color Variables\n------------------------------------------------------------------- */\n\n$primary-color      : $ci-1;\n$secondary-color    : $ci-6;\n$alert-color        : $ci-5;\n$success-color      : $ci-6;\n$warning-color      : $ci-4;\n$info-color         : $ci-1;\n\n\n\n/* Grey Scale\n------------------------------------------------------------------- */\n\n$grey-1             : #E4E4E4;\n$grey-2             : #D7D7D7;\n$grey-3             : #CBCBCB;\n$grey-4             : #BEBEBE;\n$grey-5             : #A4A4A4;\n$grey-6             : #979797;\n$grey-7             : #8B8B8B;\n$grey-8             : #7E7E7E;\n$grey-9             : #646464;\n$grey-10            : #575757;\n$grey-11            : #4B4B4B;\n$grey-12            : #3E3E3E;\n$grey-13            : #313131;\n$grey-14            : #242424;\n$grey-15            : #171717;\n$grey-16            : #0B0B0B;\n\n\n\n/* Topbar-Navigation\n------------------------------------------------------------------- */\n\n$topbar-bg-color    : $body-bg;\n$topbar-bg          : $topbar-bg-color;\n\n\n$topbar-dropdown-toggle-color: $ci-1;\n\n$topbar-link-color  : #000;\n$topbar-link-color-hover: #000;\n$topbar-link-color-active: #000;\n$topbar-link-color-active-hover: #000;\n\n$topbar-dropdown-label-color: $ci-2;\n$topbar-dropdown-link-bg-hover: $ci-6;\n\n$topbar-link-bg-active: $ci-6; // Active Navigation Link\n$topbar-link-bg-hover: $ci-6;\n$topbar-link-bg-active-hover: $ci-2;\n\n\n$topbar-dropdown-bg: $ci-6; // Background Mobile Navigation\n$topbar-dropdown-link-color: #000;\n$topbar-dropdown-link-bg: $ci-2;\n\n$topbar-menu-link-color-toggled: $ci-1;\n$topbar-menu-icon-color-toggled: $ci-1;\n$topbar-menu-link-color: #000;\n$topbar-menu-icon-color: #000;\n$topbar-menu-link-color-toggled: $ci-6;\n$topbar-menu-icon-color-toggled: $ci-6;\n\n\n\n/* Footer\n------------------------------------------------------------------- */\n\n$footer-bg          : $grey-8;\n$footer-color       : #fff;\n$footer-link-color  : $ci-6;\n\n\n$subfooter-bg       : $grey-13;\n$subfooter-color    : $grey-8;\n$subfooter-link-color: $grey-8;\n\n\n\n/* Code\n------------------------------------------------------------------- */\n\n$code-background-color: scale-color($secondary-color, $lightness: 70%);\n\n$highlight-background: #ffffff;\n$highlight-comment: #999988;\n$highlight-error: #a61717;\n$highlight-comment-special: #999999;\n$highlight-deleted: #000000;\n$highlight-error-2: #aa0000;\n$highlight-literal-string: #d14;\n$highlight-literal-number: #009999;\n$highlight-name-attribut: #008080;\n$highlight-error-background: #e3d2d2;\n$highlight-generic-deleted: #ffdddd;\n$highlight-generic-deleted-specific: #ffaaaa;\n$highlight-generic-inserted: #ddffdd;\n$highlight-generic-inserted-specific: #aaffaa;\n$highlight-generic-output: #888888;\n$highlight-generic-prompt: #555555;\n$highlight-subheading: #aaaaaa;\n$highlight-keyword-type: #445588;\n$highlight-name-builtin: #0086B3;\n$highlight-name-class: #445588;\n$highlight-name-entity: #800080;\n$highlight-name-exception: #990000;\n$highlight-name-function: #990000;\n$highlight-name-namespace: #555555;\n$highlight-name-tag: #000080;\n$highlight-text-whitespace: #bbbbbb;\n$highlight-literal-string-regex: #009926;\n$highlight-literal-string-symbol: #990073;\n\n\n/* links\n------------------------------------------------------------------- */\n$link-unvisited: #0921e2;\n$link-visited: #071582;\n$link-hover: darken( $link-unvisited, 10% );\n$link-focus: lighten( $link-unvisited, 20% );\n$link-active: darken( $link-unvisited, 20% );\n","@charset \"utf-8\";\n/*! normalize.css v3.0.2 | MIT License | git.io/normalize */\n\n/**\n * 1. Set default font family to sans-serif.\n * 2. Prevent iOS text size adjust after orientation change, without disabling\n *    user zoom.\n */\n\nhtml {\n  font-family: sans-serif; /* 1 */\n  -ms-text-size-adjust: 100%; /* 2 */\n  -webkit-text-size-adjust: 100%; /* 2 */\n}\n\n/**\n * Remove default margin.\n */\n\nbody {\n  margin: 0;\n}\n\n/* HTML5 display definitions\n   ========================================================================== */\n\n/**\n * Correct `block` display not defined for any HTML5 element in IE 8/9.\n * Correct `block` display not defined for `details` or `summary` in IE 10/11\n * and Firefox.\n * Correct `block` display not defined for `main` in IE 11.\n */\n\narticle,\naside,\ndetails,\nfigcaption,\nfigure,\nfooter,\nheader,\nhgroup,\nmain,\nmenu,\nnav,\nsection,\nsummary {\n  display: block;\n}\n\n/**\n * 1. Correct `inline-block` display not defined in IE 8/9.\n * 2. Normalize vertical alignment of `progress` in Chrome, Firefox, and Opera.\n */\n\naudio,\ncanvas,\nprogress,\nvideo {\n  display: inline-block; /* 1 */\n  vertical-align: baseline; /* 2 */\n}\n\n/**\n * Prevent modern browsers from displaying `audio` without controls.\n * Remove excess height in iOS 5 devices.\n */\n\naudio:not([controls]) {\n  display: none;\n  height: 0;\n}\n\n/**\n * Address `[hidden]` styling not present in IE 8/9/10.\n * Hide the `template` element in IE 8/9/11, Safari, and Firefox < 22.\n */\n\n[hidden],\ntemplate {\n  display: none;\n}\n\n/* Links\n   ========================================================================== */\n\n/**\n * Remove the gray background color from active links in IE 10.\n */\n\na {\n  background-color: transparent;\n}\n\n/**\n * Improve readability when focused and also mouse hovered in all browsers.\n */\n\na:active,\na:hover {\n  outline: 0;\n}\n\n/* Text-level semantics\n   ========================================================================== */\n\n/**\n * Address styling not present in IE 8/9/10/11, Safari, and Chrome.\n */\n\nabbr[title] {\n  border-bottom: 1px dotted;\n}\n\n/**\n * Address style set to `bolder` in Firefox 4+, Safari, and Chrome.\n */\n\nb,\nstrong {\n  font-weight: bold;\n}\n\n/**\n * Address styling not present in Safari and Chrome.\n */\n\ndfn {\n  font-style: italic;\n}\n\n/**\n * Address variable `h1` font-size and margin within `section` and `article`\n * contexts in Firefox 4+, Safari, and Chrome.\n */\n\nh1 {\n  font-size: 2em;\n  margin: 0.67em 0;\n}\n\n/**\n * Address styling not present in IE 8/9.\n */\n\nmark {\n  background: #ff0;\n  color: #000;\n}\n\n/**\n * Address inconsistent and variable font size in all browsers.\n */\n\nsmall {\n  font-size: 80%;\n}\n\n/**\n * Prevent `sub` and `sup` affecting `line-height` in all browsers.\n */\n\nsub,\nsup {\n  font-size: 75%;\n  line-height: 0;\n  position: relative;\n  vertical-align: baseline;\n}\n\nsup {\n  top: -0.5em;\n}\n\nsub {\n  bottom: -0.25em;\n}\n\n/* Embedded content\n   ========================================================================== */\n\n/**\n * Remove border when inside `a` element in IE 8/9/10.\n */\n\nimg {\n  border: 0;\n}\n\n/**\n * Correct overflow not hidden in IE 9/10/11.\n */\n\nsvg:not(:root) {\n  overflow: hidden;\n}\n\n/* Grouping content\n   ========================================================================== */\n\n/**\n * Address margin not present in IE 8/9 and Safari.\n */\n\nfigure {\n  margin: 1em 40px;\n}\n\n/**\n * Address differences between Firefox and other browsers.\n */\n\nhr {\n  -moz-box-sizing: content-box;\n  box-sizing: content-box;\n  height: 0;\n}\n\n/**\n * Contain overflow in all browsers.\n */\n\npre {\n  overflow: auto;\n}\n\n/**\n * Address odd `em`-unit font size rendering in all browsers.\n */\n\ncode,\nkbd,\npre,\nsamp {\n  font-family: monospace, monospace;\n  font-size: 1em;\n}\n\n/* Forms\n   ========================================================================== */\n\n/**\n * Known limitation: by default, Chrome and Safari on OS X allow very limited\n * styling of `select`, unless a `border` property is set.\n */\n\n/**\n * 1. Correct color not being inherited.\n *    Known issue: affects color of disabled elements.\n * 2. Correct font properties not being inherited.\n * 3. Address margins set differently in Firefox 4+, Safari, and Chrome.\n */\n\nbutton,\ninput,\noptgroup,\nselect,\ntextarea {\n  color: inherit; /* 1 */\n  font: inherit; /* 2 */\n  margin: 0; /* 3 */\n}\n\n/**\n * Address `overflow` set to `hidden` in IE 8/9/10/11.\n */\n\nbutton {\n  overflow: visible;\n}\n\n/**\n * Address inconsistent `text-transform` inheritance for `button` and `select`.\n * All other form control elements do not inherit `text-transform` values.\n * Correct `button` style inheritance in Firefox, IE 8/9/10/11, and Opera.\n * Correct `select` style inheritance in Firefox.\n */\n\nbutton,\nselect {\n  text-transform: none;\n}\n\n/**\n * 1. Avoid the WebKit bug in Android 4.0.* where (2) destroys native `audio`\n *    and `video` controls.\n * 2. Correct inability to style clickable `input` types in iOS.\n * 3. Improve usability and consistency of cursor style between image-type\n *    `input` and others.\n */\n\nbutton,\nhtml input[type=\"button\"], /* 1 */\ninput[type=\"reset\"],\ninput[type=\"submit\"] {\n  -webkit-appearance: button; /* 2 */\n  cursor: pointer; /* 3 */\n}\n\n/**\n * Re-set default cursor for disabled elements.\n */\n\nbutton[disabled],\nhtml input[disabled] {\n  cursor: default;\n}\n\n/**\n * Remove inner padding and border in Firefox 4+.\n */\n\nbutton::-moz-focus-inner,\ninput::-moz-focus-inner {\n  border: 0;\n  padding: 0;\n}\n\n/**\n * Address Firefox 4+ setting `line-height` on `input` using `!important` in\n * the UA stylesheet.\n */\n\ninput {\n  line-height: normal;\n}\n\n/**\n * It's recommended that you don't attempt to style these elements.\n * Firefox's implementation doesn't respect box-sizing, padding, or width.\n *\n * 1. Address box sizing set to `content-box` in IE 8/9/10.\n * 2. Remove excess padding in IE 8/9/10.\n */\n\ninput[type=\"checkbox\"],\ninput[type=\"radio\"] {\n  box-sizing: border-box; /* 1 */\n  padding: 0; /* 2 */\n}\n\n/**\n * Fix the cursor style for Chrome's increment/decrement buttons. For certain\n * `font-size` values of the `input`, it causes the cursor style of the\n * decrement button to change from `default` to `text`.\n */\n\ninput[type=\"number\"]::-webkit-inner-spin-button,\ninput[type=\"number\"]::-webkit-outer-spin-button {\n  height: auto;\n}\n\n/**\n * 1. Address `appearance` set to `searchfield` in Safari and Chrome.\n * 2. Address `box-sizing` set to `border-box` in Safari and Chrome\n *    (include `-moz` to future-proof).\n */\n\ninput[type=\"search\"] {\n  -webkit-appearance: textfield; /* 1 */\n  -moz-box-sizing: content-box;\n  -webkit-box-sizing: content-box; /* 2 */\n  box-sizing: content-box;\n}\n\n/**\n * Remove inner padding and search cancel button in Safari and Chrome on OS X.\n * Safari (but not Chrome) clips the cancel button when the search input has\n * padding (and `textfield` appearance).\n */\n\ninput[type=\"search\"]::-webkit-search-cancel-button,\ninput[type=\"search\"]::-webkit-search-decoration {\n  -webkit-appearance: none;\n}\n\n/**\n * Define consistent border, margin, and padding.\n */\n\nfieldset {\n  border: 1px solid #c0c0c0;\n  margin: 0 2px;\n  padding: 0.35em 0.625em 0.75em;\n}\n\n/**\n * 1. Correct `color` not being inherited in IE 8/9/10/11.\n * 2. Remove padding so people aren't caught out if they zero out fieldsets.\n */\n\nlegend {\n  border: 0; /* 1 */\n  padding: 0; /* 2 */\n}\n\n/**\n * Remove default vertical scrollbar in IE 8/9/10/11.\n */\n\ntextarea {\n  overflow: auto;\n}\n\n/**\n * Don't inherit the `font-weight` (applied by a rule above).\n * NOTE: the default cannot safely be changed in Chrome and Safari on OS X.\n */\n\noptgroup {\n  font-weight: bold;\n}\n\n/* Tables\n   ========================================================================== */\n\n/**\n * Remove most spacing between table cells.\n */\n\ntable {\n  border-collapse: collapse;\n  border-spacing: 0;\n}\n\ntd,\nth {\n  padding: 0;\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-grid-classes: $include-html-classes !default;\n$include-xl-html-grid-classes: false !default;\n\n$row-width: rem-calc(1500) !default;\n$total-columns: 12 !default;\n\n$last-child-float: $opposite-direction !default;\n\n//\n// Grid Functions\n//\n\n// Deprecated: We'll drop support for this in 5.1, use grid-calc()\n@function gridCalc($colNumber, $totalColumns) {\n  @warn \"gridCalc() is deprecated, use grid-calc()\";\n  @return grid-calc($colNumber, $totalColumns);\n}\n\n// @FUNCTION\n// $colNumber - Found in settings file\n// $totalColumns - Found in settings file\n@function grid-calc($colNumber, $totalColumns) {\n  @return percentage(calc($colNumber / $totalColumns));\n}\n\n//\n// @mixins\n//\n\n// For creating container, nested, and collapsed rows.\n//\n//\n// $behavior - Any special behavior for this row? Default: false. Options: nest, collapse, nest-collapse, false.\n@mixin grid-row($behavior: false) {\n\n  // use @include grid-row(nest); to include a nested row\n  @if $behavior ==nest {\n    width: auto;\n    margin-#{$default-float}: - calc($column-gutter/2);\n    margin-#{$opposite-direction}: - calc($column-gutter/2);\n    margin-top: 0;\n    margin-bottom: 0;\n    max-width: none;\n  }\n\n  // use @include grid-row(collapse); to collapsed a container row margins\n  @else if $behavior ==collapse {\n    width: 100%;\n    margin: 0;\n    max-width: $row-width;\n  }\n\n  // use @include grid-row(nest-collapse); to collapse outer margins on a nested row\n  @else if $behavior ==nest-collapse {\n    width: auto;\n    margin: 0;\n    max-width: none;\n  }\n\n  // use @include grid-row; to use a container row\n  @else {\n    width: 100%;\n    margin-#{$default-float}: auto;\n    margin-#{$opposite-direction}: auto;\n    margin-top: 0;\n    margin-bottom: 0;\n    max-width: $row-width;\n  }\n\n  // Clearfix for all rows\n  @include clearfix();\n}\n\n// Creates a column, should be used inside of a media query to control layouts\n//\n// $columns - The number of columns this should be\n// $last-column - Is this the last column? Default: false.\n// $center - Center these columns? Default: false.\n// $offset - # of columns to offset. Default: false.\n// $push - # of columns to push. Default: false.\n// $pull - # of columns to pull. Default: false.\n// $collapse - Get rid of gutter padding on column? Default: false.\n// $float - Should this float? Default: true. Options: true, false, left, right.\n@mixin grid-column($columns: false,\n  $last-column: false,\n  $center: false,\n  $offset: false,\n  $push: false,\n  $pull: false,\n  $collapse: false,\n  $float: true,\n  $position: false) {\n\n  // If positioned for default .column, include relative position\n  // push and pull require position set\n  @if $position or $push or $pull {\n    position: relative;\n  }\n\n  // If collapsed, get rid of gutter padding\n  @if $collapse {\n    padding-left: 0;\n    padding-right: 0;\n  }\n\n  // Gutter padding whenever a column isn't set to collapse\n  // (use $collapse:null to do nothing)\n  @else if $collapse ==false {\n    padding-left: calc($column-gutter / 2);\n    padding-right: calc($column-gutter / 2);\n  }\n\n  // If a column number is given, calculate width\n  @if $columns {\n    width: grid-calc($columns, $total-columns);\n\n    // If last column, float naturally instead of to the right\n    @if $last-column {\n      float: $opposite-direction;\n    }\n  }\n\n  // Source Ordering, adds left/right depending on which you use.\n  @if $push {\n    #{$default-float}: grid-calc($push, $total-columns);\n    #{$opposite-direction}: auto;\n  }\n\n  @if $pull {\n    #{$opposite-direction}: grid-calc($pull, $total-columns);\n    #{$default-float}: auto;\n  }\n\n  @if $float {\n    @if $float ==left or $float ==true {\n      float: $default-float;\n    }\n\n    @else if $float ==right {\n      float: $opposite-direction;\n    }\n\n    @else {\n      float: none;\n    }\n  }\n\n  // If centered, get rid of float and add appropriate margins\n  @if $center {\n    margin-#{$default-float}: auto;\n    margin-#{$opposite-direction}: auto;\n    float: none;\n  }\n\n  // If offset, calculate appropriate margins\n  @if $offset {\n    margin-#{$default-float}: grid-calc($offset, $total-columns) !important;\n  }\n\n}\n\n// Create presentational classes for grid\n//\n// $size - Name of class to use, i.e. \"large\" will generate .large-1, .large-2, etc.\n@mixin grid-html-classes($size) {\n\n  @for $i from 0 through $total-columns - 1 {\n    .#{$size}-push-#{$i} {\n      @include grid-column($push: $i, $collapse: null, $float: false);\n    }\n\n    .#{$size}-pull-#{$i} {\n      @include grid-column($pull: $i, $collapse: null, $float: false);\n    }\n  }\n\n  .column,\n  .columns {\n    @include grid-column($columns: false, $position: true);\n  }\n\n\n  @for $i from 1 through $total-columns {\n    .#{$size}-#{$i} {\n      @include grid-column($columns: $i, $collapse: null, $float: false);\n    }\n  }\n\n  @for $i from 0 through $total-columns - 1 {\n    .#{$size}-offset-#{$i} {\n      @include grid-column($offset: $i, $collapse: null, $float: false);\n    }\n  }\n\n  .#{$size}-reset-order {\n    margin-#{$default-float}: 0;\n    margin-#{$opposite-direction}: 0;\n    left: auto;\n    right: auto;\n    float: $default-float;\n  }\n\n  .column.#{$size}-centered,\n  .columns.#{$size}-centered {\n    @include grid-column($center: true, $collapse: null, $float: false);\n  }\n\n  .column.#{$size}-uncentered,\n  .columns.#{$size}-uncentered {\n    margin-#{$default-float}: 0;\n    margin-#{$opposite-direction}: 0;\n    float: $default-float;\n  }\n\n  // Fighting [class*=\"column\"] + [class*=\"column\"]:last-child\n  .column.#{$size}-centered:last-child,\n  .columns.#{$size}-centered:last-child {\n    float: none;\n  }\n\n  // Fighting .column.<previous-size>-centered:last-child\n  .column.#{$size}-uncentered:last-child,\n  .columns.#{$size}-uncentered:last-child {\n    float: $default-float;\n  }\n\n  .column.#{$size}-uncentered.opposite,\n  .columns.#{$size}-uncentered.opposite {\n    float: $opposite-direction;\n  }\n\n  .row {\n    &.#{$size}-collapse {\n\n      >.column,\n      >.columns {\n        @include grid-column($collapse: true, $float: false);\n      }\n\n      .row {\n        margin-left: 0;\n        margin-right: 0;\n      }\n    }\n\n    &.#{$size}-uncollapse {\n\n      >.column,\n      >.columns {\n        @include grid-column;\n      }\n    }\n  }\n}\n\n@include exports(\"grid\") {\n  @if $include-html-grid-classes {\n    .row {\n      @include grid-row;\n\n      &.collapse {\n\n        >.column,\n        >.columns {\n          @include grid-column($collapse: true, $float: false);\n        }\n\n        .row {\n          margin-left: 0;\n          margin-right: 0;\n        }\n      }\n\n      .row {\n        @include grid-row($behavior: nest);\n\n        &.collapse {\n          @include grid-row($behavior: nest-collapse);\n        }\n      }\n    }\n\n    .column,\n    .columns {\n      @include grid-column($columns: $total-columns);\n    }\n\n    [class*=\"column\"]+[class*=\"column\"]:last-child {\n      float: $last-child-float;\n    }\n\n    [class*=\"column\"]+[class*=\"column\"].end {\n      float: $default-float;\n    }\n\n    @media #{$small-up} {\n      @include grid-html-classes($size: small);\n    }\n\n    @media #{$medium-up} {\n      @include grid-html-classes($size: medium);\n\n      // Old push and pull classes\n      @for $i from 0 through $total-columns - 1 {\n        .push-#{$i} {\n          @include grid-column($push: $i, $collapse: null, $float: false);\n        }\n\n        .pull-#{$i} {\n          @include grid-column($pull: $i, $collapse: null, $float: false);\n        }\n      }\n    }\n\n    @media #{$large-up} {\n      @include grid-html-classes($size: large);\n\n      @for $i from 0 through $total-columns - 1 {\n        .push-#{$i} {\n          @include grid-column($push: $i, $collapse: null, $float: false);\n        }\n\n        .pull-#{$i} {\n          @include grid-column($pull: $i, $collapse: null, $float: false);\n        }\n      }\n    }\n  }\n\n  @if $include-xl-html-grid-classes {\n    @media #{$xlarge-up} {\n      @include grid-html-classes($size: xlarge);\n    }\n\n    @media #{$xxlarge-up} {\n      @include grid-html-classes($size: xxlarge);\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"../functions\";\n//\n// Foundation Variables\n//\n\n// Data attribute namespace\n// styles get applied to [data-mysite-plugin], etc\n$namespace: false !default;\n\n// The default font-size is set to 100% of the browser style sheet (usually 16px)\n// for compatibility with browser-based text zoom or user-set defaults.\n\n// Since the typical default browser font-size is 16px, that makes the calculation for grid size.\n// If you want your base font-size to be different and not have it affect the grid breakpoints,\n// set $rem-base to $base-font-size and make sure $base-font-size is a px value.\n$base-font-size: 100% !default;\n\n// $base-line-height is 24px while $base-font-size is 16px\n$base-line-height: 1.5 !default;\n\n//\n// Global Foundation Mixins\n//\n\n// @mixins\n//\n// We use this to control border radius.\n// $radius - Default: $global-radius || 4px\n@mixin radius($radius: $global-radius) {\n  @if $radius {\n    border-radius: $radius;\n  }\n}\n\n// @mixins\n//\n// We use this to create equal side border radius on elements.\n// $side - Options: left, right, top, bottom\n@mixin side-radius($side, $radius: $global-radius) {\n  @if ($side ==left or $side ==right) {\n    -webkit-border-bottom-#{$side}-radius: $radius;\n    -webkit-border-top-#{$side}-radius: $radius;\n    border-bottom-#{$side}-radius: $radius;\n    border-top-#{$side}-radius: $radius;\n  }\n\n  @else {\n    -webkit-#{$side}-left-radius: $radius;\n    -webkit-#{$side}-right-radius: $radius;\n    border-#{$side}-left-radius: $radius;\n    border-#{$side}-right-radius: $radius;\n  }\n}\n\n// @mixins\n//\n// We can control whether or not we have inset shadows edges.\n// $active - Default: true, Options: false\n@mixin inset-shadow($active: true) {\n  box-shadow: $shiny-edge-size $shiny-edge-color inset;\n\n  @if $active {\n    &:active {\n      box-shadow: $shiny-edge-size $shiny-edge-active-color inset;\n    }\n  }\n}\n\n// @mixins\n//\n// We use this to add transitions to elements\n// $property - Default: all, Options: http://www.w3.org/TR/css3-transitions/#animatable-properties\n// $speed - Default: 300ms\n// $ease - Default:ease-out, Options: http://css-tricks.com/almanac/properties/t/transition-timing-function/\n@mixin single-transition($property: all, $speed: 300ms, $ease: ease-out) {\n  transition: $property $speed $ease;\n}\n\n// @mixins\n//\n// We use this to add box-sizing across browser prefixes\n@mixin box-sizing($type: border-box) {\n  -webkit-box-sizing: $type; // Android < 2.3, iOS < 4\n  -moz-box-sizing: $type; // Firefox < 29\n  box-sizing: $type; // Chrome, IE 8+, Opera, Safari 5.1\n}\n\n// @mixins\n//\n// We use this to create isosceles triangles\n// $triangle-size - Used to set border-size. No default, set a px or em size.\n// $triangle-color - Used to set border-color which makes up triangle. No default\n// $triangle-direction - Used to determine which direction triangle points. Options: top, bottom, left, right\n@mixin css-triangle($triangle-size, $triangle-color, $triangle-direction) {\n  content: \"\";\n  display: block;\n  width: 0;\n  height: 0;\n  border: inset $triangle-size;\n\n  @if ($triangle-direction ==top) {\n    border-color: $triangle-color transparent transparent transparent;\n    border-top-style: solid;\n  }\n\n  @if ($triangle-direction ==bottom) {\n    border-color: transparent transparent $triangle-color transparent;\n    border-bottom-style: solid;\n  }\n\n  @if ($triangle-direction ==left) {\n    border-color: transparent transparent transparent $triangle-color;\n    border-left-style: solid;\n  }\n\n  @if ($triangle-direction ==right) {\n    border-color: transparent $triangle-color transparent transparent;\n    border-right-style: solid;\n  }\n}\n\n// @mixins\n//\n// We use this to create the icon with three lines aka the hamburger icon, the menu-icon or the navicon\n// $width - Width of hamburger icon in rem\n// $left - If false, icon will be centered horizontally || explicitly set value in rem\n// $top - If false, icon will be centered vertically || explicitly set value in rem\n// $thickness - thickness of lines in hamburger icon, set value in px\n// $gap - spacing between the lines in hamburger icon, set value in px\n// $color - icon color\n// $hover-color - icon color during hover\n// $offcanvas - Set to true of @include in offcanvas\n@mixin hamburger($width, $left, $top, $thickness, $gap, $color, $hover-color, $offcanvas) {\n  span::after {\n    content: \"\";\n    position: absolute;\n    display: block;\n    height: 0;\n\n    @if $offcanvas {\n      @if $top {\n        top: $top;\n      }\n\n      @else {\n        top: 50%;\n        margin-top: (-$width/2);\n      }\n\n      @if $left {\n        left: $left;\n      }\n\n      @else {\n        left: ($tabbar-menu-icon-width - $width)/2;\n      }\n    }\n\n    @else {\n      top: 50%;\n      margin-top: -(calc($width / 2));\n      #{$opposite-direction}: $topbar-link-padding;\n    }\n\n    box-shadow: 0 0 0 $thickness $color,\n    0 ($gap + $thickness) 0 $thickness $color,\n    0 (2 * $gap + 2*$thickness) 0 $thickness $color;\n    width: $width;\n  }\n\n  span:hover:after {\n    box-shadow:\n      0 0 0 $thickness $hover-color,\n      0 $gap + $thickness 0 $thickness $hover-color,\n      0 (2 * $gap + 2*$thickness) 0 $thickness $hover-color;\n  }\n}\n\n// We use this to do clear floats\n@mixin clearfix {\n\n  &:before,\n  &:after {\n    content: \" \";\n    display: table;\n  }\n\n  &:after {\n    clear: both;\n  }\n}\n\n// @mixins\n//\n// We use this to add a glowing effect to block elements\n// $selector - Used for selector state. Default: focus, Options: hover, active, visited\n// $fade-time - Default: 300ms\n// $glowing-effect-color - Default: fade-out($primary-color, .25)\n@mixin block-glowing-effect($selector: focus, $fade-time: 300ms, $glowing-effect-color: fade-out($primary-color, .25)) {\n  transition: box-shadow $fade-time, border-color $fade-time ease-in-out;\n\n  &:#{$selector} {\n    box-shadow: 0 0 5px $glowing-effect-color;\n    border-color: $glowing-effect-color;\n  }\n}\n\n// @mixins\n//\n// We use this to translate elements in 2D\n// $horizontal: Default: 0\n// $vertical: Default: 0\n@mixin translate2d($horizontal: 0, $vertical: 0) {\n  transform: translate($horizontal, $vertical)\n}\n\n// @mixins\n//\n// Makes an element visually hidden, but accessible.\n// @see http://snook.ca/archives/html_and_css/hiding-content-for-accessibility\n@mixin element-invisible {\n  position: absolute !important;\n  height: 1px;\n  width: 1px;\n  overflow: hidden;\n  clip: rect(1px, 1px, 1px, 1px);\n}\n\n// @mixins\n//\n// Turns off the element-invisible effect.\n@mixin element-invisible-off {\n  position: static !important;\n  height: auto;\n  width: auto;\n  overflow: visible;\n  clip: auto;\n}\n\n$white : #FFFFFF !default;\n$ghost : #FAFAFA !default;\n$snow : #F9F9F9 !default;\n$vapor : #F6F6F6 !default;\n$white-smoke : #F5F5F5 !default;\n$silver : #EFEFEF !default;\n$smoke : #EEEEEE !default;\n$gainsboro : #DDDDDD !default;\n$iron : #CCCCCC !default;\n$base : #AAAAAA !default;\n$aluminum : #999999 !default;\n$jumbo : #888888 !default;\n$monsoon : #777777 !default;\n$steel : #666666 !default;\n$charcoal : #555555 !default;\n$tuatara : #444444 !default;\n$oil : #333333 !default;\n$jet : #222222 !default;\n$black : #000000 !default;\n\n// We use these as default colors throughout\n$primary-color: #008CBA !default; // bondi-blue\n$secondary-color: #e7e7e7 !default; // white-lilac\n$alert-color: #f04124 !default; // cinnabar\n$success-color: #43AC6A !default; // sea-green\n$warning-color: #f08a24 !default; // carrot\n$info-color: #a0d3e8 !default; // cornflower\n\n// We use these to define default font stacks\n$font-family-sans-serif: \"Helvetica Neue\", Helvetica, Roboto, Arial, sans-serif !default;\n$font-family-serif: Georgia, Cambria, \"Times New Roman\", Times, serif !default;\n$font-family-monospace: Consolas, \"Liberation Mono\", Courier, monospace !default;\n\n// We use these to define default font weights\n$font-weight-normal: normal !default;\n$font-weight-bold: bold !default;\n\n// We use these to control various global styles\n$body-bg: #fff !default;\n$body-font-color: #222 !default;\n$body-font-family: $font-family-sans-serif !default;\n$body-font-weight: $font-weight-normal !default;\n$body-font-style: normal !default;\n\n// We use this to control font-smoothing\n$font-smoothing: antialiased !default;\n\n// We use these to control text direction settings\n$text-direction: ltr !default;\n$default-float: left !default;\n$opposite-direction: right !default;\n\n@if $text-direction ==ltr {\n  $default-float: left;\n  $opposite-direction: right;\n}\n\n@else {\n  $default-float: right;\n  $opposite-direction: left;\n}\n\n// We use these to make sure border radius matches unless we want it different.\n$global-radius: 3px !default;\n$global-rounded: 1000px !default;\n\n// We use these to control inset shadow shiny edges and depressions.\n$shiny-edge-size: 0 1px 0 !default;\n$shiny-edge-color: rgba(#fff, .5) !default;\n$shiny-edge-active-color: rgba(#000, .2) !default;\n\n// We use this to control whether or not CSS classes come through in the gem files.\n$include-html-classes: true !default;\n$include-print-styles: true !default;\n$include-html-global-classes: $include-html-classes !default;\n\n$column-gutter: rem-calc(30) !default;\n\n// Media Query Ranges\n$small-range: (\n  0,\n  40em) !default;\n$medium-range: (\n  40.063em,\n  64em) !default;\n$large-range: (\n  64.063em,\n  90em) !default;\n$xlarge-range: (\n  90.063em,\n  120em) !default;\n$xxlarge-range: (\n  120.063em,\n  99999999em) !default;\n\n\n$screen: \"only screen\" !default;\n\n$landscape: \"#{$screen} and (orientation: landscape)\" !default;\n$portrait: \"#{$screen} and (orientation: portrait)\" !default;\n\n$small-up: $screen !default;\n$small-only: \"#{$screen} and (max-width: #{upper-bound($small-range)})\" !default;\n\n$medium-up: \"#{$screen} and (min-width:#{lower-bound($medium-range)})\" !default;\n$medium-only: \"#{$screen} and (min-width:#{lower-bound($medium-range)}) and (max-width:#{upper-bound($medium-range)})\" !default;\n\n$large-up: \"#{$screen} and (min-width:#{lower-bound($large-range)})\" !default;\n$large-only: \"#{$screen} and (min-width:#{lower-bound($large-range)}) and (max-width:#{upper-bound($large-range)})\" !default;\n\n$xlarge-up: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)})\" !default;\n$xlarge-only: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)}) and (max-width:#{upper-bound($xlarge-range)})\" !default;\n\n$xxlarge-up: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)})\" !default;\n$xxlarge-only: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)}) and (max-width:#{upper-bound($xxlarge-range)})\" !default;\n\n// Legacy\n$small: $medium-up;\n$medium: $medium-up;\n$large: $large-up;\n\n\n//We use this as cursors values for enabling the option of having custom cursors in the whole site's stylesheet\n$cursor-auto-value: auto !default;\n$cursor-crosshair-value: crosshair !default;\n$cursor-default-value: default !default;\n$cursor-pointer-value: pointer !default;\n$cursor-help-value: help !default;\n$cursor-text-value: text !default;\n\n\n@include exports(\"global\") {\n\n  // Meta styles are included in all builds, as they are a dependency of the Javascript.\n  // Used to provide media query values for javascript components.\n  // Forward slash placed around everything to convince PhantomJS to read the value.\n\n  meta.foundation-version {\n    font-family: \"/5.5.0/\";\n  }\n\n  meta.foundation-mq-small {\n    font-family: \"/\" + unquote($small-up) + \"/\";\n    width: lower-bound($small-range\n    );\n}\n\nmeta.foundation-mq-small-only {\n  font-family: \"/\" + unquote($small-only) + \"/\";\n  width: lower-bound($small-range);\n}\n\nmeta.foundation-mq-medium {\n  font-family: \"/\" + unquote($medium-up) + \"/\";\n  width: lower-bound($medium-range);\n}\n\nmeta.foundation-mq-medium-only {\n  font-family: \"/\" + unquote($medium-only) + \"/\";\n  width: lower-bound($medium-range);\n}\n\nmeta.foundation-mq-large {\n  font-family: \"/\" + unquote($large-up) + \"/\";\n  width: lower-bound($large-range);\n}\n\nmeta.foundation-mq-large-only {\n  font-family: \"/\" + unquote($large-only) + \"/\";\n  width: lower-bound($large-range);\n}\n\nmeta.foundation-mq-xlarge {\n  font-family: \"/\" + unquote($xlarge-up) + \"/\";\n  width: lower-bound($xlarge-range);\n}\n\nmeta.foundation-mq-xlarge-only {\n  font-family: \"/\" + unquote($xlarge-only) + \"/\";\n  width: lower-bound($xlarge-range);\n}\n\nmeta.foundation-mq-xxlarge {\n  font-family: \"/\" + unquote($xxlarge-up) + \"/\";\n  width: lower-bound($xxlarge-range);\n}\n\nmeta.foundation-data-attribute-namespace {\n  font-family: #{$namespace};\n}\n\n@if $include-html-global-classes {\n\n  // Must be 100% for off canvas to work\n  html,\n  body {\n    height: 100%;\n  }\n\n  // Set box-sizing globally to handle padding and border widths\n  *,\n  *:before,\n  *:after {\n    @include box-sizing(border-box);\n  }\n\n  html,\n  body {\n    font-size: $base-font-size;\n  }\n\n  // Default body styles\n  body {\n    background: $body-bg;\n    color: $body-font-color;\n    padding: 0;\n    margin: 0;\n    font-family: $body-font-family;\n    font-weight: $body-font-weight;\n    font-style: $body-font-style;\n    line-height: $base-line-height; // Set to $base-line-height to take on browser default of 150%\n    position: relative;\n    cursor: $cursor-auto-value;\n  }\n\n  a:hover {\n    cursor: $cursor-pointer-value;\n  }\n\n  // Grid Defaults to get images and embeds to work properly\n  img {\n    max-width: 100%;\n    height: auto;\n  }\n\n  img {\n    -ms-interpolation-mode: bicubic;\n  }\n\n  #map_canvas,\n  .map_canvas {\n\n    img,\n    embed,\n    object {\n      max-width: none !important;\n    }\n  }\n\n  // Miscellaneous useful HTML classes\n  .left {\n    float: left !important;\n  }\n\n  .right {\n    float: right !important;\n  }\n\n  .clearfix {\n    @include clearfix;\n  }\n\n  // Hide visually and from screen readers\n  .hide {\n    display: none !important;\n    visibility: hidden;\n  }\n\n  // Hide visually and from screen readers, but maintain layout\n  .invisible {\n    visibility: hidden;\n  }\n\n  // Font smoothing\n  // Antialiased font smoothing works best for light text on a dark background.\n  // Apply to single elements instead of globally to body.\n  // Note this only applies to webkit-based desktop browsers and Firefox 25 (and later) on the Mac.\n  .antialiased {\n    -webkit-font-smoothing: antialiased;\n    -moz-osx-font-smoothing: grayscale;\n  }\n\n  // Get rid of gap under images by making them display: inline-block; by default\n  img {\n    display: inline-block;\n    vertical-align: middle;\n  }\n\n  //\n  // Global resets for forms\n  //\n\n  // Make sure textarea takes on height automatically\n  textarea {\n    height: auto;\n    min-height: 50px;\n  }\n\n  // Make select elements 100% width by default\n  select {\n    width: 100%;\n  }\n}\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-button-classes: $include-html-classes !default;\n\n// We use these to build padding for buttons.\n$button-tny: rem-calc(10) !default;\n$button-sml: rem-calc(14) !default;\n$button-med: rem-calc(16) !default;\n$button-lrg: rem-calc(18) !default;\n\n// We use this to control the display property.\n$button-display: inline-block !default;\n$button-margin-bottom: rem-calc(20) !default;\n\n// We use these to control button text styles.\n$button-font-family: $body-font-family !default;\n$button-font-color: $white !default;\n$button-font-color-alt: $oil !default;\n$button-font-tny: rem-calc(11) !default;\n$button-font-sml: rem-calc(13) !default;\n$button-font-med: rem-calc(16) !default;\n$button-font-lrg: rem-calc(20) !default;\n$button-font-weight: $font-weight-normal !default;\n$button-font-align: center !default;\n\n// We use these to control various hover effects.\n$button-function-factor: -20% !default;\n\n// We use these to control button border styles.\n$button-border-width: 0 !default;\n$button-border-style: solid !default;\n$button-bg-color: $primary-color !default;\n$button-bg-hover: scale-color($button-bg-color, $lightness: $button-function-factor) !default;\n$button-border-color: $button-bg-hover !default;\n$secondary-button-bg-hover: scale-color($secondary-color, $lightness: $button-function-factor) !default;\n$secondary-button-border-color: $secondary-button-bg-hover !default;\n$success-button-bg-hover: scale-color($success-color, $lightness: $button-function-factor) !default;\n$success-button-border-color: $success-button-bg-hover !default;\n$alert-button-bg-hover: scale-color($alert-color, $lightness: $button-function-factor) !default;\n$alert-button-border-color: $alert-button-bg-hover !default;\n$warning-button-bg-hover: scale-color($warning-color, $lightness: $button-function-factor) !default;\n$warning-button-border-color: $warning-button-bg-hover !default;\n$info-button-bg-hover: scale-color($info-color, $lightness: $button-function-factor) !default;\n$info-button-border-color: $info-button-bg-hover !default;\n\n// We use this to set the default radius used throughout the core.\n$button-radius: $global-radius !default;\n$button-round: $global-rounded !default;\n\n// We use this to set default opacity and cursor for disabled buttons.\n$button-disabled-opacity: 0.7 !default;\n$button-disabled-cursor: $cursor-default-value !default;\n\n\n//\n// @MIXIN\n//\n// We use this mixin to create a default button base.\n//\n// $style - Sets base styles. Can be set to false. Default: true.\n// $display - Used to control display property. Default: $button-display || inline-block\n\n@mixin button-base($style:true, $display:$button-display) {\n  @if $style {\n    border-style: $button-border-style;\n    border-width: $button-border-width;\n    cursor: $cursor-pointer-value;\n    font-family: $button-font-family;\n    font-weight: $button-font-weight;\n    line-height: normal;\n    margin: 0 0 $button-margin-bottom;\n    position: relative;\n    text-decoration: none;\n    text-align: $button-font-align;\n    -webkit-appearance: none;\n    border-radius:0;\n  }\n  @if $display { display: $display; }\n}\n\n// @MIXIN\n//\n// We use this mixin to add button size styles\n//\n// $padding - Used to build padding for buttons Default: $button-med ||= rem-calc(12)\n// $full-width - We can set $full-width:true to remove side padding extend width - Default: false\n\n@mixin button-size($padding:$button-med, $full-width:false) {\n\n  // We control which padding styles come through,\n  // these can be turned off by setting $padding:false\n  @if $padding {\n    padding-top: $padding;\n    padding-#{$opposite-direction}: $padding * 2;\n    padding-bottom: $padding + rem-calc(1);\n    padding-#{$default-float}: $padding * 2;\n\n    // We control the font-size based on mixin input.\n    @if      $padding == $button-med { font-size: $button-font-med; }\n    @else if $padding == $button-tny { font-size: $button-font-tny; }\n    @else if $padding == $button-sml { font-size: $button-font-sml; }\n    @else if $padding == $button-lrg { font-size: $button-font-lrg; }\n  }\n\n  // We can set $full-width:true to remove side padding extend width.\n  @if $full-width {\n    // We still need to check if $padding is set.\n    @if $padding {\n    padding-top: $padding;\n    padding-bottom: $padding + rem-calc(1);\n    } @else if $padding == false {\n      padding-top:0;\n      padding-bottom:0;\n    }\n    padding-right: 0;\n    padding-left: 0;\n    width: 100%;\n  }\n}\n\n// @MIXIN\n//\n// we use this mixin to create the button hover and border colors\n\n// @MIXIN\n//\n// We use this mixin to add button color styles\n//\n// $bg - Background color. We can set $bg:false for a transparent background. Default: $primary-color.\n// $radius - If true, set to button radius which is $global-radius || explicitly set radius amount in px (ex. $radius:10px). Default: true\n// $disabled - We can set $disabled:true to create a disabled transparent button. Default: false\n// $bg-hover - Button Hover Background Color. Default: $button-bg-hover\n// $border-color - Button Border Color. Default: $button-border-color\n@mixin button-style($bg:$button-bg-color, $radius:false, $disabled:false, $bg-hover:null, $border-color:null) {\n\n  // We control which background styles are used,\n  // these can be removed by setting $bg:false\n  @if $bg {\n\n    @if $bg-hover == null {\n      $bg-hover: if($bg == $button-bg-color, $button-bg-hover, scale-color($bg, $lightness: $button-function-factor));\n    }\n\n    @if $border-color == null {\n      $border-color: if($bg == $button-bg-color, $button-border-color, scale-color($bg, $lightness: $button-function-factor));\n    }\n\n    // This find the lightness percentage of the background color.\n    $bg-lightness: lightness($bg);\n    $bg-hover-lightness: lightness($bg-hover);\n\n    background-color: $bg;\n    border-color: $border-color;\n    &:hover,\n    &:focus { background-color: $bg-hover; }\n\n    // We control the text color for you based on the background color.\n    color: if($bg-lightness > 70%, $button-font-color-alt, $button-font-color);\n\n    &:hover,\n    &:focus {\n      color: if($bg-hover-lightness > 70%, $button-font-color-alt, $button-font-color);\n    }\n  }\n\n  // We can set $disabled:true to create a disabled transparent button.\n  @if $disabled {\n    cursor: $button-disabled-cursor;\n    opacity: $button-disabled-opacity;\n    box-shadow: none;\n    &:hover,\n    &:focus { background-color: $bg; }\n  }\n\n  // We can control how much button radius is used.\n  @if $radius == true { @include radius($button-radius); }\n  @else if $radius { @include radius($radius); }\n\n}\n\n// @MIXIN\n//\n// We use this to quickly create buttons with a single mixin. As @jaredhardy puts it, \"the kitchen sink mixin\"\n//\n// $padding - Used to build padding for buttons Default: $button-med ||= rem-calc(12)\n// $bg - Primary color set in settings file. Default: $button-bg.\n// $radius - If true, set to button radius which is $global-radius || explicitly set radius amount in px (ex. $radius:10px). Default:false.\n// $full-width - We can set $full-width:true to remove side padding extend width. Default:false.\n// $disabled - We can set $disabled:true to create a disabled transparent button. Default:false.\n// $is-prefix - Not used? Default:false.\n// $bg-hover - Button Hover Color - Default null - see button-style mixin\n// $border-color - Button Border Color - Default null - see button-style mixin\n// $transition - We can control whether or not to include the background-color transition property - Default:true.\n@mixin button($padding:$button-med, $bg:$button-bg-color, $radius:false, $full-width:false, $disabled:false, $is-prefix:false, $bg-hover:null, $border-color:null, $transition: true) {\n  @include button-base;\n  @include button-size($padding, $full-width);\n  @include button-style($bg, $radius, $disabled, $bg-hover, $border-color);\n\n  @if $transition {\n    @include single-transition(background-color);\n  }\n}\n\n\n@include exports(\"button\") {\n  @if $include-html-button-classes {\n\n    // Default styles applied outside of media query\n    button, .button {\n      @include button-base;\n      @include button-size;\n      @include button-style;\n\n      @include single-transition(background-color);\n\n      &.secondary { @include button-style($bg:$secondary-color, $bg-hover:$secondary-button-bg-hover, $border-color:$secondary-button-border-color); }\n      &.success   { @include button-style($bg:$success-color, $bg-hover:$success-button-bg-hover, $border-color:$success-button-border-color); }\n      &.alert     { @include button-style($bg:$alert-color, $bg-hover:$alert-button-bg-hover, $border-color:$alert-button-border-color); }\n      &.warning   { @include button-style($bg:$warning-color, $bg-hover:$warning-button-bg-hover, $border-color:$warning-button-border-color); }\n      &.info      { @include button-style($bg:$info-color, $bg-hover:$info-button-bg-hover, $border-color:$info-button-border-color); }\n\n      &.large  { @include button-size($padding:$button-lrg); }\n      &.small  { @include button-size($padding:$button-sml); }\n      &.tiny   { @include button-size($padding:$button-tny); }\n      &.expand { @include button-size($padding:null,$full-width:true); }\n\n      &.left-align  { text-align: left; text-indent: rem-calc(12); }\n      &.right-align { text-align: right; padding-right: rem-calc(12); }\n\n      &.radius { @include button-style($bg:false, $radius:true); }\n      &.round  { @include button-style($bg:false, $radius:$button-round); }\n\n      &.disabled, &[disabled] { @include button-style($bg:$button-bg-color, $disabled:true, $bg-hover:$button-bg-hover, $border-color:$button-border-color);\n        &.secondary { @include button-style($bg:$secondary-color, $disabled:true, $bg-hover:$secondary-button-bg-hover, $border-color:$secondary-button-border-color); }\n        &.success { @include button-style($bg:$success-color, $disabled:true, $bg-hover:$success-button-bg-hover, $border-color:$success-button-border-color); }\n        &.alert { @include button-style($bg:$alert-color, $disabled:true, $bg-hover:$alert-button-bg-hover, $border-color:$alert-button-border-color); }\n        &.warning { @include button-style($bg:$warning-color, $disabled:true, $bg-hover:$warning-button-bg-hover, $border-color:$warning-button-border-color); }\n        &.info { @include button-style($bg:$info-color, $disabled:true, $bg-hover:$info-button-bg-hover, $border-color:$info-button-border-color); }\n      }\n    }\n\n    //firefox 2px fix\n    button::-moz-focus-inner {border:0; padding:0;}\n\n    @media #{$medium-up} {\n      button, .button {\n        @include button-base($style:false, $display:inline-block);\n        @include button-size($padding:false, $full-width:false);\n      }\n    }\n  }\n}\n","@charset \"utf-8\";\n\n$spacing-unit: 30px;\n\n\n// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n//\n\n// Table of Contents\n// Foundation Settings\n//\n// a. Base\n// b. Grid\n// c. Global\n// d. Media Query Ranges\n// e. Typography\n// 01. Accordion\n// 02. Alert Boxes\n// 03. Block Grid\n// 04. Breadcrumbs\n// 05. Buttons\n// 06. Button Groups\n// 07. Clearing\n// 08. Dropdown\n// 09. Dropdown Buttons\n// 10. Flex Video\n// 11. Forms\n// 12. Icon Bar\n// 13. Inline Lists\n// 14. Joyride\n// 15. Keystrokes\n// 16. Labels\n// 17. Magellan\n// 18. Off-canvas\n// 19. Orbit\n// 20. Pagination\n// 21. Panels\n// 22. Pricing Tables\n// 23. Progress Bar\n// 24. Range Slider\n// 25. Reveal\n// 26. Side Nav\n// 27. Split Buttons\n// 28. Sub Nav\n// 29. Switch\n// 30. Tables\n// 31. Tabs\n// 32. Thumbnails\n// 33. Tooltips\n// 34. Top Bar\n// 36. Visibility Classes\n\n// a. Base\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// This is the default html and body font-size for the base rem value.\n// $rem-base: 16px;\n\n// Allows the use of rem-calc() or lower-bound() in your settings\n@import \"functions\";\n\n// The default font-size is set to 100% of the browser style sheet (usually 16px)\n// for compatibility with browser-based text zoom or user-set defaults.\n\n// Since the typical default browser font-size is 16px, that makes the calculation for grid size.\n// If you want your base font-size to be different and not have it affect the grid breakpoints,\n// set $rem-base to $base-font-size and make sure $base-font-size is a px value.\n// $base-font-size: 100%;\n\n$base-font-size: 16px;\n$rem-base: $base-font-size;\n\n\n// The $base-font-size is 100% while $base-line-height is 150%\n// $base-line-height: 150%;\n\n// We use this to control whether or not CSS classes come through in the gem files.\n$include-html-classes: true;\n// $include-print-styles: true;\n$include-html-global-classes: $include-html-classes;\n\n// b. Grid\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-grid-classes: $include-html-classes;\n// $include-xl-html-grid-classes: false;\n\n// $row-width: rem-calc(1000);\n// $total-columns: 12;\n// $column-gutter: rem-calc(30);\n\n// c. Global\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// We use these to define default font stacks\n// $font-family-sans-serif: \"Lato\", \"Helvetica Neue\", \"Helvetica\", Helvetica, Arial, sans-serif;\n// $font-family-serif: \"Volkhov\", Georgia, Times, serif;\n// $font-family-monospace: \"Lucida Console\", Monaco, monospace;\n\n// We use these to define default font weights\n// $font-weight-normal: normal !default;\n// $font-weight-bold: bold !default;\n\n// $white       : #FFFFFF;\n// $ghost       : #FAFAFA;\n// $snow        : #F9F9F9;\n// $vapor       : #F6F6F6;\n// $white-smoke : #F5F5F5;\n// $silver      : #EFEFEF;\n// $smoke       : #EEEEEE;\n// $gainsboro   : #DDDDDD;\n// $iron        : #CCCCCC;\n// $base        : #AAAAAA;\n// $aluminum    : #999999;\n// $jumbo       : #888888;\n// $monsoon     : #777777;\n// $steel       : #666666;\n// $charcoal    : #555555;\n// $tuatara     : #444444;\n// $oil         : #333333;\n// $jet         : #222222;\n// $black       : #000000;\n\n// We use these as default colors throughout\n// $primary-color: #008CBA;\n// $secondary-color: #e7e7e7;\n// $alert-color: #f04124;\n// $success-color: #43AC6A;\n// $warning-color: #f08a24;\n// $info-color: #a0d3e8;\n\n// We use these to control various global styles\n// $body-bg: $white;\n// $body-font-color: $jet;\n// $body-font-family: $font-family-sans-serif;\n// $body-font-weight: $font-weight-normal;\n// $body-font-style: normal;\n\n// We use this to control font-smoothing\n// $font-smoothing: antialiased;\n\n// We use these to control text direction settings\n// $text-direction: ltr;\n// $opposite-direction: right;\n// $default-float: left;\n// $last-child-float: $opposite-direction;\n\n// We use these to make sure border radius matches unless we want it different.\n$global-radius: 3px;\n// $global-rounded: 1000px;\n\n// We use these to control inset shadow shiny edges and depressions.\n// $shiny-edge-size: 0 1px 0;\n// $shiny-edge-color: rgba($white, .5);\n// $shiny-edge-active-color: rgba($black, .2);\n\n// // d. Media Query Ranges\n// // - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $small-range: (0em, 40em);\n// $medium-range: (40.063em, 64em);\n// $large-range: (64.063em, 90em);\n// $xlarge-range: (90.063em, 120em);\n// $xxlarge-range: (120.063em, 99999999em);\n\n// $screen: \"only screen\";\n\n// // $landscape: \"#{$screen} and (orientation: landscape)\";\n// // $portrait: \"#{$screen} and (orientation: portrait)\";\n\n// $small-up: $screen;\n// $small-only: \"#{$screen} and (max-width: #{upper-bound($small-range)})\";\n\n// $medium-up: \"#{$screen} and (min-width:#{lower-bound($medium-range)})\";\n// $medium-only: \"#{$screen} and (min-width:#{lower-bound($medium-range)}) and (max-width:#{upper-bound($medium-range)})\";\n\n// $large-up: \"#{$screen} and (min-width:#{lower-bound($large-range)})\";\n// $large-only: \"#{$screen} and (min-width:#{lower-bound($large-range)}) and (max-width:#{upper-bound($large-range)})\";\n\n// $xlarge-up: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)})\";\n// $xlarge-only: \"#{$screen} and (min-width:#{lower-bound($xlarge-range)}) and (max-width:#{upper-bound($xlarge-range)})\";\n\n// $xxlarge-up: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)})\";\n// $xxlarge-only: \"#{$screen} and (min-width:#{lower-bound($xxlarge-range)}) and (max-width:#{upper-bound($xxlarge-range)})\";\n\n// Legacy\n// $small: $medium-up;\n// $medium: $medium-up;\n// $large: $large-up;\n\n// We use this as cursors values for enabling the option of having custom cursors in the whole site's stylesheet\n// $cursor-crosshair-value: crosshair;\n// $cursor-default-value: default;\n// $cursor-pointer-value: pointer;\n// $cursor-help-value: help;\n// $cursor-text-value: text;\n\n// e. Typography\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-type-classes: $include-html-classes;\n\n// We use these to control header font styles\n// $header-font-family: $font-family-serif;\n// $header-font-weight: $font-weight-normal;\n// $header-font-style: normal;\n// $header-font-color: $jet;\n// $header-line-height: 1.4;\n// $header-top-margin: .2rem;\n// $header-bottom-margin: .5rem;\n// $header-text-rendering: optimizeLegibility;\n\n// We use these to control header font sizes\n// $h1-font-size: rem-calc(54);\n// $h2-font-size: rem-calc(36);\n// $h3-font-size: rem-calc(29);\n// $h4-font-size: rem-calc(24);\n// $h5-font-size: rem-calc(19);\n// $h6-font-size: 1rem;\n\n// We use these to control header size reduction on small screens\n// $h1-font-reduction: rem-calc(10) !default;\n// $h2-font-reduction: rem-calc(10) !default;\n// $h3-font-reduction: rem-calc(5) !default;\n// $h4-font-reduction: rem-calc(5) !default;\n// $h5-font-reduction: 0 !default;\n// $h6-font-reduction: 0 !default;\n\n// These control how subheaders are styled.\n// $subheader-line-height: 1.4;\n// $subheader-font-color: scale-color($header-font-color, $lightness: 35%);\n// $subheader-font-weight: $font-weight-normal;\n// $subheader-top-margin: .2rem;\n// $subheader-bottom-margin: .5rem;\n\n// A general <small> styling\n// $small-font-size: 60%;\n// $small-font-color: scale-color($header-font-color, $lightness: 35%);\n\n// We use these to style paragraphs\n// $paragraph-font-family: inherit;\n// $paragraph-font-weight: $font-weight-normal;\n// $paragraph-font-size: 1rem;\n// $paragraph-line-height: 1.6;\n// $paragraph-margin-bottom: rem-calc(20);\n// $paragraph-aside-font-size: rem-calc(14);\n// $paragraph-aside-line-height: 1.35;\n// $paragraph-aside-font-style: italic;\n// $paragraph-text-rendering: optimizeLegibility;\n\n// We use these to style <code> tags\n// $code-color: $oil;\n// $code-font-family: $font-family-monospace;\n// $code-font-weight: $font-weight-normal;\n// $code-background-color: scale-color($secondary-color, $lightness: 70%);\n// $code-border-size: 1px;\n// $code-border-style: solid;\n// $code-border-color: scale-color($code-background-color, $lightness: -10%);\n// $code-padding: rem-calc(2) rem-calc(5) rem-calc(1);\n\n// We use these to style anchors\n// $anchor-text-decoration: none;\n// $anchor-text-decoration-hover: none;\n// $anchor-font-color: $primary-color;\n// $anchor-font-color-hover: scale-color($primary-color, $lightness: -14%);\n\n// We use these to style the <hr> element\n// $hr-border-width: 1px;\n// $hr-border-style: solid;\n$hr-border-color: $grey-3;\n// $hr-margin: rem-calc(20);\n\n// We use these to style lists\n// $list-font-family: $paragraph-font-family;\n// $list-font-size: $paragraph-font-size;\n// $list-line-height: $paragraph-line-height;\n// $list-margin-bottom: $paragraph-margin-bottom;\n// $list-style-position: outside;\n$list-side-margin: 1.3rem;\n// $list-ordered-side-margin: 1.4rem;\n// $list-side-margin-no-bullet: 0;\n// $list-nested-margin: rem-calc(20);\n// $definition-list-header-weight: $font-weight-bold;\n// $definition-list-header-margin-bottom: .3rem;\n// $definition-list-margin-bottom: rem-calc(12);\n\n// We use these to style blockquotes\n// $blockquote-font-color: scale-color($header-font-color, $lightness: 35%);\n// $blockquote-padding: rem-calc(9 20 0 19);\n// $blockquote-border: 1px solid $gainsboro;\n// $blockquote-cite-font-size: rem-calc(13);\n// $blockquote-cite-font-color: scale-color($header-font-color, $lightness: 23%);\n// $blockquote-cite-link-color: $blockquote-cite-font-color;\n\n// Acronym styles\n// $acronym-underline: 1px dotted $gainsboro;\n\n// We use these to control padding and margin\n// $microformat-padding: rem-calc(10 12);\n// $microformat-margin: rem-calc(0 0 20 0);\n\n// We use these to control the border styles\n// $microformat-border-width: 1px;\n// $microformat-border-style: solid;\n// $microformat-border-color: $gainsboro;\n\n// We use these to control full name font styles\n// $microformat-fullname-font-weight: $font-weight-bold;\n// $microformat-fullname-font-size: rem-calc(15);\n\n// We use this to control the summary font styles\n// $microformat-summary-font-weight: $font-weight-bold;\n\n// We use this to control abbr padding\n// $microformat-abbr-padding: rem-calc(0 1);\n\n// We use this to control abbr font styles\n// $microformat-abbr-font-weight: $font-weight-bold;\n// $microformat-abbr-font-decoration: none;\n\n// 01. Accordion\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-accordion-classes: $include-html-classes;\n\n$accordion-navigation-padding: rem-calc(12);\n// $accordion-navigation-bg-color: #ffffff;\n// $accordion-navigation-hover-bg-color: $grey-1;\n// $accordion-navigation-active-bg-color: $grey-1;\n// $accordion-navigation-font-color: $jet;\n// $accordion-navigation-font-size: rem-calc(16);\n// $accordion-navigation-font-family: $body-font-family;\n\n// $accordion-content-padding: $column-gutter/2;\n$accordion-content-active-bg-color: $body-bg;\n\n// 02. Alert Boxes\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-alert-classes: $include-html-classes;\n\n// We use this to control alert padding.\n// $alert-padding-top: rem-calc(14);\n// $alert-padding-default-float: $alert-padding-top;\n// $alert-padding-opposite-direction: $alert-padding-top + rem-calc(10);\n// $alert-padding-bottom: $alert-padding-top;\n\n// We use these to control text style.\n// $alert-font-weight: $font-weight-normal;\n$alert-font-size: rem-calc(15);\n// $alert-font-color: $white;\n// $alert-font-color-alt: scale-color($secondary-color, $lightness: -66%);\n\n// We use this for close hover effect.\n// $alert-function-factor: -14%;\n\n// We use these to control border styles.\n// $alert-border-style: solid;\n// $alert-border-width: 1px;\n// $alert-border-color: scale-color($primary-color, $lightness: $alert-function-factor);\n// $alert-bottom-margin: rem-calc(20);\n\n// We use these to style the close buttons\n// $alert-close-color: $oil;\n// $alert-close-top: 50%;\n// $alert-close-position: rem-calc(4);\n// $alert-close-font-size: rem-calc(22);\n// $alert-close-opacity: 0.3;\n// $alert-close-opacity-hover: 0.5;\n// $alert-close-padding: 9px 6px 4px;\n\n// We use this to control border radius\n// $alert-radius: $global-radius;\n\n// We use this to control transition effects\n// $alert-transition-speed: 300ms;\n// $alert-transition-ease: ease-out;\n\n// 03. Block Grid\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-block-grid-classes: $include-html-classes;\n// $include-xl-html-block-grid-classes: false;\n\n// We use this to control the maximum number of block grid elements per row\n// $block-grid-elements: 12;\n// $block-grid-default-spacing: rem-calc(20);\n// $align-block-grid-to-grid: false;\n\n// Enables media queries for block-grid classes. Set to false if writing semantic HTML.\n// $block-grid-media-queries: true;\n\n// 04. Breadcrumbs\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-nav-classes: $include-html-classes;\n\n// We use this to set the background color for the breadcrumb container.\n$crumb-bg: $grey-1;\n\n// We use these to set the padding around the breadcrumbs.\n// $crumb-padding: rem-calc(9 9 14 0);\n// $crumb-side-padding: rem-calc(12);\n\n// We use these to control border styles.\n// $crumb-function-factor: -10%;\n$crumb-border-size: 0;\n// $crumb-border-style: solid;\n$crumb-border-color: $grey-1;\n$crumb-radius: 0;\n\n// We use these to set various text styles for breadcrumbs.\n// $crumb-font-size: rem-calc(11);\n// $crumb-font-color: $primary-color;\n// $crumb-font-color-current: $oil;\n// $crumb-font-color-unavailable: $aluminum;\n// $crumb-font-transform: uppercase;\n// $crumb-link-decor: underline;\n\n// We use these to control the slash between breadcrumbs\n// $crumb-slash-color: $base;\n$crumb-slash: \"/\";\n\n// 05. Buttons\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-button-classes: $include-html-classes;\n\n// We use these to build padding for buttons.\n// $button-tny: rem-calc(10);\n// $button-sml: rem-calc(14);\n// $button-med: rem-calc(16);\n// $button-lrg: rem-calc(18);\n\n// We use this to control the display property.\n// $button-display: inline-block;\n// $button-margin-bottom: rem-calc(20);\n\n// We use these to control button text styles.\n// $button-font-family: $body-font-family;\n// $button-font-color: $white;\n// $button-font-color-alt: $oil;\n// $button-font-tny: rem-calc(11);\n// $button-font-sml: rem-calc(13);\n// $button-font-med: rem-calc(16);\n// $button-font-lrg: rem-calc(20);\n// $button-font-weight: $font-weight-normal;\n// $button-font-align: center;\n\n// We use these to control various hover effects.\n// $button-function-factor: -20%;\n\n// We use these to control button border and hover styles.\n// $button-border-width: 0px;\n// $button-border-style: solid;\n// $button-bg-color: $primary-color;\n// $button-bg-hover: scale-color($button-bg-color, $lightness: $button-function-factor);\n// $button-border-color: $button-bg-hover;\n// $secondary-button-bg-hover: scale-color($secondary-color, $lightness: $button-function-factor);\n// $secondary-button-border-color: $secondary-button-bg-hover;\n// $success-button-bg-hover: scale-color($success-color, $lightness: $button-function-factor);\n// $success-button-border-color: $success-button-bg-hover;\n// $alert-button-bg-hover: scale-color($alert-color, $lightness: $button-function-factor);\n// $alert-button-border-color: $alert-button-bg-hover;\n\n// We use this to set the default radius used throughout the core.\n// $button-radius: $global-radius;\n// $button-round: $global-rounded;\n\n// We use this to set default opacity and cursor for disabled buttons.\n// $button-disabled-opacity: 0.7;\n// $button-disabled-cursor: $cursor-default-value;\n\n// 06. Button Groups\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-button-classes: $include-html-classes;\n\n// Sets the margin for the right side by default, and the left margin if right-to-left direction is used\n// $button-bar-margin-opposite: rem-calc(10);\n// $button-group-border-width: 1px;\n\n// 07. Clearing\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-clearing-classes: $include-html-classes;\n\n// We use these to set the background colors for parts of Clearing.\n// $clearing-bg: $oil;\n// $clearing-caption-bg: $clearing-bg;\n// $clearing-carousel-bg: rgba(51,51,51,0.8);\n// $clearing-img-bg: $clearing-bg;\n\n// We use these to style the close button\n// $clearing-close-color: $iron;\n// $clearing-close-size: 30px;\n\n// We use these to style the arrows\n// $clearing-arrow-size: 12px;\n// $clearing-arrow-color: $clearing-close-color;\n\n// We use these to style captions\n// $clearing-caption-font-color: $iron;\n// $clearing-caption-font-size: 0.875em;\n// $clearing-caption-padding: 10px 30px 20px;\n\n// We use these to make the image and carousel height and style\n// $clearing-active-img-height: 85%;\n// $clearing-carousel-height: 120px;\n// $clearing-carousel-thumb-width: 120px;\n// $clearing-carousel-thumb-active-border: 1px solid rgb(255,255,255);\n\n// 08. Dropdown\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-dropdown-classes: $include-html-classes;\n\n// We use these to controls height and width styles.\n// $f-dropdown-max-width: 200px;\n// $f-dropdown-height: auto;\n// $f-dropdown-max-height: none;\n\n// Used for bottom position\n// $f-dropdown-margin-top: 2px;\n\n// Used for right position\n// $f-dropdown-margin-left: $f-dropdown-margin-top;\n\n// Used for left position\n// $f-dropdown-margin-right: $f-dropdown-margin-top;\n\n// Used for top position\n// $f-dropdown-margin-bottom: $f-dropdown-margin-top;\n\n// We use this to control the background color\n// $f-dropdown-bg: $white;\n\n// We use this to set the border styles for dropdowns.\n// $f-dropdown-border-style: solid;\n// $f-dropdown-border-width: 1px;\n// $f-dropdown-border-color: scale-color($white, $lightness: -20%);\n\n// We use these to style the triangle pip.\n// $f-dropdown-triangle-size: 6px;\n// $f-dropdown-triangle-color: $white;\n// $f-dropdown-triangle-side-offset: 10px;\n\n// We use these to control styles for the list elements.\n// $f-dropdown-list-style: none;\n// $f-dropdown-font-color: $charcoal;\n// $f-dropdown-font-size: rem-calc(14);\n// $f-dropdown-list-padding: rem-calc(5, 10);\n// $f-dropdown-line-height: rem-calc(18);\n// $f-dropdown-list-hover-bg: $smoke  ;\n// $dropdown-mobile-default-float: 0;\n\n// We use this to control the styles for when the dropdown has custom content.\n// $f-dropdown-content-padding: rem-calc(20);\n\n// Default radius for dropdown.\n// $f-dropdown-radius: $global-radius;\n\n\n// 09. Dropdown Buttons\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-button-classes: $include-html-classes;\n\n// We use these to set the color of the pip in dropdown buttons\n// $dropdown-button-pip-color: $white;\n// $dropdown-button-pip-color-alt: $oil;\n\n// $button-pip-tny: rem-calc(6);\n// $button-pip-sml: rem-calc(7);\n// $button-pip-med: rem-calc(9);\n// $button-pip-lrg: rem-calc(11);\n\n// We use these to style tiny dropdown buttons\n// $dropdown-button-padding-tny: $button-pip-tny * 7;\n// $dropdown-button-pip-size-tny: $button-pip-tny;\n// $dropdown-button-pip-opposite-tny: $button-pip-tny * 3;\n// $dropdown-button-pip-top-tny: -$button-pip-tny / 2 + rem-calc(1);\n\n// We use these to style small dropdown buttons\n// $dropdown-button-padding-sml: $button-pip-sml * 7;\n// $dropdown-button-pip-size-sml: $button-pip-sml;\n// $dropdown-button-pip-opposite-sml: $button-pip-sml * 3;\n// $dropdown-button-pip-top-sml: -$button-pip-sml / 2 + rem-calc(1);\n\n// We use these to style medium dropdown buttons\n// $dropdown-button-padding-med: $button-pip-med * 6 + rem-calc(3);\n// $dropdown-button-pip-size-med: $button-pip-med - rem-calc(3);\n// $dropdown-button-pip-opposite-med: $button-pip-med * 2.5;\n// $dropdown-button-pip-top-med: -$button-pip-med / 2 + rem-calc(2);\n\n// We use these to style large dropdown buttons\n// $dropdown-button-padding-lrg: $button-pip-lrg * 5 + rem-calc(3);\n// $dropdown-button-pip-size-lrg: $button-pip-lrg - rem-calc(6);\n// $dropdown-button-pip-opposite-lrg: $button-pip-lrg * 2.5;\n// $dropdown-button-pip-top-lrg: -$button-pip-lrg / 2 + rem-calc(3);\n\n// 10. Flex Video\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-media-classes: $include-html-classes;\n\n// We use these to control video container padding and margins\n// $flex-video-padding-top: rem-calc(25);\n// $flex-video-padding-bottom: 67.5%;\n// $flex-video-margin-bottom: rem-calc(16);\n\n// We use this to control widescreen bottom padding\n// $flex-video-widescreen-padding-bottom: 56.34%;\n\n// 11. Forms\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-form-classes: $include-html-classes;\n\n// We use this to set the base for lots of form spacing and positioning styles\n// $form-spacing: rem-calc(16);\n\n// We use these to style the labels in different ways\n// $form-label-pointer: pointer;\n// $form-label-font-size: rem-calc(14);\n// $form-label-font-weight: $font-weight-normal;\n// $form-label-line-height: 1.5;\n// $form-label-font-color: scale-color($black, $lightness: 30%);\n// $form-label-small-transform: capitalize;\n// $form-label-bottom-margin: 0;\n// $input-font-family: inherit;\n// $input-font-color: rgba(0,0,0,0.75);\n// $input-font-size: rem-calc(14);\n// $input-bg-color: $white;\n// $input-focus-bg-color: scale-color($white, $lightness: -2%);\n// $input-border-color: scale-color($white, $lightness: -20%);\n// $input-focus-border-color: scale-color($white, $lightness: -40%);\n// $input-border-style: solid;\n// $input-border-width: 1px;\n// $input-border-radius: $global-radius;\n// $input-disabled-bg: $gainsboro;\n// $input-disabled-cursor: $cursor-default-value;\n// $input-box-shadow: inset 0 1px 2px rgba(0,0,0,0.1);\n\n// We use these to style the fieldset border and spacing.\n// $fieldset-border-style: solid;\n// $fieldset-border-width: 1px;\n// $fieldset-border-color: $gainsboro;\n// $fieldset-padding: rem-calc(20);\n// $fieldset-margin: rem-calc(18 0);\n\n// We use these to style the legends when you use them\n// $legend-bg: $white;\n// $legend-font-weight: $font-weight-bold;\n// $legend-padding: rem-calc(0 3);\n\n// We use these to style the prefix and postfix input elements\n// $input-prefix-bg: scale-color($white, $lightness: -5%);\n// $input-prefix-border-color: scale-color($white, $lightness: -20%);\n// $input-prefix-border-size: 1px;\n// $input-prefix-border-type: solid;\n// $input-prefix-overflow: hidden;\n// $input-prefix-font-color: $oil;\n// $input-prefix-font-color-alt: $white;\n\n// We use this setting to turn on/off HTML5 number spinners (the up/down arrows)\n// $input-number-spinners: true;\n\n// We use these to style the error states for inputs and labels\n// $input-error-message-padding: rem-calc(6 9 9);\n// $input-error-message-top: -1px;\n// $input-error-message-font-size: rem-calc(12);\n// $input-error-message-font-weight: $font-weight-normal;\n// $input-error-message-font-style: italic;\n// $input-error-message-font-color: $white;\n// $input-error-message-font-color-alt: $oil;\n\n// We use this to style the glowing effect of inputs when focused\n// $input-include-glowing-effect: true;\n// $glowing-effect-fade-time: 0.45s;\n// $glowing-effect-color: $input-focus-border-color;\n\n// Select variables\n// $select-bg-color: $ghost;\n// $select-hover-bg-color: scale-color($select-bg-color, $lightness: -3%);\n\n// 12. Icon Bar\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// We use these to style the icon-bar and items\n// $include-html-icon-bar-classes: $include-html-classes;\n// $icon-bar-bg: $oil;\n// $icon-bar-font-color: $white;\n// $icon-bar-font-size: 1rem;\n// $icon-bar-hover-color: $primary-color;\n// $icon-bar-icon-color: $white;\n// $icon-bar-icon-size: 1.875rem;\n// $icon-bar-image-width: 1.875rem;\n// $icon-bar-image-height: 1.875rem;\n// $icon-bar-active-color: $primary-color;\n// $icon-bar-item-padding: 1.25rem;\n\n// 13. Inline Lists\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-inline-list-classes: $include-html-classes;\n\n// We use this to control the margins and padding of the inline list.\n// $inline-list-top-margin: 0;\n// $inline-list-opposite-margin: 0;\n// $inline-list-bottom-margin: rem-calc(17);\n// $inline-list-default-float-margin: rem-calc(-22);\n// $inline-list-default-float-list-margin: rem-calc(22);\n\n// $inline-list-padding: 0;\n\n// We use this to control the overflow of the inline list.\n// $inline-list-overflow: hidden;\n\n// We use this to control the list items\n// $inline-list-display: block;\n\n// We use this to control any elements within list items\n// $inline-list-children-display: block;\n\n// 14. Joyride\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-joyride-classes: $include-html-classes;\n\n// Controlling default Joyride styles\n// $joyride-tip-bg: $oil;\n// $joyride-tip-default-width: 300px;\n// $joyride-tip-padding: rem-calc(18 20 24);\n// $joyride-tip-border: solid 1px $charcoal;\n// $joyride-tip-radius: 4px;\n// $joyride-tip-position-offset: 22px;\n\n// Here, we're setting the tip font styles\n// $joyride-tip-font-color: $white;\n// $joyride-tip-font-size: rem-calc(14);\n// $joyride-tip-header-weight: $font-weight-bold;\n\n// This changes the nub size\n// $joyride-tip-nub-size: 10px;\n\n// This adjusts the styles for the timer when its enabled\n// $joyride-tip-timer-width: 50px;\n// $joyride-tip-timer-height: 3px;\n// $joyride-tip-timer-color: $steel;\n\n// This changes up the styles for the close button\n// $joyride-tip-close-color: $monsoon;\n// $joyride-tip-close-size: 24px;\n// $joyride-tip-close-weight: $font-weight-normal;\n\n// When Joyride is filling the screen, we use this style for the bg\n// $joyride-screenfill: rgba(0,0,0,0.5);\n\n// 15. Keystrokes\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-keystroke-classes: $include-html-classes;\n\n// We use these to control text styles.\n// $keystroke-font: \"Consolas\", \"Menlo\", \"Courier\", monospace;\n// $keystroke-font-size: inherit;\n// $keystroke-font-color: $jet;\n// $keystroke-font-color-alt: $white;\n// $keystroke-function-factor: -7%;\n\n// We use this to control keystroke padding.\n// $keystroke-padding: rem-calc(2 4 0);\n\n// We use these to control background and border styles.\n// $keystroke-bg: scale-color($white, $lightness: $keystroke-function-factor);\n// $keystroke-border-style: solid;\n// $keystroke-border-width: 1px;\n// $keystroke-border-color: scale-color($keystroke-bg, $lightness: $keystroke-function-factor);\n// $keystroke-radius: $global-radius;\n\n// 16. Labels\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-label-classes: $include-html-classes;\n\n// We use these to style the labels\n// $label-padding: rem-calc(4 8 4);\n// $label-radius: $global-radius;\n\n// We use these to style the label text\n// $label-font-sizing: rem-calc(11);\n// $label-font-weight: $font-weight-normal;\n// $label-font-color: $oil;\n// $label-font-color-alt: $white;\n// $label-font-family: $body-font-family;\n\n// 17. Magellan\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-magellan-classes: $include-html-classes;\n\n// $magellan-bg: $white;\n// $magellan-padding: 0 !important;\n\n// 18. Off-canvas\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-off-canvas-classes: $include-html-classes;\n\n// $tabbar-bg: $oil;\n// $tabbar-height: rem-calc(45);\n// $tabbar-icon-width: $tabbar-height;\n// $tabbar-line-height: $tabbar-height;\n// $tabbar-color: $white;\n// $tabbar-middle-padding: 0 rem-calc(10);\n\n// Off Canvas Divider Styles\n// $tabbar-right-section-border: solid 1px scale-color($tabbar-bg, $lightness: 13%);\n// $tabbar-left-section-border: solid 1px scale-color($tabbar-bg, $lightness: -50%);\n\n// Off Canvas Tab Bar Headers\n// $tabbar-header-color: $white;\n// $tabbar-header-weight: $font-weight-bold;\n// $tabbar-header-line-height: $tabbar-height;\n// $tabbar-header-margin: 0;\n\n// Off Canvas Menu Variables\n// $off-canvas-width: rem-calc(250);\n// $off-canvas-bg: $oil;\n// $off-canvas-bg-hover: scale-color($tabbar-bg, $lightness: -30%);\n\n// Off Canvas Menu List Variables\n// $off-canvas-label-padding: 0.3rem rem-calc(15);\n// $off-canvas-label-color: $aluminum;\n// $off-canvas-label-text-transform: uppercase;\n// $off-canvas-label-font-size: rem-calc(12);\n// $off-canvas-label-font-weight: $font-weight-bold;\n// $off-canvas-label-bg: $tuatara;\n// $off-canvas-label-border-top: 1px solid scale-color($tuatara, $lightness: 14%);\n// $off-canvas-label-border-bottom: none;\n// $off-canvas-label-margin:0;\n// $off-canvas-link-padding: rem-calc(10, 15);\n// $off-canvas-link-color: rgba($white, 0.7);\n// $off-canvas-link-border-bottom: 1px solid scale-color($off-canvas-bg, $lightness: -25%);\n// $off-canvas-back-bg: $tuatara;\n// $off-canvas-back-border-top: $off-canvas-label-border-top;\n// $off-canvas-back-border-bottom: $off-canvas-label-border-bottom;\n// $off-canvas-back-hover-bg: scale-color($off-canvas-back-bg, $lightness: -30%);\n// $off-canvas-back-hover-border-top: 1px solid scale-color($off-canvas-label-bg, $lightness: 14%);\n// $off-canvas-back-hover-border-bottom: none;\n\n// Off Canvas Menu Icon Variables\n// $tabbar-menu-icon-color: $white;\n// $tabbar-menu-icon-hover: scale-color($tabbar-menu-icon-color, $lightness: -30%);\n\n// $tabbar-menu-icon-text-indent: rem-calc(35);\n// $tabbar-menu-icon-width: $tabbar-height;\n// $tabbar-menu-icon-height: $tabbar-height;\n// $tabbar-menu-icon-padding: 0;\n\n// $tabbar-hamburger-icon-width: rem-calc(16);\n// $tabbar-hamburger-icon-left: false;\n// $tabbar-hamburger-icon-top: false;\n// $tabbar-hamburger-icon-thickness: 1px;\n// $tabbar-hamburger-icon-gap: 6px;\n\n// Off Canvas Back-Link Overlay\n// $off-canvas-overlay-transition: background 300ms ease;\n// $off-canvas-overlay-cursor: pointer;\n// $off-canvas-overlay-box-shadow: -4px 0 4px rgba($black, 0.5), 4px 0 4px rgba($black, 0.5);\n// $off-canvas-overlay-background: rgba($white, 0.2);\n// $off-canvas-overlay-background-hover: rgba($white, 0.05);\n\n// Transition Variables\n// $menu-slide: \"transform 500ms ease\";\n\n// 19. Orbit\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-orbit-classes: $include-html-classes;\n\n// We use these to control the caption styles\n// $orbit-container-bg: none;\n// $orbit-caption-bg: rgba(51,51,51, 0.8);\n// $orbit-caption-font-color: $white;\n// $orbit-caption-font-size: rem-calc(14);\n// $orbit-caption-position: \"bottom\"; // Supported values: \"bottom\", \"under\"\n// $orbit-caption-padding: rem-calc(10 14);\n// $orbit-caption-height: auto;\n\n// We use these to control the left/right nav styles\n// $orbit-nav-bg: transparent;\n// $orbit-nav-bg-hover: rgba(0,0,0,0.3);\n// $orbit-nav-arrow-color: $white;\n// $orbit-nav-arrow-color-hover: $white;\n\n// We use these to control the timer styles\n// $orbit-timer-bg: rgba(255,255,255,0.3);\n// $orbit-timer-show-progress-bar: true;\n\n// We use these to control the bullet nav styles\n// $orbit-bullet-nav-color: $iron;\n// $orbit-bullet-nav-color-active: $aluminum;\n// $orbit-bullet-radius: rem-calc(9);\n\n// We use these to controls the style of slide numbers\n// $orbit-slide-number-bg: rgba(0,0,0,0);\n// $orbit-slide-number-font-color: $white;\n// $orbit-slide-number-padding: rem-calc(5);\n\n// Hide controls on small\n// $orbit-nav-hide-for-small: true;\n// $orbit-bullet-hide-for-small: true;\n// $orbit-timer-hide-for-small: true;\n\n// Graceful Loading Wrapper and preloader\n// $wrapper-class: \"slideshow-wrapper\";\n// $preloader-class: \"preloader\";\n\n// 20. Pagination\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-pagination-classes: $include-html-classes;\n\n// We use these to control the pagination container\n// $pagination-height: rem-calc(24);\n// $pagination-margin: rem-calc(-5);\n\n// We use these to set the list-item properties\n// $pagination-li-float: $default-float;\n// $pagination-li-height: rem-calc(24);\n// $pagination-li-font-color: $jet;\n// $pagination-li-font-size: rem-calc(14);\n// $pagination-li-margin: rem-calc(5);\n\n// We use these for the pagination anchor links\n// $pagination-link-pad: rem-calc(1 10 1);\n// $pagination-link-font-color: $aluminum;\n// $pagination-link-active-bg: scale-color($white, $lightness: -10%);\n\n// We use these for disabled anchor links\n// $pagination-link-unavailable-cursor: default;\n// $pagination-link-unavailable-font-color: $aluminum;\n// $pagination-link-unavailable-bg-active: transparent;\n\n// We use these for currently selected anchor links\n// $pagination-link-current-background: $primary-color;\n// $pagination-link-current-font-color: $white;\n// $pagination-link-current-font-weight: $font-weight-bold;\n// $pagination-link-current-cursor: default;\n// $pagination-link-current-active-bg: $primary-color;\n\n// 21. Panels\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-panel-classes: $include-html-classes;\n\n// We use these to control the background and border styles\n$panel-bg: $grey-1;\n// $panel-border-style: solid;\n// $panel-border-size: 1px;\n\n// We use this % to control how much we darken things on hover\n// $panel-function-factor: -11%;\n// $panel-border-color: scale-color($panel-bg, $lightness: $panel-function-factor);\n\n// We use these to set default inner padding and bottom margin\n// $panel-margin-bottom: rem-calc(20);\n// $panel-padding: rem-calc(20);\n\n// We use these to set default font colors\n// $panel-font-color: $oil;\n// $panel-font-color-alt: $white;\n\n// $panel-header-adjust: true;\n// $callout-panel-link-color: $primary-color;\n\n// 22. Pricing Tables\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-pricing-classes: $include-html-classes;\n\n// We use this to control the border color\n// $price-table-border: solid 1px $gainsboro;\n\n// We use this to control the bottom margin of the pricing table\n// $price-table-margin-bottom: rem-calc(20);\n\n// We use these to control the title styles\n// $price-title-bg: $oil;\n// $price-title-padding: rem-calc(15 20);\n// $price-title-align: center;\n// $price-title-color: $smoke;\n// $price-title-weight: $font-weight-normal;\n// $price-title-size: rem-calc(16);\n// $price-title-font-family: $body-font-family;\n\n// We use these to control the price styles\n// $price-money-bg: $vapor  ;\n// $price-money-padding: rem-calc(15 20);\n// $price-money-align: center;\n// $price-money-color: $oil;\n// $price-money-weight: $font-weight-normal;\n// $price-money-size: rem-calc(32);\n// $price-money-font-family: $body-font-family;\n\n// We use these to control the description styles\n// $price-bg: $white;\n// $price-desc-color: $monsoon;\n// $price-desc-padding: rem-calc(15);\n// $price-desc-align: center;\n// $price-desc-font-size: rem-calc(12);\n// $price-desc-weight: $font-weight-normal;\n// $price-desc-line-height: 1.4;\n// $price-desc-bottom-border: dotted 1px $gainsboro;\n\n// We use these to control the list item styles\n// $price-item-color: $oil;\n// $price-item-padding: rem-calc(15);\n// $price-item-align: center;\n// $price-item-font-size: rem-calc(14);\n// $price-item-weight: $font-weight-normal;\n// $price-item-bottom-border: dotted 1px $gainsboro;\n\n// We use these to control the CTA area styles\n// $price-cta-bg: $white;\n// $price-cta-align: center;\n// $price-cta-padding: rem-calc(20 20 0);\n\n// 23. Progress Bar\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-media-classes: $include-html-classes;\n\n// We use this to set the progress bar height\n// $progress-bar-height: rem-calc(25);\n// $progress-bar-color: $vapor  ;\n\n// We use these to control the border styles\n// $progress-bar-border-color: scale-color($white, $lightness: 20%);\n// $progress-bar-border-size: 1px;\n// $progress-bar-border-style: solid;\n// $progress-bar-border-radius: $global-radius;\n\n// We use these to control the margin & padding\n// $progress-bar-pad: rem-calc(2);\n// $progress-bar-margin-bottom: rem-calc(10);\n\n// We use these to set the meter colors\n// $progress-meter-color: $primary-color;\n// $progress-meter-secondary-color: $secondary-color;\n// $progress-meter-success-color: $success-color;\n// $progress-meter-alert-color: $alert-color;\n\n// 24. Range Slider\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-range-slider-classes: $include-html-classes;\n\n// These variables define the slider bar styles\n// $range-slider-bar-width: 100%;\n// $range-slider-bar-height: rem-calc(16);\n\n// $range-slider-bar-border-width: 1px;\n// $range-slider-bar-border-style: solid;\n// $range-slider-bar-border-color: $gainsboro;\n// $range-slider-radius: $global-radius;\n// $range-slider-round: $global-rounded;\n// $range-slider-bar-bg-color: $ghost;\n\n// Vertical bar styles\n// $range-slider-vertical-bar-width: rem-calc(16);\n// $range-slider-vertical-bar-height: rem-calc(200);\n\n// These variables define the slider handle styles\n// $range-slider-handle-width: rem-calc(32);\n// $range-slider-handle-height: rem-calc(22);\n// $range-slider-handle-position-top: rem-calc(-5);\n// $range-slider-handle-bg-color: $primary-color;\n// $range-slider-handle-border-width: 1px;\n// $range-slider-handle-border-style: solid;\n// $range-slider-handle-border-color: none;\n// $range-slider-handle-radius: $global-radius;\n// $range-slider-handle-round: $global-rounded;\n// $range-slider-handle-bg-hover-color: scale-color($primary-color, $lightness: -12%);\n// $range-slider-handle-cursor: pointer;\n\n// 25. Reveal\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-reveal-classes: $include-html-classes;\n\n// We use these to control the style of the reveal overlay.\n// $reveal-overlay-bg: rgba($black, .45);\n// $reveal-overlay-bg-old: $black;\n\n// We use these to control the style of the modal itself.\n// $reveal-modal-bg: $white;\n// $reveal-position-top: rem-calc(100);\n// $reveal-default-width: 80%;\n// $reveal-max-width: $row-width;\n// $reveal-modal-padding: rem-calc(20);\n// $reveal-box-shadow: 0 0 10px rgba($black,.4);\n\n// We use these to style the reveal close button\n// $reveal-close-font-size: rem-calc(40);\n// $reveal-close-top: rem-calc(8);\n// $reveal-close-side: rem-calc(11);\n// $reveal-close-color: $base;\n// $reveal-close-weight: $font-weight-bold;\n\n// We use this to set the default radius used throughout the core.\n// $reveal-radius: $global-radius;\n// $reveal-round: $global-rounded;\n\n// We use these to control the modal border\n// $reveal-border-style: solid;\n// $reveal-border-width: 1px;\n// $reveal-border-color: $steel;\n\n// $reveal-modal-class: \"reveal-modal\";\n// $close-reveal-modal-class: \"close-reveal-modal\";\n\n// 26. Side Nav\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-nav-classes: $include-html-classes;\n\n// We use this to control padding.\n$side-nav-padding: rem-calc(0 0 0 0);\n\n// We use these to control list styles.\n// $side-nav-list-type: none;\n// $side-nav-list-position: inside;\n$side-nav-list-margin: rem-calc(0 0 0 0);\n\n// We use these to control link styles.\n$side-nav-link-color: $primary-color;\n$side-nav-link-color-active: scale-color($side-nav-link-color, $lightness: -40%);\n$side-nav-link-color-hover: scale-color($side-nav-link-color, $lightness: -40%);\n$side-nav-font-size: rem-calc(16);\n\n// $side-nav-link-bg-hover: hsla(0, 0, 0, 0.025);\n// $side-nav-link-margin: 0;\n// $side-nav-link-padding: rem-calc(7 14);\n// $side-nav-font-size: rem-calc(14);\n// $side-nav-font-weight: $font-weight-normal;\n// $side-nav-font-weight-active: $side-nav-font-weight;\n// $side-nav-font-family: $body-font-family;\n// $side-nav-font-family-active: $side-nav-font-family;\n\n// We use these to control heading styles.\n// $side-nav-heading-color: $side-nav-link-color;\n// $side-nav-heading-font-size: $side-nav-font-size;\n// $side-nav-heading-font-weight: bold;\n// $side-nav-heading-text-transform: uppercase;\n\n// We use these to control border styles\n$side-nav-divider-size: 1px;\n$side-nav-divider-style: solid;\n$side-nav-divider-color: $grey-1;\n\n\n\n// 27. Split Buttons\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-button-classes: $include-html-classes;\n\n// We use these to control different shared styles for Split Buttons\n// $split-button-function-factor: 10%;\n// $split-button-pip-color: $white;\n// $split-button-pip-color-alt: $oil;\n// $split-button-active-bg-tint: rgba(0,0,0,0.1);\n\n// We use these to control tiny split buttons\n// $split-button-padding-tny: $button-pip-tny * 10;\n// $split-button-span-width-tny: $button-pip-tny * 6;\n// $split-button-pip-size-tny: $button-pip-tny;\n// $split-button-pip-top-tny: $button-pip-tny * 2;\n// $split-button-pip-default-float-tny: rem-calc(-6);\n\n// We use these to control small split buttons\n// $split-button-padding-sml: $button-pip-sml * 10;\n// $split-button-span-width-sml: $button-pip-sml * 6;\n// $split-button-pip-size-sml: $button-pip-sml;\n// $split-button-pip-top-sml: $button-pip-sml * 1.5;\n// $split-button-pip-default-float-sml: rem-calc(-6);\n\n// We use these to control medium split buttons\n// $split-button-padding-med: $button-pip-med * 9;\n// $split-button-span-width-med: $button-pip-med * 5.5;\n// $split-button-pip-size-med: $button-pip-med - rem-calc(3);\n// $split-button-pip-top-med: $button-pip-med * 1.5;\n// $split-button-pip-default-float-med: rem-calc(-6);\n\n// We use these to control large split buttons\n// $split-button-padding-lrg: $button-pip-lrg * 8;\n// $split-button-span-width-lrg: $button-pip-lrg * 5;\n// $split-button-pip-size-lrg: $button-pip-lrg - rem-calc(6);\n// $split-button-pip-top-lrg: $button-pip-lrg + rem-calc(5);\n// $split-button-pip-default-float-lrg: rem-calc(-6);\n\n// 28. Sub Nav\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-nav-classes: $include-html-classes;\n\n// We use these to control margin and padding\n// $sub-nav-list-margin: rem-calc(-4 0 18);\n// $sub-nav-list-padding-top: rem-calc(4);\n\n// We use this to control the definition\n// $sub-nav-font-family: $body-font-family;\n// $sub-nav-font-size: rem-calc(14);\n// $sub-nav-font-color: $aluminum;\n// $sub-nav-font-weight: $font-weight-normal;\n// $sub-nav-text-decoration: none;\n// $sub-nav-padding: rem-calc(3 16);\n// $sub-nav-border-radius: 3px;\n// $sub-nav-font-color-hover: scale-color($sub-nav-font-color, $lightness: -25%);\n\n// We use these to control the active item styles\n// $sub-nav-active-font-weight: $font-weight-normal;\n// $sub-nav-active-bg: $primary-color;\n// $sub-nav-active-bg-hover: scale-color($sub-nav-active-bg, $lightness: -14%);\n// $sub-nav-active-color: $white;\n// $sub-nav-active-padding: $sub-nav-padding;\n// $sub-nav-active-cursor: default;\n\n// $sub-nav-item-divider: \"\";\n// $sub-nav-item-divider-margin: rem-calc(12);\n\n// 29. Switch\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-form-classes: $include-html-classes;\n\n// Controlling border styles and background colors for the switch container\n// $switch-border-color: scale-color($white, $lightness: -20%);\n// $switch-border-style: solid;\n// $switch-border-width: 1px;\n// $switch-bg: $white;\n\n// We use these to control the switch heights for our default classes\n// $switch-height-tny: rem-calc(22);\n// $switch-height-sml: rem-calc(28);\n// $switch-height-med: rem-calc(36);\n// $switch-height-lrg: rem-calc(44);\n// $switch-bottom-margin: rem-calc(20);\n\n// We use these to control default font sizes for our classes.\n// $switch-font-size-tny: 11px;\n// $switch-font-size-sml: 12px;\n// $switch-font-size-med: 14px;\n// $switch-font-size-lrg: 17px;\n// $switch-label-side-padding: 6px;\n\n// We use these to style the switch-paddle\n// $switch-paddle-bg: $white;\n// $switch-paddle-fade-to-color: scale-color($switch-paddle-bg, $lightness: -10%);\n// $switch-paddle-border-color: scale-color($switch-paddle-bg, $lightness: -35%);\n// $switch-paddle-border-width: 1px;\n// $switch-paddle-border-style: solid;\n// $switch-paddle-transition-speed: .1s;\n// $switch-paddle-transition-ease: ease-out;\n// $switch-positive-color: scale-color($success-color, $lightness: 94%);\n// $switch-negative-color: $white-smoke;\n\n// Outline Style for tabbing through switches\n// $switch-label-outline: 1px dotted $jumbo;\n\n// 30. Tables\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-table-classes: $include-html-classes;\n\n// These control the background color for the table and even rows\n// $table-bg: $white;\n$table-even-row-bg: $grey-1;\n\n// These control the table cell border style\n// $table-border-style: solid;\n// $table-border-size: 1px;\n// $table-border-color: $gainsboro;\n\n// These control the table head styles\n$table-head-bg: $grey-2;\n// $table-head-font-size: rem-calc(14);\n// $table-head-font-color: $jet;\n// $table-head-font-weight: $font-weight-bold;\n// $table-head-padding: rem-calc(8 10 10);\n\n// These control the row padding and font styles\n// $table-row-padding: rem-calc(9 10);\n// $table-row-font-size: rem-calc(14);\n// $table-row-font-color: $jet;\n// $table-line-height: rem-calc(18);\n\n// These are for controlling the layout, display and margin of tables\n// $table-layout: auto;\n// $table-display: table-cell;\n// $table-margin-bottom: rem-calc(20);\n\n// 31. Tabs\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-tabs-classes: $include-html-classes;\n\n// $tabs-navigation-padding: rem-calc(16);\n// $tabs-navigation-bg-color: $silver  ;\n// $tabs-navigation-active-bg-color: $white;\n// $tabs-navigation-hover-bg-color: scale-color($tabs-navigation-bg-color, $lightness: -6%);\n// $tabs-navigation-font-color: $jet;\n// $tabs-navigation-active-font-color: $tabs-navigation-font-color;\n// $tabs-navigation-font-size: rem-calc(16);\n// $tabs-navigation-font-family: $body-font-family;\n\n// $tabs-content-margin-bottom: rem-calc(24);\n// $tabs-content-padding: $column-gutter/2;\n\n// $tabs-vertical-navigation-margin-bottom: 1.25rem;\n\n// 32. Thumbnails\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-media-classes: $include-html-classes;\n\n// We use these to control border styles\n// $thumb-border-style: solid;\n// $thumb-border-width: 4px;\n// $thumb-border-color: $white;\n// $thumb-box-shadow: 0 0 0 1px rgba($black,.2);\n// $thumb-box-shadow-hover: 0 0 6px 1px rgba($primary-color,0.5);\n\n// Radius and transition speed for thumbs\n// $thumb-radius: $global-radius;\n// $thumb-transition-speed: 200ms;\n\n// 33. Tooltips\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-tooltip-classes: $include-html-classes;\n\n// $has-tip-border-bottom: dotted 1px $iron;\n// $has-tip-font-weight: $font-weight-bold;\n// $has-tip-font-color: $oil;\n// $has-tip-border-bottom-hover: dotted 1px scale-color($primary-color, $lightness: -55%);\n// $has-tip-font-color-hover: $primary-color;\n// $has-tip-cursor-type: help;\n\n// $tooltip-padding: rem-calc(12);\n// $tooltip-bg: $oil;\n// $tooltip-font-size: rem-calc(14);\n// $tooltip-font-weight: $font-weight-normal;\n// $tooltip-font-color: $white;\n// $tooltip-line-height: 1.3;\n// $tooltip-close-font-size: rem-calc(10);\n// $tooltip-close-font-weight: $font-weight-normal;\n// $tooltip-close-font-color: $monsoon;\n// $tooltip-font-size-sml: rem-calc(14);\n// $tooltip-radius: $global-radius;\n// $tooltip-rounded: $global-rounded;\n// $tooltip-pip-size: 5px;\n// $tooltip-max-width: 300px;\n\n// 34. Top Bar\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-top-bar-classes: $include-html-classes;\n\n// Height and margin\n$topbar-height: rem-calc(50);\n// $topbar-margin-bottom: 0;\n\n// Controlling the styles for the title in the top bar\n$topbar-title-weight: $font-weight-bold;\n$topbar-title-font-size: rem-calc(19);\n\n// Style the top bar dropdown elements\n// $topbar-dropdown-bg: $oil;\n// $topbar-dropdown-link-color: $white;\n// $topbar-dropdown-link-bg: $ci-2;\n// $topbar-dropdown-link-weight: $font-weight-normal;\n// $topbar-dropdown-toggle-size: 5px;\n// $topbar-dropdown-toggle-color: $ci-2;\n// $topbar-dropdown-toggle-alpha: 0.4;\n\n// Set the link colors and styles for top-level nav\n// $topbar-link-color: #000;\n// $topbar-link-color-hover: #000;\n// $topbar-link-color-active: #000;\n// $topbar-link-color-active-hover: #000;\n// $topbar-link-weight: $font-weight-normal;\n$topbar-link-font-size: rem-calc(15);\n// $topbar-link-hover-lightness: -10%; // Darken by 10%\n// $topbar-link-bg: $topbar-bg;\n// $topbar-link-bg-color-hover: #ff0;\n// $topbar-link-bg-hover: #f00;\n// $topbar-link-bg-active: $primary-color;\n// $topbar-link-bg-active-hover: scale-color($primary-color, $lightness: -14%);\n// $topbar-link-font-family: $body-font-family;\n$topbar-link-text-transform: uppercase;\n// $topbar-link-padding: $topbar-height / 3;\n// $topbar-back-link-size: $h5-font-size;\n// $topbar-link-dropdown-padding: 20px;\n\n// $topbar-button-font-size: 0.75rem;\n// $topbar-button-top: 7px;\n\n// $topbar-dropdown-label-color: #f77;\n// $topbar-dropdown-label-text-transform: uppercase;\n// $topbar-dropdown-label-font-weight: $font-weight-bold;\n// $topbar-dropdown-label-font-size: rem-calc(10);\n// $topbar-dropdown-label-bg: $oil;\n\n// Top menu icon styles\n$topbar-menu-link-transform: uppercase;\n// $topbar-menu-link-font-size: rem-calc(13);\n// $topbar-menu-link-weight: $font-weight-bold;\n// $topbar-menu-link-color: $white;\n// $topbar-menu-icon-color: $white;\n// $topbar-menu-link-color-toggled: $ci-6;\n// $topbar-menu-icon-color-toggled: $ci-6;\n\n// Transitions and breakpoint styles\n// $topbar-transition-speed: 300ms;\n// Using rem-calc for the below breakpoint causes issues with top bar\n$topbar-breakpoint: #{lower-bound($large-range)}; // Change to 9999px for always mobile layout\n$topbar-media-query: \"only screen and (min-width: #{$topbar-breakpoint})\" !default;\n\n// Divider Styles\n$topbar-divider-border-bottom: solid 0px scale-color($topbar-bg-color, $lightness: 23%);\n$topbar-divider-border-top: solid 0px scale-color($topbar-bg-color, $lightness: -50%);\n\n// Sticky Class\n// $topbar-sticky-class: \".sticky\";\n// $topbar-arrows: true; //Set false to remove the triangle icon from the menu item\n\n// 36. Visibility Classes\n// - - - - - - - - - - - - - - - - - - - - - - - - -\n\n// $include-html-visibility-classes: $include-html-classes;\n// $include-table-visibility-classes: true;\n// $include-legacy-visibility-classes: true;\n// $include-accessibility-classes: true;\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n@import \"buttons\";\n\n//\n// @variables\n//\n$include-html-form-classes: $include-html-classes !default;\n\n// We use this to set the base for lots of form spacing and positioning styles\n$form-spacing: rem-calc(16) !default;\n\n// We use these to style the labels in different ways\n$form-label-pointer: pointer !default;\n$form-label-font-size: rem-calc(14) !default;\n$form-label-font-weight: $font-weight-normal !default;\n$form-label-line-height: 1.5 !default;\n$form-label-font-color: scale-color($black, $lightness: 30%) !default;\n$form-label-small-transform: capitalize !default;\n$form-label-bottom-margin: 0 !default;\n$input-font-family: inherit !default;\n$input-font-color: rgba(0, 0, 0, 0.75) !default;\n$input-font-size: rem-calc(14) !default;\n$input-bg-color: $white !default;\n$input-focus-bg-color: scale-color($white, $lightness: -2%) !default;\n$input-border-color: scale-color($white, $lightness: -20%) !default;\n$input-focus-border-color: scale-color($white, $lightness: -40%) !default;\n$input-border-style: solid !default;\n$input-border-width: 1px !default;\n$input-border-radius: $global-radius !default;\n$input-disabled-bg: $gainsboro !default;\n$input-disabled-cursor: $cursor-default-value !default;\n$input-box-shadow: inset 0 1px 2px rgba(0, 0, 0, 0.1) !default;\n$input-include-glowing-effect: true !default;\n\n// We use these to style the fieldset border and spacing.\n$fieldset-border-style: solid !default;\n$fieldset-border-width: 1px !default;\n$fieldset-border-color: $gainsboro !default;\n$fieldset-padding: rem-calc(20) !default;\n$fieldset-margin: rem-calc(18 0) !default;\n\n// We use these to style the legends when you use them\n$legend-bg: $white !default;\n$legend-font-weight: $font-weight-bold !default;\n$legend-padding: rem-calc(0 3) !default;\n\n// We use these to style the prefix and postfix input elements\n$input-prefix-bg: scale-color($white, $lightness: -5%) !default;\n$input-prefix-border-color: scale-color($white, $lightness: -20%) !default;\n$input-prefix-border-size: 1px !default;\n$input-prefix-border-type: solid !default;\n$input-prefix-overflow: hidden !default;\n$input-prefix-font-color: $oil !default;\n$input-prefix-font-color-alt: $white !default;\n\n// We use this setting to turn on/off HTML5 number spinners (the up/down arrows)\n$input-number-spinners: true !default;\n\n// We use these to style the error states for inputs and labels\n$input-error-message-padding: rem-calc(6 9 9) !default;\n$input-error-message-top: -1px !default;\n$input-error-message-font-size: rem-calc(12) !default;\n$input-error-message-font-weight: $font-weight-normal !default;\n$input-error-message-font-style: italic !default;\n$input-error-message-font-color: $white !default;\n$input-error-message-bg-color: $alert-color !default;\n$input-error-message-font-color-alt: $oil !default;\n\n// We use this to style the glowing effect of inputs when focused\n$glowing-effect-fade-time: 0.45s !default;\n$glowing-effect-color: $input-focus-border-color !default;\n\n// Select variables\n$select-bg-color: $ghost !default;\n$select-hover-bg-color: scale-color($select-bg-color, $lightness: -3%) !default;\n\n//\n// @MIXINS\n//\n\n// We use this mixin to give us form styles for rows inside of forms\n@mixin form-row-base {\n  .row {\n    margin: 0 calc((-1 * $form-spacing) / 2);\n\n    .column,\n    .columns {\n      padding: 0 calc($form-spacing / 2);\n    }\n\n    // Use this to collapse the margins of a form row\n    &.collapse {\n      margin: 0;\n\n      .column,\n      .columns {\n        padding: 0;\n      }\n\n      input {\n        @include side-radius($opposite-direction, 0);\n      }\n\n    }\n  }\n\n  input.column,\n  input.columns,\n  textarea.column,\n  textarea.columns {\n    padding-#{$default-float}: calc($form-spacing / 2);\n  }\n}\n\n// @MIXIN\n//\n// We use this mixin to give all basic form elements their style\n@mixin form-element {\n  background-color: $input-bg-color;\n  font-family: $input-font-family;\n\n  border: {\n    style: $input-border-style;\n    width: $input-border-width;\n    color: $input-border-color;\n  }\n\n  box-shadow: $input-box-shadow;\n  color: $input-font-color;\n  display: block;\n  font-size: $input-font-size;\n  margin: 0 0 $form-spacing 0;\n  padding: calc($form-spacing / 2);\n  height: ($input-font-size + ($form-spacing * 1.5) - rem-calc(1));\n  width: 100%;\n  @include box-sizing(border-box);\n\n  @if $input-include-glowing-effect {\n    @include block-glowing-effect(focus, $glowing-effect-fade-time, $glowing-effect-color);\n  }\n\n  // Basic focus styles\n  &:focus {\n    background: $input-focus-bg-color;\n    border-color: $input-focus-border-color;\n    outline: none;\n  }\n\n  // Disabled Styles\n  &:disabled {\n    background-color: $input-disabled-bg;\n    cursor: $input-disabled-cursor;\n  }\n\n  // Disabled background input background color\n  &[disabled],\n  &[readonly],\n  fieldset[disabled] & {\n    background-color: $input-disabled-bg;\n    cursor: $input-disabled-cursor;\n  }\n}\n\n// @MIXIN\n//\n// We use this mixin to create form labels\n//\n// $alignment - Alignment options. Default: false. Options: [right, inline, false]\n// $base-style - Control whether or not the base styles come through. Default: true.\n@mixin form-label($alignment: false, $base-style: true) {\n\n  // Control whether or not the base styles come through.\n  @if $base-style {\n    font-size: $form-label-font-size;\n    color: $form-label-font-color;\n    cursor: $form-label-pointer;\n    display: block;\n    font-weight: $form-label-font-weight;\n    line-height: $form-label-line-height;\n    margin-bottom: $form-label-bottom-margin;\n  }\n\n  // Alignment options\n  @if $alignment ==right {\n    float: none !important;\n    text-align: right;\n  }\n\n  @else if $alignment ==inline {\n    margin: 0 0 $form-spacing 0;\n    padding: calc($form-spacing / 2) + rem-calc($input-border-width) 0;\n  }\n}\n\n// We use this mixin to create postfix/prefix form Labels\n@mixin prefix-postfix-base {\n  display: block;\n  position: relative;\n  z-index: 2;\n  text-align: center;\n  width: 100%;\n  padding-top: 0;\n  padding-bottom: 0;\n  border-style: $input-prefix-border-type;\n  border-width: $input-prefix-border-size;\n  overflow: $input-prefix-overflow;\n  font-size: $form-label-font-size;\n  height: ($input-font-size + ($form-spacing * 1.5) - rem-calc(1));\n  line-height: ($input-font-size + ($form-spacing * 1.5) - rem-calc(1));\n}\n\n// @MIXIN\n//\n// We use this mixin to create prefix label styles\n// $bg - Default:$input-prefix-bg || scale-color($white, $lightness: -5%) !default;\n// $is-button - Toggle position settings if prefix is a button. Default:false\n//\n@mixin prefix($bg: $input-prefix-bg, $border: $input-prefix-border-color, $is-button: false) {\n\n  @if $bg {\n    $bg-lightness: lightness($bg);\n    background: $bg;\n    border-#{$opposite-direction}: none;\n\n    // Control the font color based on background brightness\n    @if $bg-lightness >70% or $bg ==yellow {\n      color: $input-prefix-font-color;\n    }\n\n    @else {\n      color: $input-prefix-font-color-alt;\n    }\n  }\n\n  @if $border {\n    border-color: $border;\n  }\n\n  @if $is-button {\n    padding-#{$default-float}: 0;\n    padding-#{$opposite-direction}: 0;\n    padding-top: 0;\n    padding-bottom: 0;\n    text-align: center;\n    border: none;\n  }\n\n}\n\n// @MIXIN\n//\n// We use this mixin to create postfix label styles\n// $bg - Default:$input-prefix-bg || scale-color($white, $lightness: -5%) !default;\n// $is-button - Toggle position settings if prefix is a button. Default: false\n@mixin postfix($bg: $input-prefix-bg, $border: $input-prefix-border-color, $is-button: false) {\n\n  @if $bg {\n    $bg-lightness: lightness($bg);\n    background: $bg;\n    border-#{$default-float}: none;\n\n    // Control the font color based on background brightness\n    @if $bg-lightness >70% or $bg ==yellow {\n      color: $input-prefix-font-color;\n    }\n\n    @else {\n      color: $input-prefix-font-color-alt;\n    }\n  }\n\n  @if $border {\n    border-color: $border;\n  }\n\n  @if $is-button {\n    padding-#{$default-float}: 0;\n    padding-#{$opposite-direction}: 0;\n    padding-top: 0;\n    padding-bottom: 0;\n    text-align: center;\n    border: none;\n  }\n\n}\n\n// We use this mixin to style fieldsets\n@mixin fieldset {\n  border: $fieldset-border-width $fieldset-border-style $fieldset-border-color;\n  padding: $fieldset-padding;\n  margin: $fieldset-margin;\n\n  // and legend styles\n  legend {\n    font-weight: $legend-font-weight;\n    background: $legend-bg;\n    padding: $legend-padding;\n    margin: 0;\n    margin-#{$default-float}: rem-calc(-3);\n  }\n}\n\n// @MIXIN\n//\n// We use this mixin to control border and background color of error inputs\n// $color - Default: $alert-color (found in settings file)\n@mixin form-error-color($color: $alert-color) {\n  border-color: $color;\n  background-color: rgba($color, 0.1);\n\n  // Go back to normal on focus\n  &:focus {\n    background: $input-focus-bg-color;\n    border-color: $input-focus-border-color;\n  }\n}\n\n// @MIXIN\n//\n// We use this simple mixin to style labels for error inputs\n// $color - Default:$alert-color. Found in settings file\n@mixin form-label-error-color($color: $alert-color) {\n  color: $color;\n}\n\n// @MIXIN\n//\n// We use this mixin to create error message styles\n// $bg - Default: $alert-color (Found in settings file)\n@mixin form-error-message($bg: $input-error-message-bg-color) {\n  display: block;\n  padding: $input-error-message-padding;\n  margin-top: $input-error-message-top;\n  margin-bottom: $form-spacing;\n  font-size: $input-error-message-font-size;\n  font-weight: $input-error-message-font-weight;\n  font-style: $input-error-message-font-style;\n\n  // We can control the text color based on the brightness of the background.\n  $bg-lightness: lightness($bg);\n  background: $bg;\n\n  @if $bg-lightness < 70% or $bg ==yellow {\n    color: $input-error-message-font-color;\n  }\n\n  @else {\n    color: $input-error-message-font-color-alt;\n  }\n}\n\n// We use this mixin to style select elements\n@mixin form-select {\n  -webkit-appearance: none !important;\n  border-radius: 0;\n  background-color: $select-bg-color;\n\n  // Hide the dropdown arrow shown in newer IE versions\n  &::-ms-expand {\n    display: none;\n  }\n\n  // The custom arrow has some fake horizontal padding so we can align it\n  // from the right side of the element without relying on CSS3\n  background-image: url(data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZlcnNpb249IjEuMSIgeD0iMTJweCIgeT0iMHB4IiB3aWR0aD0iMjRweCIgaGVpZ2h0PSIzcHgiIHZpZXdCb3g9IjAgMCA2IDMiIGVuYWJsZS1iYWNrZ3JvdW5kPSJuZXcgMCAwIDYgMyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI+PHBvbHlnb24gcG9pbnRzPSI1Ljk5MiwwIDIuOTkyLDMgLTAuMDA4LDAgIi8+PC9zdmc+);\n\n  // We can safely use leftmost and rightmost now\n  background-position: if($text-direction =='rtl', 0%, 100%) center;\n\n  background-repeat: no-repeat;\n\n  border: {\n    style: $input-border-style;\n    width: $input-border-width;\n    color: $input-border-color;\n  }\n\n  padding: calc($form-spacing / 2);\n  font-size: $input-font-size;\n  font-family: $body-font-family;\n  color: $input-font-color;\n  line-height: normal;\n  @include radius(0);\n\n  &.radius {\n    @include radius($global-radius);\n  }\n\n  &:hover {\n    background-color: $select-hover-bg-color;\n    border-color: $input-focus-border-color;\n  }\n\n  // Disabled Styles\n  &:disabled {\n    background-color: $input-disabled-bg;\n    cursor: $input-disabled-cursor;\n  }\n}\n\n// We use this mixin to turn on/off HTML5 number spinners\n@mixin html5number($browser, $on: true) {\n  @if $on==false {\n    @if $browser==webkit {\n      -webkit-appearance: none;\n      margin: 0;\n    }\n\n    @else if $browser==moz {\n      -moz-appearance: textfield;\n    }\n  }\n}\n\n@include exports(\"form\") {\n  @if $include-html-form-classes {\n\n    /* Standard Forms */\n    form {\n      margin: 0 0 $form-spacing;\n    }\n\n    /* Using forms within rows, we need to set some defaults */\n    form .row {\n      @include form-row-base;\n    }\n\n    /* Label Styles */\n    label {\n      @include form-label;\n\n      &.right {\n        @include form-label(right, false);\n      }\n\n      &.inline {\n        @include form-label(inline, false);\n      }\n\n      /* Styles for required inputs */\n      small {\n        text-transform: $form-label-small-transform;\n        color: scale-color($form-label-font-color, $lightness: 15%);\n      }\n    }\n\n    /* Attach elements to the beginning or end of an input */\n    .prefix,\n    .postfix {\n      @include prefix-postfix-base;\n    }\n\n    /* Adjust padding, alignment and radius if pre/post element is a button */\n    .postfix.button {\n      @include button-size(false, false);\n      @include postfix(false, false, true);\n    }\n\n    .prefix.button {\n      @include button-size(false, false);\n      @include prefix(false, false, true);\n    }\n\n    .prefix.button.radius {\n      @include radius(0);\n      @include side-radius($default-float, $button-radius);\n    }\n\n    .postfix.button.radius {\n      @include radius(0);\n      @include side-radius($opposite-direction, $button-radius);\n    }\n\n    .prefix.button.round {\n      @include radius(0);\n      @include side-radius($default-float, $button-round);\n    }\n\n    .postfix.button.round {\n      @include radius(0);\n      @include side-radius($opposite-direction, $button-round);\n    }\n\n    /* Separate prefix and postfix styles when on span or label so buttons keep their own */\n    span.prefix,\n    label.prefix {\n      @include prefix();\n    }\n\n    span.postfix,\n    label.postfix {\n      @include postfix();\n    }\n\n    /* We use this to get basic styling on all basic form elements */\n    #{text-inputs(all, 'input')} {\n      -webkit-appearance: none;\n      border-radius: 0;\n      @include form-element;\n\n      @if $input-include-glowing-effect ==false {\n        @include single-transition(all, 0.15s, linear);\n      }\n\n      &.radius {\n        @include radius($input-border-radius);\n      }\n    }\n\n    form {\n      .row {\n        .prefix-radius.row.collapse {\n\n          input,\n          textarea,\n          select {\n            @include radius(0);\n            @include side-radius($opposite-direction, $button-radius);\n          }\n\n          .prefix {\n            @include radius(0);\n            @include side-radius($default-float, $button-radius);\n          }\n        }\n\n        .postfix-radius.row.collapse {\n\n          input,\n          textarea,\n          select {\n            @include radius(0);\n            @include side-radius($default-float, $button-radius);\n          }\n\n          .postfix {\n            @include radius(0);\n            @include side-radius($opposite-direction, $button-radius);\n          }\n        }\n\n        .prefix-round.row.collapse {\n\n          input,\n          textarea,\n          select {\n            @include radius(0);\n            @include side-radius($opposite-direction, $button-round);\n          }\n\n          .prefix {\n            @include radius(0);\n            @include side-radius($default-float, $button-round);\n          }\n        }\n\n        .postfix-round.row.collapse {\n\n          input,\n          textarea,\n          select {\n            @include radius(0);\n            @include side-radius($default-float, $button-round);\n          }\n\n          .postfix {\n            @include radius(0);\n            @include side-radius($opposite-direction, $button-round);\n          }\n        }\n      }\n    }\n\n    input[type=\"submit\"] {\n      -webkit-appearance: none;\n      border-radius: 0;\n    }\n\n    /* Respect enforced amount of rows for textarea */\n    textarea[rows] {\n      height: auto;\n    }\n\n    /* Not allow resize out of parent */\n    textarea {\n      max-width: 100%;\n    }\n\n    /* Add height value for select elements to match text input height */\n    select {\n      @include form-select;\n      height: ($input-font-size + ($form-spacing * 1.5) - rem-calc(1));\n    }\n\n    /* Adjust margin for form elements below */\n    input[type=\"file\"],\n    input[type=\"checkbox\"],\n    input[type=\"radio\"],\n    select {\n      margin: 0 0 $form-spacing 0;\n    }\n\n    input[type=\"checkbox\"]+label,\n    input[type=\"radio\"]+label {\n      display: inline-block;\n      margin-#{$default-float}: $form-spacing * .5;\n      margin-#{$opposite-direction}: $form-spacing;\n      margin-bottom: 0;\n      vertical-align: baseline;\n    }\n\n    /* Normalize file input width */\n    input[type=\"file\"] {\n      width: 100%;\n    }\n\n    /* HTML5 Number spinners settings */\n    input[type=number] {\n      @include html5number(moz, $input-number-spinners)\n    }\n\n    input[type=\"number\"]::-webkit-inner-spin-button,\n    input[type=\"number\"]::-webkit-outer-spin-button {\n      @include html5number(webkit, $input-number-spinners);\n    }\n\n    /* We add basic fieldset styling */\n    fieldset {\n      @include fieldset;\n    }\n\n    /* Error Handling */\n\n    #{data('abide')} {\n\n      .error small.error,\n      .error span.error,\n      span.error,\n      small.error {\n        @include form-error-message;\n      }\n\n      span.error,\n      small.error {\n        display: none;\n      }\n    }\n\n    span.error,\n    small.error {\n      @include form-error-message;\n    }\n\n    .error {\n\n      input,\n      textarea,\n      select {\n        margin-bottom: 0;\n      }\n\n      input[type=\"checkbox\"],\n      input[type=\"radio\"] {\n        margin-bottom: $form-spacing\n      }\n\n      label,\n      label.error {\n        @include form-label-error-color;\n      }\n\n      small.error {\n        @include form-error-message;\n      }\n\n      >label {\n        >small {\n          color: scale-color($form-label-font-color, $lightness: 15%);\n          background: transparent;\n          padding: 0;\n          text-transform: $form-label-small-transform;\n          font-style: normal;\n          font-size: 60%;\n          margin: 0;\n          display: inline;\n        }\n      }\n\n      span.error-message {\n        display: block;\n      }\n    }\n\n    input.error,\n    textarea.error,\n    select.error {\n      margin-bottom: 0;\n    }\n\n    label.error {\n      @include form-label-error-color;\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n@import \"grid\";\n@import \"buttons\";\n@import \"forms\";\n\n//\n// Top Bar Variables\n//\n$include-html-top-bar-classes: $include-html-classes !default;\n\n// Background color for the top bar\n$topbar-bg-color: $oil !default;\n$topbar-bg: $topbar-bg-color !default;\n\n// Height and margin\n$topbar-height: rem-calc(45) !default;\n$topbar-margin-bottom: 0 !default;\n\n// Controlling the styles for the title in the top bar\n$topbar-title-weight: $font-weight-normal !default;\n$topbar-title-font-size: rem-calc(17) !default;\n\n// Set the link colors and styles for top-level nav\n$topbar-link-color: $white !default;\n$topbar-link-color-hover: $white !default;\n$topbar-link-color-active: $white !default;\n$topbar-link-color-active-hover: $white !default;\n$topbar-link-weight: $font-weight-normal !default;\n$topbar-link-font-size: rem-calc(13) !default;\n$topbar-link-hover-lightness: -10% !default; // Darken by 10%\n$topbar-link-bg: $topbar-bg !default;\n$topbar-link-bg-hover: $oil !default;\n$topbar-link-bg-color-hover: $charcoal !default;\n$topbar-link-bg-active: $primary-color !default;\n$topbar-link-bg-active-hover: scale-color($primary-color, $lightness: -14%) !default;\n$topbar-link-font-family: $body-font-family !default;\n$topbar-link-text-transform: none !default;\n$topbar-link-padding: calc($topbar-height / 3) !default;\n$topbar-back-link-size: rem-calc(18) !default;\n$topbar-link-dropdown-padding: rem-calc(20) !default;\n$topbar-button-font-size: 0.75rem !default;\n$topbar-button-top: 7px !default;\n\n// Style the top bar dropdown elements\n$topbar-dropdown-bg: $oil !default;\n$topbar-dropdown-link-color: $white !default;\n$topbar-dropdown-link-color-hover: $topbar-link-color-hover !default;\n$topbar-dropdown-link-bg: $oil !default;\n$topbar-dropdown-link-bg-hover: $oil !default;\n$topbar-dropdown-link-weight: $font-weight-normal !default;\n$topbar-dropdown-toggle-size: 5px !default;\n$topbar-dropdown-toggle-color: $white !default;\n$topbar-dropdown-toggle-alpha: 0.4 !default;\n\n$topbar-dropdown-label-color: $monsoon !default;\n$topbar-dropdown-label-text-transform: uppercase !default;\n$topbar-dropdown-label-font-weight: $font-weight-bold !default;\n$topbar-dropdown-label-font-size: rem-calc(10) !default;\n$topbar-dropdown-label-bg: $oil !default;\n\n// Top menu icon styles\n$topbar-menu-link-transform: uppercase !default;\n$topbar-menu-link-font-size: rem-calc(13) !default;\n$topbar-menu-link-weight: $font-weight-bold !default;\n$topbar-menu-link-color: $white !default;\n$topbar-menu-icon-color: $white !default;\n$topbar-menu-link-color-toggled: $jumbo !default;\n$topbar-menu-icon-color-toggled: $jumbo !default;\n\n// Transitions and breakpoint styles\n$topbar-transition-speed: 300ms !default;\n// Using rem-calc for the below breakpoint causes issues with top bar\n$topbar-breakpoint: #{lower-bound($medium-range)} !default; // Change to 9999px for always mobile layout\n$topbar-media-query: $medium-up !default;\n\n// Top-bar input styles\n$topbar-input-height: rem-calc(28) !default;\n\n// Divider Styles\n$topbar-divider-border-bottom: solid 1px scale-color($topbar-bg-color, $lightness: 13%) !default;\n$topbar-divider-border-top: solid 1px scale-color($topbar-bg-color, $lightness: -50%) !default;\n\n// Sticky Class\n$topbar-sticky-class: \".sticky\" !default;\n$topbar-arrows: true !default; //Set false to remove the triangle icon from the menu item\n$topbar-dropdown-arrows: true !default; //Set false to remove the \\00bb >> text from dropdown subnavigation li\n\n// Accessibility mixins for hiding and showing the menu dropdown items\n@mixin topbar-hide-dropdown {\n  // Makes an element visually hidden by default, but visible when focused.\n  display: block;\n  @include element-invisible();\n}\n\n@mixin topbar-show-dropdown {\n  display: block;\n  @include element-invisible-off();\n  position: absolute !important; // Reset the position from static to absolute\n}\n\n@include exports(\"top-bar\") {\n\n  @if $include-html-top-bar-classes {\n\n    // Used to provide media query values for javascript components.\n    // This class is generated despite the value of $include-html-top-bar-classes\n    // to ensure width calculations work correctly.\n    meta.foundation-mq-topbar {\n      font-family: \"/\" + unquote($topbar-media-query) + \"/\";\n      width: $topbar-breakpoint;\n    }\n\n    /* Wrapped around .top-bar to contain to grid width */\n    .contain-to-grid {\n      width: 100%;\n      background: $topbar-bg;\n\n      .top-bar {\n        margin-bottom: $topbar-margin-bottom;\n      }\n    }\n\n    // Wrapped around .top-bar to make it stick to the top\n    .fixed {\n      width: 100%;\n      #{$default-float}: 0;\n      position: fixed;\n      top: 0;\n      z-index: 99;\n\n      &.expanded:not(.top-bar) {\n        overflow-y: auto;\n        height: auto;\n        width: 100%;\n        max-height: 100%;\n\n        .title-area {\n          position: fixed;\n          width: 100%;\n          z-index: 99;\n        }\n\n        // Ensure you can scroll the menu on small screens\n        .top-bar-section {\n          z-index: 98;\n          margin-top: $topbar-height;\n        }\n      }\n    }\n\n    .top-bar {\n      overflow: hidden;\n      height: $topbar-height;\n      line-height: $topbar-height;\n      position: relative;\n      background: $topbar-bg;\n      margin-bottom: $topbar-margin-bottom;\n\n      // Topbar Global list Styles\n      ul {\n        margin-bottom: 0;\n        list-style: none;\n      }\n\n      .row {\n        max-width: none;\n      }\n\n      form,\n      input {\n        margin-bottom: 0;\n      }\n\n      input {\n        height: $topbar-input-height;\n        padding-top: .35rem;\n        padding-bottom: .35rem;\n        font-size: $topbar-button-font-size;\n      }\n\n      .button,\n      button {\n        padding-top: .35rem + rem-calc(1);\n        padding-bottom: .35rem + rem-calc(1);\n        margin-bottom: 0;\n        font-size: $topbar-button-font-size;\n        // position: relative;\n        // top: -1px;\n\n        // Corrects a slight misalignment when put next to an input field\n        @media #{$small-only} {\n          position: relative;\n          top: -1px;\n        }\n      }\n\n      // Title Area\n      .title-area {\n        position: relative;\n        margin: 0;\n      }\n\n      .name {\n        height: $topbar-height;\n        margin: 0;\n        font-size: $rem-base;\n\n        h1,\n        h2,\n        h3,\n        h4,\n        p,\n        span {\n          line-height: $topbar-height;\n          font-size: $topbar-title-font-size;\n          margin: 0;\n\n          a {\n            font-weight: $topbar-title-weight;\n            color: $topbar-link-color;\n            width: 75%;\n            display: block;\n            padding: 0 $topbar-link-padding;\n          }\n        }\n      }\n\n      // Menu toggle button on small devices\n      .toggle-topbar {\n        position: absolute;\n        #{$opposite-direction}: 0;\n        top: 0;\n\n        a {\n          color: $topbar-link-color;\n          text-transform: $topbar-menu-link-transform;\n          font-size: $topbar-menu-link-font-size;\n          font-weight: $topbar-menu-link-weight;\n          position: relative;\n          display: block;\n          padding: 0 $topbar-link-padding;\n          height: $topbar-height;\n          line-height: $topbar-height;\n        }\n\n        // Adding the class \"menu-icon\" will add the 3-line icon people love and adore.\n        &.menu-icon {\n          top: 50%;\n          margin-top: -16px;\n\n          a {\n            @if $text-direction ==rtl {\n              text-indent: -58px;\n            }\n\n            height: 34px;\n            line-height: 33px;\n            padding: 0 $topbar-link-padding+rem-calc(25) 0 $topbar-link-padding;\n            color: $topbar-menu-link-color;\n            position: relative;\n\n            & {\n              // @include hamburger icon\n              //\n              // We use this to create the icon with three lines aka the hamburger icon, the menu-icon or the navicon\n              // $width - Width of hamburger icon\n              // $left - If false, icon will be centered horizontally || explicitly set value in rem\n              // $top - If false, icon will be centered vertically || explicitly set value in rem\n              // $thickness - thickness of lines in hamburger icon, set value in px\n              // $gap - spacing between the lines in hamburger icon, set value in px\n              // $color - icon color\n              // $hover-color - icon color during hover, here it isn't set b/c it would override $topbar-menu-icon-color-toggled\n              // $offcanvas - Set to false of @include in topbar\n              @include hamburger(16px, false, 0, 1px, 6px, $topbar-menu-icon-color, \"\", false);\n            }\n          }\n        }\n      }\n\n      // Change things up when the top-bar is expanded\n      &.expanded {\n        height: auto;\n        background: transparent;\n\n        .title-area {\n          background: $topbar-bg;\n        }\n\n        .toggle-topbar {\n          a {\n            color: $topbar-menu-link-color-toggled;\n\n            span::after {\n              // Shh, don't tell, but box-shadows create the menu icon :)\n              // Change the color of the bars when the menu is expanded, using given thickness from hamburger() above\n              box-shadow: 0 0 0 1px $topbar-menu-icon-color-toggled,\n                0 7px 0 1px $topbar-menu-icon-color-toggled,\n                0 14px 0 1px $topbar-menu-icon-color-toggled;\n            }\n          }\n        }\n      }\n    }\n\n    // Right and Left Navigation that stacked by default\n    .top-bar-section {\n      #{$default-float}: 0;\n      position: relative;\n      width: auto;\n      @include single-transition($default-float, $topbar-transition-speed);\n\n      ul {\n        padding: 0;\n        width: 100%;\n        height: auto;\n        display: block;\n        font-size: $rem-base;\n        margin: 0;\n      }\n\n      .divider,\n      [role=\"separator\"] {\n        border-top: $topbar-divider-border-top;\n        clear: both;\n        height: 1px;\n        width: 100%;\n      }\n\n      ul li {\n        background: $topbar-dropdown-bg;\n\n        &>a {\n          display: block;\n          width: 100%;\n          color: $topbar-link-color;\n          padding: 12px 0 12px 0;\n          padding-#{$default-float}: $topbar-link-padding;\n          font-family: $topbar-link-font-family;\n          font-size: $topbar-link-font-size;\n          font-weight: $topbar-link-weight;\n          text-transform: $topbar-link-text-transform;\n\n          &.button {\n            font-size: $topbar-link-font-size;\n            padding-#{$opposite-direction}: $topbar-link-padding;\n            padding-#{$default-float}: $topbar-link-padding;\n            @include button-style($bg: $primary-color);\n          }\n\n          &.button.secondary {\n            @include button-style($bg: $secondary-color);\n          }\n\n          &.button.success {\n            @include button-style($bg: $success-color);\n          }\n\n          &.button.alert {\n            @include button-style($bg: $alert-color);\n          }\n\n          &.button.warning {\n            @include button-style($bg: $warning-color);\n          }\n        }\n\n        >button {\n          font-size: $topbar-link-font-size;\n          padding-#{$opposite-direction}: $topbar-link-padding;\n          padding-#{$default-float}: $topbar-link-padding;\n          @include button-style($bg: $primary-color);\n\n          &.secondary {\n            @include button-style($bg: $secondary-color);\n          }\n\n          &.success {\n            @include button-style($bg: $success-color);\n          }\n\n          &.alert {\n            @include button-style($bg: $alert-color);\n          }\n\n          &.warning {\n            @include button-style($bg: $warning-color);\n          }\n        }\n\n        // Apply the hover link color when it has that class\n        &:hover:not(.has-form)>a {\n          background-color: $topbar-link-bg-color-hover;\n\n          @if ($topbar-link-bg-hover) {\n            background: $topbar-link-bg-hover;\n          }\n\n          color: $topbar-link-color-hover;\n        }\n\n        // Apply the active link color when it has that class\n        &.active>a {\n          background: $topbar-link-bg-active;\n          color: $topbar-link-color-active;\n\n          &:hover {\n            background: $topbar-link-bg-active-hover;\n            color: $topbar-link-color-active-hover;\n          }\n        }\n      }\n\n      // Add some extra padding for list items contains buttons\n      .has-form {\n        padding: $topbar-link-padding;\n      }\n\n      // Styling for list items that have a dropdown within them.\n      .has-dropdown {\n        position: relative;\n\n        &>a {\n          &:after {\n            @if ($topbar-arrows) {\n              @include css-triangle($topbar-dropdown-toggle-size, rgba($topbar-dropdown-toggle-color, $topbar-dropdown-toggle-alpha), $default-float);\n            }\n\n            margin-#{$opposite-direction}: $topbar-link-padding;\n            margin-top: -(calc($topbar-dropdown-toggle-size / 2)) - 2;\n            position: absolute;\n            top: 50%;\n            #{$opposite-direction}: 0;\n          }\n        }\n\n        &.moved {\n          position: static;\n\n          &>.dropdown {\n            @include topbar-show-dropdown();\n            width: 100%;\n          }\n\n          &>a:after {\n            display: none;\n          }\n        }\n      }\n\n      // Styling elements inside of dropdowns\n      .dropdown {\n        padding: 0;\n        position: absolute;\n        #{$default-float}: 100%;\n        top: 0;\n        z-index: 99;\n        @include topbar-hide-dropdown();\n\n        li {\n          width: 100%;\n          height: auto;\n\n          a {\n            font-weight: $topbar-dropdown-link-weight;\n            padding: 8px $topbar-link-padding;\n\n            &.parent-link {\n              font-weight: $topbar-link-weight;\n            }\n          }\n\n          &.title h5,\n          &.parent-link {\n            // Back Button\n            margin-bottom: 0;\n            margin-top: 0;\n            font-size: $topbar-back-link-size;\n\n            a {\n              color: $topbar-link-color;\n              // line-height: ($topbar-height / 2);\n              display: block;\n\n              &:hover {\n                background: none;\n              }\n            }\n          }\n\n          &.has-form {\n            padding: 8px $topbar-link-padding;\n          }\n\n          .button,\n          button {\n            top: auto;\n          }\n        }\n\n        label {\n          padding: 8px $topbar-link-padding 2px;\n          margin-bottom: 0;\n          text-transform: $topbar-dropdown-label-text-transform;\n          color: $topbar-dropdown-label-color;\n          font-weight: $topbar-dropdown-label-font-weight;\n          font-size: $topbar-dropdown-label-font-size;\n        }\n      }\n    }\n\n    .js-generated {\n      display: block;\n    }\n\n\n    // Top Bar styles intended for screen sizes above the breakpoint.\n    @media #{$topbar-media-query} {\n      .top-bar {\n        background: $topbar-bg;\n        @include clearfix;\n        overflow: visible;\n\n        .toggle-topbar {\n          display: none;\n        }\n\n        .title-area {\n          float: $default-float;\n        }\n\n        .name h1 a {\n          width: auto;\n        }\n\n        input,\n        .button,\n        button {\n          font-size: rem-calc(14);\n          position: relative;\n          height: $topbar-input-height;\n          top: calc(($topbar-height - $topbar-input-height) / 2);\n        }\n\n        &.expanded {\n          background: $topbar-bg;\n        }\n      }\n\n      .contain-to-grid .top-bar {\n        max-width: $row-width;\n        margin: 0 auto;\n        margin-bottom: $topbar-margin-bottom;\n      }\n\n      .top-bar-section {\n        @include single-transition(none, 0, 0);\n        #{$default-float}: 0 !important;\n\n        ul {\n          width: auto;\n          height: auto !important;\n          display: inline;\n\n          li {\n            float: $default-float;\n\n            .js-generated {\n              display: none;\n            }\n          }\n        }\n\n        li {\n          &.hover {\n            >a:not(.button) {\n              background-color: $topbar-link-bg-color-hover;\n\n              @if ($topbar-link-bg-hover) {\n                background: $topbar-link-bg-hover;\n              }\n\n              color: $topbar-link-color-hover;\n            }\n          }\n\n          &:not(.has-form) {\n            a:not(.button) {\n              padding: 0 $topbar-link-padding;\n              line-height: $topbar-height;\n              background: $topbar-link-bg;\n\n              &:hover {\n                background-color: $topbar-link-bg-color-hover;\n\n                @if ($topbar-link-bg-hover) {\n                  background: $topbar-link-bg-hover;\n                }\n              }\n            }\n          }\n\n          &.active:not(.has-form) {\n            a:not(.button) {\n              padding: 0 $topbar-link-padding;\n              line-height: $topbar-height;\n              color: $topbar-link-color-active;\n              background: $topbar-link-bg-active;\n\n              &:hover {\n                background: $topbar-link-bg-active-hover;\n                color: $topbar-link-color-active-hover;\n              }\n            }\n          }\n        }\n\n        .has-dropdown {\n          @if($topbar-arrows) {\n            &>a {\n              padding-#{$opposite-direction}: $topbar-link-padding + $topbar-link-dropdown-padding !important;\n\n              &:after {\n                @include css-triangle($topbar-dropdown-toggle-size, rgba($topbar-dropdown-toggle-color, $topbar-dropdown-toggle-alpha), top);\n                margin-top: -(calc($topbar-dropdown-toggle-size / 2));\n                top: calc($topbar-height / 2);\n              }\n            }\n          }\n\n          &.moved {\n            position: relative;\n\n            &>.dropdown {\n              @include topbar-hide-dropdown();\n            }\n          }\n\n          &.hover,\n          &.not-click:hover {\n            &>.dropdown {\n              @include topbar-show-dropdown();\n            }\n          }\n\n          >a:focus+.dropdown {\n            @include topbar-show-dropdown();\n          }\n\n          .dropdown li.has-dropdown {\n            &>a {\n              @if ($topbar-dropdown-arrows) {\n                &:after {\n                  border: none;\n                  content: \"\\00bb\";\n                  top: 1rem;\n                  margin-top: -1px;\n                  #{$opposite-direction}: 5px;\n                  line-height: 1.2;\n                }\n              }\n            }\n          }\n        }\n\n        .dropdown {\n          #{$default-float}: 0;\n          top: auto;\n          background: transparent;\n          min-width: 100%;\n\n          li {\n            a {\n              color: $topbar-dropdown-link-color;\n              line-height: $topbar-height;\n              white-space: nowrap;\n              padding: 12px $topbar-link-padding;\n              background: $topbar-dropdown-link-bg;\n            }\n\n            &:not(.has-form):not(.active) {\n              &>a:not(.button) {\n                color: $topbar-dropdown-link-color;\n                background: $topbar-dropdown-link-bg;\n              }\n\n              &:hover>a:not(.button) {\n                color: $topbar-dropdown-link-color-hover;\n                background-color: $topbar-link-bg-color-hover;\n\n                @if ($topbar-dropdown-link-bg-hover) {\n                  background: $topbar-dropdown-link-bg-hover;\n                }\n              }\n            }\n\n            label {\n              white-space: nowrap;\n              background: $topbar-dropdown-label-bg;\n            }\n\n            // Second Level Dropdowns\n            .dropdown {\n              #{$default-float}: 100%;\n              top: 0;\n            }\n          }\n        }\n\n        &>ul>.divider,\n        &>ul>[role=\"separator\"] {\n          border-bottom: none;\n          border-top: none;\n          border-#{$opposite-direction}: $topbar-divider-border-bottom;\n          clear: none;\n          height: $topbar-height;\n          width: 0;\n        }\n\n        .has-form {\n          background: $topbar-link-bg;\n          padding: 0 calc($topbar-height / 3);\n          height: $topbar-height;\n        }\n\n        // Position overrides for ul.right and ul.left\n        .#{$opposite-direction} {\n          li .dropdown {\n            #{$default-float}: auto;\n            #{$opposite-direction}: 0;\n\n            li .dropdown {\n              #{$opposite-direction}: 100%;\n            }\n          }\n        }\n\n        .#{$default-float} {\n          li .dropdown {\n            #{$opposite-direction}: auto;\n            #{$default-float}: 0;\n\n            li .dropdown {\n              #{$default-float}: 100%;\n            }\n          }\n        }\n      }\n\n      // Degrade gracefully when Javascript is disabled. Displays dropdown and changes\n      // background & text color on hover.\n      .no-js .top-bar-section {\n        ul li {\n\n          // Apply the hover link color when it has that class\n          &:hover>a {\n            background-color: $topbar-link-bg-color-hover;\n\n            @if ($topbar-link-bg-hover) {\n              background: $topbar-link-bg-hover;\n            }\n\n            color: $topbar-link-color-hover;\n          }\n\n          // Apply the active link color when it has that class\n          &:active>a {\n            background: $topbar-link-bg-active;\n            color: $topbar-link-color-active;\n          }\n        }\n\n        .has-dropdown {\n          &:hover {\n            &>.dropdown {\n              @include topbar-show-dropdown();\n            }\n          }\n\n          >a:focus+.dropdown {\n            @include topbar-show-dropdown();\n          }\n        }\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n\n$include-html-accordion-classes: $include-html-classes !default;\n\n$accordion-navigation-padding: rem-calc(16) !default;\n$accordion-navigation-bg-color: $silver !default;\n$accordion-navigation-hover-bg-color: scale-color($accordion-navigation-bg-color, $lightness: -5%) !default;\n$accordion-navigation-active-bg-color: scale-color($accordion-navigation-bg-color, $lightness: -3%) !default;\n$accordion-navigation-font-color: $jet !default;\n$accordion-navigation-font-size: rem-calc(16) !default;\n$accordion-navigation-font-family: $body-font-family !default;\n\n$accordion-content-padding: calc($column-gutter / 2) !default;\n$accordion-content-active-bg-color: $white !default;\n\n\n//  Mixin: accordion-container()\n//  Description: Responsible for the container component of accordions, generating styles relating to a margin of zero and a clearfix\n//  Explicit Dependencies: a clearfix mixin *is* defined.\n//  Implicit Dependencies: None\n\n@mixin accordion-container() {\n  @include clearfix;\n  margin-bottom: 0;\n}\n\n//  Mixin: accordion-navigation( $bg, $hover-bg, $active-bg, $padding, $active_class,  $font-color, $font-size, $font-family){\n//    @params $bg-color: [ color or string ]: Specify the background color for the navigation element\n//    @params $hover-bg-color [ color or string ]: Specify the background color for the navigation element when hovered\n//    @params $active-bg [ color or string ]: Specify the background color for the navigation element when clicked and not released.\n//    @params $active_class [ string ]: Specify the class name used to keep track of which accordion tab should be visible\n//    @params $font-color [ color or string ]: Color of the font for accordion\n//    @params $font-size [ number ]: Specify the font-size of the text inside the navigation element\n//    @params $font-family [ string ]: Specify the font family for the text of the navigation of the accordion\n\n@mixin accordion-navigation($bg: $accordion-navigation-bg-color, $hover-bg: $accordion-navigation-hover-bg-color, $active-bg: $accordion-navigation-active-bg-color, $padding: $accordion-navigation-padding, $active_class: 'active', $font-color: $accordion-navigation-font-color, $font-size: $accordion-navigation-font-size, $font-family: $accordion-navigation-font-family ) {\n  display: block;\n  margin-bottom: 0 !important;\n\n  @if type-of($active_class) !=\"string\" {\n    @warn \"`#{$active_class}` isn't a valid string. A valid string is needed to correctly be interpolated as a CSS class. CSS classes cannot start with a number or consist of only numbers. CSS will not be generated for the active state of this navigation component.\"\n  }\n\n  @else {\n    &.#{ $active_class }>a {\n      background: $active-bg;\n    }\n  }\n\n  >a {\n    background: $bg;\n    color: $font-color;\n\n    @if type-of($padding) !=number {\n      @warn \"`#{$padding}` was read as #{type-of($padding)}\";\n\n      @if $accordion-navigation-padding !=null {\n        @warn \"#{$padding} was read as a #{type-of($padding)}\";\n        @warn \"`#{$padding}` isn't a valid number. $accordion-navigation-padding (#{$accordion-navigation-padding}) will be used instead.)\";\n        padding: $accordion-navigation-padding;\n      }\n\n      @else {\n        @warn \"`#{$padding}` isn't a valid number and $accordion-navigation-padding is missing. A value of `null` is returned to not output an invalid value for padding\";\n        padding: null;\n      }\n    }\n\n    @else {\n      padding: $padding;\n    }\n\n    display: block;\n    font-family: $font-family;\n\n    @if type-of($font-size) !=number {\n      @warn \"`#{$font-size}` was read as a #{type-of($font-size)}\";\n\n      @if $accordion-navigation-font-size !=null {\n        @warn \"`#{$font-size}` is not a valid number. The value of $accordion-navigation-font-size will be used instead (#{$accordion-navigation-font-size}).\";\n        font-size: $accordion-navigation-font-size;\n      }\n\n      @else {\n        @warn \"`#{$font-size}` is not a valid number and the default value of $accordion-navigation-font-size is not defined. A value of `null` will be returned to not generate an invalid value for font-size.\";\n        font-size: null;\n\n      }\n    }\n\n    @else {\n      font-size: $font-size;\n    }\n\n    &:hover {\n      background: $hover-bg;\n    }\n  }\n}\n\n//  Mixin: accordion-content($bg, $padding, $active-class)\n//    @params $padding [ number ]: Padding for the content of the container\n//    @params $bg [ color  ]: Background color for the content when it's visible\n//    @params $active_class [ string ]: Class name used to keep track of which accordion tab should be visible.\n\n@mixin accordion-content($bg: $accordion-content-active-bg-color, $padding: $accordion-content-padding, $active_class: 'active') {\n  display: none;\n\n  @if type-of($padding) !=\"number\" {\n    @warn \"#{$padding} was read as a #{type-of($padding)}\";\n\n    @if $accordion-content-padding !=null {\n      @warn \"`#{$padding}` isn't a valid number. $accordion-content-padding used instead\";\n      padding: $accordion-content-padding;\n    }\n\n    @else {\n      @warn \"`#{$padding}` isn't a valid number and the default value of $accordion-content-padding is not defined. A value of `null` is returned to not output an invalid value for padding.\";\n      padding: null;\n    }\n  }\n\n  @else {\n    padding: $padding;\n  }\n\n  @if type-of($active_class) !=\"string\" {\n    @warn \"`#{$active_class}` isn't a valid string. A valid string is needed to correctly be interpolated as a CSS class. CSS classes cannot start with a number or consist of only numbers. CSS will not be generated for the active state of the content. \"\n  }\n\n  @else {\n    &.#{$active_class} {\n      display: block;\n      background: $bg;\n    }\n  }\n}\n\n@include exports(\"accordion\") {\n  @if $include-html-accordion-classes {\n    .accordion {\n      @include clearfix;\n      margin-bottom: 0;\n\n      .accordion-navigation,\n      dd {\n        display: block;\n        margin-bottom: 0 !important;\n\n        &.active>a {\n          background: $accordion-navigation-active-bg-color;\n        }\n\n        >a {\n          background: $accordion-navigation-bg-color;\n          color: $accordion-navigation-font-color;\n          padding: $accordion-navigation-padding;\n          display: block;\n          font-family: $accordion-navigation-font-family;\n          font-size: $accordion-navigation-font-size;\n\n          &:hover {\n            background: $accordion-navigation-hover-bg-color;\n          }\n        }\n\n        >.content {\n          display: none;\n          padding: $accordion-content-padding;\n\n          &.active {\n            display: block;\n            background: $accordion-content-active-bg-color;\n          }\n        }\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// Alert Box Variables\n//\n$include-html-alert-classes: $include-html-classes !default;\n\n// We use this to control alert padding.\n$alert-padding-top: rem-calc(14) !default;\n$alert-padding-default-float: $alert-padding-top !default;\n$alert-padding-opposite-direction: $alert-padding-top + rem-calc(10) !default;\n$alert-padding-bottom: $alert-padding-top !default;\n\n// We use these to control text style.\n$alert-font-weight: $font-weight-normal !default;\n$alert-font-size: rem-calc(13) !default;\n$alert-font-color: $white !default;\n$alert-font-color-alt: scale-color($secondary-color, $lightness: -66%) !default;\n\n// We use this for close hover effect.\n$alert-function-factor: -14% !default;\n\n// We use these to control border styles.\n$alert-border-style: solid !default;\n$alert-border-width: 1px !default;\n$alert-border-color: scale-color($primary-color, $lightness: $alert-function-factor) !default;\n$alert-bottom-margin: rem-calc(20) !default;\n\n// We use these to style the close buttons\n$alert-close-color: $oil !default;\n$alert-close-top: 50% !default;\n$alert-close-position: rem-calc(4) !default;\n$alert-close-font-size: rem-calc(22) !default;\n$alert-close-opacity: 0.3 !default;\n$alert-close-opacity-hover: 0.5 !default;\n$alert-close-padding: 9px 6px 4px !default;\n$alert-close-background: inherit !default;\n\n// We use this to control border radius\n$alert-radius: $global-radius !default;\n\n$alert-transition-speed: 300ms !default;\n$alert-transition-ease: ease-out !default;\n\n//\n// Alert Mixins\n//\n\n// We use this mixin to create a default alert base.\n@mixin alert-base {\n  border-style: $alert-border-style;\n  border-width: $alert-border-width;\n  display: block;\n  font-weight: $alert-font-weight;\n  margin-bottom: $alert-bottom-margin;\n  position: relative;\n  padding: $alert-padding-top $alert-padding-opposite-direction $alert-padding-bottom $alert-padding-default-float;\n  font-size: $alert-font-size;\n  @include single-transition(opacity, $alert-transition-speed, $alert-transition-ease)\n}\n\n// We use this mixin to add alert styles\n//\n// $bg - The background of the alert. Default: $primary-color.\n@mixin alert-style($bg: $primary-color) {\n\n  // This finds the lightness percentage of the background color.\n  $bg-lightness: lightness($bg);\n\n  // We control which background color and border come through.\n  background-color: $bg;\n  border-color: scale-color($bg, $lightness: $alert-function-factor);\n\n  // We control the text color for you based on the background color.\n  @if $bg-lightness >70% {\n    color: $alert-font-color-alt;\n  }\n\n  @else {\n    color: $alert-font-color;\n  }\n\n}\n\n// We use this to create the close button.\n@mixin alert-close {\n  font-size: $alert-close-font-size;\n  padding: $alert-close-padding;\n  line-height: 0;\n  position: absolute;\n  top: $alert-close-top;\n  margin-top: -(calc($alert-close-font-size / 2));\n  #{$opposite-direction}: $alert-close-position;\n  color: $alert-close-color;\n  opacity: $alert-close-opacity;\n  background: $alert-close-background;\n\n  &:hover,\n  &:focus {\n    opacity: $alert-close-opacity-hover;\n  }\n}\n\n// We use this to quickly create alerts with a single mixin.\n//\n// $bg - Background of alert. Default: $primary-color.\n// $radius - Radius of alert box. Default: false.\n@mixin alert($bg: $primary-color, $radius: false) {\n  @include alert-base;\n  @include alert-style($bg);\n  @include radius($radius);\n}\n\n@include exports(\"alert-box\") {\n  @if $include-html-alert-classes {\n    .alert-box {\n      @include alert;\n\n      .close {\n        @include alert-close;\n      }\n\n      &.radius {\n        @include radius($alert-radius);\n      }\n\n      &.round {\n        @include radius($global-rounded);\n      }\n\n      &.success {\n        @include alert-style($success-color);\n      }\n\n      &.alert {\n        @include alert-style($alert-color);\n      }\n\n      &.secondary {\n        @include alert-style($secondary-color);\n      }\n\n      &.warning {\n        @include alert-style($warning-color);\n      }\n\n      &.info {\n        @include alert-style($info-color);\n      }\n\n      &.alert-close {\n        opacity: 0\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// Breadcrumb Variables\n//\n$include-html-nav-classes: $include-html-classes !default;\n\n// We use this to set the background color for the breadcrumb container.\n$crumb-bg: scale-color($secondary-color, $lightness: 55%) !default;\n\n// We use these to set the padding around the breadcrumbs.\n$crumb-padding: rem-calc(9 14 9) !default;\n$crumb-side-padding: rem-calc(12) !default;\n\n// We use these to control border styles.\n$crumb-function-factor: -10% !default;\n$crumb-border-size: 1px !default;\n$crumb-border-style: solid !default;\n$crumb-border-color: scale-color($crumb-bg, $lightness: $crumb-function-factor) !default;\n$crumb-radius: $global-radius !default;\n\n// We use these to set various text styles for breadcrumbs.\n$crumb-font-size: rem-calc(11) !default;\n$crumb-font-color: $primary-color !default;\n$crumb-font-color-current: $oil !default;\n$crumb-font-color-unavailable: $aluminum !default;\n$crumb-font-transform: uppercase !default;\n$crumb-link-decor: underline !default;\n\n// We use these to control the slash between breadcrumbs\n$crumb-slash-color: $base !default;\n$crumb-slash: \"/\" !default;\n\n//\n// Breadcrumb Mixins\n//\n\n// We use this mixin to create a container around our breadcrumbs\n@mixin crumb-container {\n  display: block;\n  padding: $crumb-padding;\n  overflow: hidden;\n  margin-#{$default-float}: 0;\n  list-style: none;\n  border-style: $crumb-border-style;\n  border-width: $crumb-border-size;\n\n  // We control which background color and border come through.\n  background-color: $crumb-bg;\n  border-color: $crumb-border-color;\n}\n\n// We use this mixin to create breadcrumb styles from list items.\n@mixin crumbs {\n\n  // A normal state will make the links look and act like clickable breadcrumbs.\n  margin: 0;\n  float: $default-float;\n  font-size: $crumb-font-size;\n  line-height: $crumb-font-size;\n  text-transform: $crumb-font-transform;\n  color: $crumb-font-color;\n\n  &:hover a, &:focus a { text-decoration: $crumb-link-decor; }\n\n  a {\n    color: $crumb-font-color;\n  }\n\n  // Current is for the link of the current page\n  &.current {\n    cursor: $cursor-default-value;\n    color: $crumb-font-color-current;\n    a {\n      cursor: $cursor-default-value;\n      color: $crumb-font-color-current;\n    }\n\n    &:hover, &:hover a,\n    &:focus, &:focus a { text-decoration: none; }\n  }\n\n  // Unavailable removed color and link styles so it looks inactive.\n  &.unavailable {\n    color: $crumb-font-color-unavailable;\n    a { color: $crumb-font-color-unavailable; }\n\n    &:hover,\n    &:hover a,\n    &:focus,\n    a:focus {\n      text-decoration: none;\n      color: $crumb-font-color-unavailable;\n      cursor: $cursor-default-value;\n    }\n  }\n\n  &:before {\n    content: \"#{$crumb-slash}\";\n    color: $crumb-slash-color;\n    margin: 0 $crumb-side-padding;\n    position: relative;\n    top: 1px;\n  }\n\n  &:first-child:before {\n    content: \" \";\n    margin: 0;\n  }\n}\n\n@include exports(\"breadcrumbs\") {\n  @if $include-html-nav-classes {\n    .breadcrumbs {\n      @include crumb-container;\n      @include radius($crumb-radius);\n\n      &>* {\n        @include crumbs;\n      }\n    }\n  }\n}\n\n/* Accessibility - hides the forward slash */\n[aria-label=\"breadcrumbs\"] [aria-hidden=\"true\"]:after {\n  content: \"/\";\n  }\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// Block Grid Variables\n//\n$include-html-block-grid-classes: $include-html-classes !default;\n$include-xl-html-block-grid-classes: false !default;\n\n// We use this to control the maximum number of block grid elements per row\n$block-grid-elements: 12 !default;\n$block-grid-default-spacing: rem-calc(20) !default;\n\n$align-block-grid-to-grid: false !default;\n\n@if $align-block-grid-to-grid {\n  $block-grid-default-spacing: $column-gutter;\n}\n\n// Enables media queries for block-grid classes. Set to false if writing semantic HTML.\n$block-grid-media-queries: true !default;\n\n//\n// Block Grid Mixins\n//\n\n// Create a custom block grid\n//\n// $per-row - # of items to display per row. Default: false.\n// $spacing - # of ems to use as padding on each block item. Default: rem-calc(20).\n// $base-style - Apply a base style to block grid. Default: true.\n@mixin block-grid($per-row: false,\n  $spacing: $block-grid-default-spacing,\n  $include-spacing: true,\n  $base-style: true) {\n\n  @if $base-style {\n    display: block;\n    padding: 0;\n\n    @if $align-block-grid-to-grid {\n      margin: 0;\n    }\n\n    @else {\n      margin: 0 calc(-1 * $spacing / 2);\n    }\n\n    @include clearfix;\n\n    &>li {\n      display: block;\n      height: auto;\n      float: $default-float;\n\n      @if $include-spacing {\n        padding: 0 calc($spacing / 2) $spacing;\n      }\n    }\n  }\n\n  @if $per-row {\n    &>li {\n      width: calc(100% / $per-row);\n\n      @if $include-spacing {\n        padding: 0 ($spacing/2) $spacing;\n      }\n\n      list-style: none;\n\n      &:nth-of-type(1n) {\n        clear: none;\n      }\n\n      &:nth-of-type(#{$per-row}n+1) {\n        clear: both;\n      }\n\n      @if $align-block-grid-to-grid {\n        @include block-grid-aligned($per-row, $spacing);\n      }\n    }\n  }\n}\n\n@mixin block-grid-aligned($per-row, $spacing) {\n  @for $i from 1 through $block-grid-elements {\n    @if $per-row >=$i {\n      $grid-column: '+'+$i;\n\n      @if $per-row ==$i {\n        $grid-column: '';\n      }\n\n      &:nth-of-type(#{$per-row}n#{unquote($grid-column)}) {\n        padding-left: ($spacing - (($spacing / $per-row) * ($per-row - ($i - 1))));\n        padding-right: ($spacing - (($spacing / $per-row) * $i));\n      }\n    }\n  }\n}\n\n// Generate presentational markup for block grid.\n//\n// $size - Name of class to use, i.e. \"large\" will generate .large-block-grid-1, .large-block-grid-2, etc.\n@mixin block-grid-html-classes($size, $include-spacing) {\n  @for $i from 1 through $block-grid-elements {\n    .#{$size}-block-grid-#{($i)} {\n      @include block-grid($i, $block-grid-default-spacing, $include-spacing, false);\n    }\n  }\n}\n\n@include exports(\"block-grid\") {\n  @if $include-html-block-grid-classes {\n\n    [class*=\"block-grid-\"] {\n      @include block-grid;\n    }\n\n    @if $block-grid-media-queries {\n      @media #{$small-up} {\n        @include block-grid-html-classes($size: small, $include-spacing: false);\n      }\n\n      @media #{$medium-up} {\n        @include block-grid-html-classes($size: medium, $include-spacing: false);\n      }\n\n      @media #{$large-up} {\n        @include block-grid-html-classes($size: large, $include-spacing: false);\n      }\n\n      @if $include-xl-html-block-grid-classes {\n        @media #{$xlarge-up} {\n          @include block-grid-html-classes($size: xlarge, $include-spacing: false);\n        }\n\n        @media #{$xxlarge-up} {\n          @include block-grid-html-classes($size: xxlarge, $include-spacing: false);\n        }\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n@import \"buttons\";\n\n//\n// Button Group Variables\n//\n$include-html-button-classes: $include-html-classes !default;\n\n// Sets the margin for the right side by default, and the left margin if right-to-left direction is used\n$button-bar-margin-opposite: rem-calc(10) !default;\n$button-group-border-width: 1px !default;\n\n//\n// Button Group Mixins\n//\n\n// We use this to add styles for a button group container\n@mixin button-group-container($styles: true, $float: false) {\n  @if $styles {\n    list-style: none;\n    margin: 0;\n    #{$default-float}: 0;\n    @include clearfix();\n  }\n\n  @if $float {\n    float: #{$default-float};\n    margin-#{$opposite-direction}: $button-bar-margin-opposite;\n\n    & div {\n      overflow: hidden;\n    }\n  }\n}\n\n// We use this to control styles for button groups\n@mixin button-group-style($radius: false, $even: false, $float: false, $orientation: horizontal) {\n\n  >button,\n  .button {\n    border-#{$default-float}: $button-group-border-width solid;\n    border-color: rgba(255, 255, 255, 0.5);\n  }\n\n  &:first-child {\n\n    button,\n    .button {\n      border-#{$default-float}: 0;\n    }\n  }\n\n  // We use this to control the flow, or remove those styles completely.\n  @if $float {\n    margin: 0;\n    float: $float;\n    display: list-item;\n\n    // Make sure the first child doesn't get the negative margin.\n    &:first-child {\n      margin-#{$default-float}: 0;\n    }\n  }\n\n  @else {\n    margin: 0 -2px;\n    display: inline-block;\n  }\n\n  @if $orientation ==vertical {\n    display: block;\n    margin: 0;\n\n    >button,\n    .button {\n      border-top: $button-group-border-width solid;\n      border-color: rgba(255, 255, 255, 0.5);\n      border-left-width: 0;\n      margin: 0;\n      display: block;\n    }\n\n    &:first-child {\n\n      button,\n      .button {\n        border-top: 0;\n      }\n    }\n  }\n\n  // We use these to control left and right radius on first/last buttons in the group.\n  @if $radius ==true {\n\n    &,\n    &>a,\n    &>button,\n    &>.button {\n      @include radius(0);\n    }\n\n    &:first-child,\n    &:first-child>a,\n    &:first-child>button,\n    &:first-child>.button {\n      @if $orientation ==vertical {\n        @include side-radius(top, $button-radius);\n      }\n\n      @else {\n        @include side-radius($default-float, $button-radius);\n      }\n    }\n\n    &:last-child,\n    &:last-child>a,\n    &:last-child>button,\n    &:last-child>.button {\n      @if $orientation ==vertical {\n        @include side-radius(bottom, $button-radius);\n      }\n\n      @else {\n        @include side-radius($opposite-direction, $button-radius);\n      }\n    }\n  }\n\n  @else if $radius {\n\n    &,\n    &>a,\n    &>button,\n    &>.button {\n      @include radius(0);\n    }\n\n    &:first-child,\n    &:first-child>a,\n    &:first-child>button,\n    &:first-child>.button {\n      @if $orientation ==vertical {\n        @include side-radius(top, $radius);\n      }\n\n      @else {\n        @include side-radius($default-float, $radius);\n      }\n    }\n\n    &:last-child,\n    &:last-child>a,\n    &:last-child>button,\n    &:last-child>.button {\n      @if $orientation ==vertical {\n        @include side-radius(bottom, $radius);\n      }\n\n      @else {\n        @include side-radius($opposite-direction, $radius);\n      }\n    }\n  }\n\n  // We use this to make the buttons even width across their container\n  @if $even {\n    width: percentage(calc((100/$even) / 100));\n\n    button,\n    .button {\n      width: 100%;\n    }\n  }\n}\n\n@include exports(\"button-group\") {\n  @if $include-html-button-classes {\n    .button-group {\n      @include button-group-container;\n\n      &>li {\n        @include button-group-style();\n      }\n\n      &.stack {\n        &>li {\n          @include button-group-style($orientation: vertical);\n          float: none;\n        }\n      }\n\n      &.stack-for-small {\n        &>li {\n          @include button-group-style($orientation: horizontal);\n\n          @media #{$small-only} {\n            @include button-group-style($orientation: vertical);\n          }\n        }\n      }\n\n      &.radius>* {\n        @include button-group-style($radius: $button-radius, $float: null);\n      }\n\n      &.radius.stack>* {\n        @include button-group-style($radius: $button-radius, $float: null, $orientation: vertical);\n      }\n\n      &.radius.stack-for-small>* {\n        @media #{$medium-up} {\n          @include button-group-style($radius: $button-radius, $orientation: horizontal);\n        }\n\n        @media #{$small-only} {\n          @include button-group-style($radius: $button-radius, $orientation: vertical);\n        }\n      }\n\n      &.round>* {\n        @include button-group-style($radius: $button-round, $float: null);\n      }\n\n      &.round.stack>* {\n        @include button-group-style($radius: $button-med, $float: null, $orientation: vertical);\n      }\n\n      &.round.stack-for-small>* {\n        @media #{$medium-up} {\n          @include button-group-style($radius: $button-round, $orientation: horizontal);\n        }\n\n        @media #{$small-only} {\n          @include button-group-style($radius: $button-med, $orientation: vertical);\n        }\n      }\n\n      @for $i from 2 through 8 {\n        &.even-#{$i} li {\n          @include button-group-style($even: $i, $float: null);\n        }\n      }\n    }\n\n    .button-bar {\n      @include clearfix;\n\n      .button-group {\n        @include button-group-container($styles: false, $float: true);\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-clearing-classes: $include-html-classes !default;\n\n// We use these to set the background colors for parts of Clearing.\n$clearing-bg: $oil !default;\n$clearing-caption-bg: $clearing-bg !default;\n$clearing-carousel-bg: rgba(51,51,51,0.8) !default;\n$clearing-img-bg: $clearing-bg !default;\n\n// We use these to style the close button\n$clearing-close-color: $iron !default;\n$clearing-close-size: 30px !default;\n\n// We use these to style the arrows\n$clearing-arrow-size: 12px !default;\n$clearing-arrow-color: $clearing-close-color !default;\n\n// We use these to style captions\n$clearing-caption-font-color: $iron !default;\n$clearing-caption-font-size: 0.875em !default;\n$clearing-caption-padding: 10px 30px 20px !default;\n\n// We use these to make the image and carousel height and style\n$clearing-active-img-height: 85% !default;\n$clearing-carousel-height: 120px !default;\n$clearing-carousel-thumb-width: 120px !default;\n$clearing-carousel-thumb-active-border: 1px solid rgb(255,255,255) !default;\n\n@include exports(\"clearing\") {\n  @if $include-html-clearing-classes {\n    // We decided to not create a mixin for Clearing because it relies\n    // on predefined classes and structure to work properly.\n    // The variables above should give enough control.\n\n    /* Clearing Styles */\n    .clearing-thumbs, #{data('clearing')} {\n      @include clearfix;\n      margin-bottom: 0;\n      margin-#{$default-float}: 0;\n      list-style: none;\n\n      li {\n        float: $default-float;\n        margin-#{$opposite-direction}: 10px;\n      }\n\n      &[class*=\"block-grid-\"] li {\n        margin-#{$opposite-direction}: 0;\n      }\n    }\n\n    .clearing-blackout {\n      background: $clearing-bg;\n      position: fixed;\n      width: 100%;\n      height: 100%;\n      top: 0;\n      #{$default-float}: 0;\n      z-index: 998;\n\n      .clearing-close { display: block; }\n    }\n\n    .clearing-container {\n      position: relative;\n      z-index: 998;\n      height: 100%;\n      overflow: hidden;\n      margin: 0;\n    }\n\n    .clearing-touch-label {\n      position: absolute;\n      top: 50%;\n      left: 50%;\n      color: $base;\n      font-size: 0.6em;\n    }\n\n    .visible-img {\n      height: 95%;\n      position: relative;\n\n      img {\n        position: absolute;\n        #{$default-float}: 50%;\n        top: 50%;\n        margin-#{$default-float}: -50%;\n        max-height: 100%;\n        max-width: 100%;\n      }\n    }\n\n    .clearing-caption {\n      color: $clearing-caption-font-color;\n      font-size: $clearing-caption-font-size;\n      line-height: 1.3;\n      margin-bottom: 0;\n      text-align: center;\n      bottom: 0;\n      background: $clearing-caption-bg;\n      width: 100%;\n      padding: $clearing-caption-padding;\n      position: absolute;\n      #{$default-float}: 0;\n    }\n\n    .clearing-close {\n      z-index: 999;\n      padding-#{$default-float}: 20px;\n      padding-top: 10px;\n      font-size: $clearing-close-size;\n      line-height: 1;\n      color: $clearing-close-color;\n      display: none;\n\n      &:hover,\n      &:focus { color: $iron; }\n    }\n\n    .clearing-assembled .clearing-container { height: 100%;\n      .carousel > ul { display: none; }\n    }\n\n    // If you want to show a lightbox, but only have a single image come through as the thumbnail\n    .clearing-feature li {\n      display: none;\n      &.clearing-featured-img {\n        display: block;\n      }\n    }\n\n    // Large screen overrides\n    @media #{$medium-up} {\n      .clearing-main-prev,\n      .clearing-main-next {\n        position: absolute;\n        height: 100%;\n        width: 40px;\n        top: 0;\n        & > span {\n          position: absolute;\n          top: 50%;\n          display: block;\n          width: 0;\n          height: 0;\n          border: solid $clearing-arrow-size;\n          &:hover { opacity: 0.8; }\n        }\n      }\n      .clearing-main-prev {\n        #{$default-float}: 0;\n        & > span {\n          #{$default-float}: 5px;\n          border-color: transparent;\n          border-#{$opposite-direction}-color: $clearing-arrow-color;\n        }\n      }\n      .clearing-main-next {\n        #{$opposite-direction}: 0;\n        & > span {\n          border-color: transparent;\n          border-#{$default-float}-color: $clearing-arrow-color;\n        }\n      }\n    \n      .clearing-main-prev.disabled,\n      .clearing-main-next.disabled { opacity: 0.3; }\n\n      .clearing-assembled .clearing-container {\n\n        .carousel {\n          background: $clearing-carousel-bg;\n          height: $clearing-carousel-height;\n          margin-top: 10px;\n          text-align: center;\n\n          & > ul {\n            display: inline-block;\n            z-index: 999;\n            height: 100%;\n            position: relative;\n            float: none;\n\n            li {\n              display: block;\n              width: $clearing-carousel-thumb-width;\n              min-height: inherit;\n              float: $default-float;\n              overflow: hidden;\n              margin-#{$opposite-direction}: 0;\n              padding: 0;\n              position: relative;\n              cursor: $cursor-pointer-value;\n              opacity: 0.4;\n              clear: none;\n\n              &.fix-height {\n                img {\n                  height: 100%;\n                  max-width: none;\n                }\n              }\n\n              a.th {\n                border: none;\n                box-shadow: none;\n                display: block;\n              }\n\n              img {\n              cursor: $cursor-pointer-value !important;\n              width: 100% !important;\n              }\n\n              &.visible { opacity: 1; }\n              &:hover { opacity: 0.8; }\n            }\n          }\n        }\n\n        .visible-img {\n          background: $clearing-img-bg;\n          overflow: hidden;\n          height: $clearing-active-img-height;\n        }\n      }\n\n      .clearing-close {\n        position: absolute;\n        top: 10px;\n        #{$opposite-direction}: 20px;\n        padding-#{$default-float}: 0;\n        padding-top: 0;\n      }\n    }\n\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-dropdown-classes: $include-html-classes !default;\n\n// We use these to controls height and width styles.\n$f-dropdown-max-width: 200px !default;\n$f-dropdown-height: auto !default;\n$f-dropdown-max-height: none !default;\n\n// Used for bottom position\n$f-dropdown-margin-top: 2px !default;\n\n// Used for right position\n$f-dropdown-margin-left: $f-dropdown-margin-top !default;\n\n// Used for left position\n$f-dropdown-margin-right: $f-dropdown-margin-top !default;\n\n// Used for top position\n$f-dropdown-margin-bottom: $f-dropdown-margin-top !default;\n\n// We use this to control the background color\n$f-dropdown-bg: $white !default;\n\n// We use this to set the border styles for dropdowns.\n$f-dropdown-border-style: solid !default;\n$f-dropdown-border-width: 1px !default;\n$f-dropdown-border-color: scale-color($white, $lightness: -20%) !default;\n\n// We use these to style the triangle pip.\n$f-dropdown-triangle-size: 6px !default;\n$f-dropdown-triangle-color: $white !default;\n$f-dropdown-triangle-side-offset: 10px !default;\n\n// We use these to control styles for the list elements.\n$f-dropdown-list-style: none !default;\n$f-dropdown-font-color: $charcoal !default;\n$f-dropdown-font-size: rem-calc(14) !default;\n$f-dropdown-list-padding: rem-calc(5, 10) !default;\n$f-dropdown-line-height: rem-calc(18) !default;\n$f-dropdown-list-hover-bg: $smoke !default;\n$dropdown-mobile-default-float: 0 !default;\n\n// We use this to control the styles for when the dropdown has custom content.\n$f-dropdown-content-padding: rem-calc(20) !default;\n\n// Default radius for dropdown.\n$f-dropdown-radius: $global-radius !default;\n\n//\n// @mixins\n//\n//\n// NOTE: Make default max-width change between list and content types. Can add more width with classes, maybe .small, .medium, .large, etc.;\n// We use this to style the dropdown container element.\n// $content-list - Sets list-style. Default: list. Options: [list, content]\n// $triangle - Sets if dropdown has triangle. Default:true.\n// $max-width - Default: $f-dropdown-max-width || 200px.\n@mixin dropdown-container($content:list, $triangle:true, $max-width:$f-dropdown-max-width) {\n  position: absolute;\n  left: -9999px;\n  list-style: $f-dropdown-list-style;\n  margin-#{$default-float}: 0;\n  outline: none;\n\n  > *:first-child { margin-top: 0; }\n  > *:last-child { margin-bottom: 0; }\n\n  @if $content == list {\n    width: 100%;\n    max-height: $f-dropdown-max-height;\n    height: $f-dropdown-height;\n    background: $f-dropdown-bg;\n    border: $f-dropdown-border-style $f-dropdown-border-width $f-dropdown-border-color;\n    font-size: $f-dropdown-font-size;\n    z-index: 89;\n  }\n  @else if $content == content {\n    padding: $f-dropdown-content-padding;\n    width: 100%;\n    height: $f-dropdown-height;\n    max-height: $f-dropdown-max-height;\n    background: $f-dropdown-bg;\n    border: $f-dropdown-border-style $f-dropdown-border-width $f-dropdown-border-color;\n    font-size: $f-dropdown-font-size;\n    z-index: 89;\n  }\n\n  @if $triangle == bottom {\n    margin-top: $f-dropdown-margin-top;\n\n    &:before {\n      @include css-triangle($f-dropdown-triangle-size, $f-dropdown-triangle-color, bottom);\n      position: absolute;\n      top: -($f-dropdown-triangle-size * 2);\n      #{$default-float}: $f-dropdown-triangle-side-offset;\n      z-index: 89;\n    }\n    &:after {\n      @include css-triangle($f-dropdown-triangle-size + 1, $f-dropdown-border-color, bottom);\n      position: absolute;\n      top: -(($f-dropdown-triangle-size + 1) * 2);\n      #{$default-float}: $f-dropdown-triangle-side-offset - 1;\n      z-index: 88;\n    }\n\n    &.right:before {\n      #{$default-float}: auto;\n      #{$opposite-direction}: $f-dropdown-triangle-side-offset;\n    }\n    &.right:after {\n      #{$default-float}: auto;\n      #{$opposite-direction}: $f-dropdown-triangle-side-offset - 1;\n    }\n  }\n\n  @if $triangle == $default-float {\n    margin-top: 0;\n    margin-#{$default-float}: $f-dropdown-margin-right;\n\n    &:before {\n      @include css-triangle($f-dropdown-triangle-size, $f-dropdown-triangle-color, #{$opposite-direction});\n      position: absolute;\n      top: $f-dropdown-triangle-side-offset;\n      #{$default-float}: -($f-dropdown-triangle-size * 2);\n      z-index: 89;\n    }\n    &:after {\n      @include css-triangle($f-dropdown-triangle-size + 1, $f-dropdown-border-color, #{$opposite-direction});\n      position: absolute;\n      top: $f-dropdown-triangle-side-offset - 1;\n      #{$default-float}: -($f-dropdown-triangle-size * 2) - 2;\n      z-index: 88;\n    }\n\n  }\n\n  @if $triangle == $opposite-direction {\n    margin-top: 0;\n    margin-#{$default-float}: -$f-dropdown-margin-right;\n\n    &:before {\n      @include css-triangle($f-dropdown-triangle-size, $f-dropdown-triangle-color, #{$default-float});\n      position: absolute;\n      top: $f-dropdown-triangle-side-offset;\n      #{$opposite-direction}: -($f-dropdown-triangle-size * 2);\n      #{$default-float}: auto;\n      z-index: 89;\n    }\n    &:after {\n      @include css-triangle($f-dropdown-triangle-size + 1, $f-dropdown-border-color, #{$default-float});\n      position: absolute;\n      top: $f-dropdown-triangle-side-offset - 1;\n      #{$opposite-direction}: -($f-dropdown-triangle-size * 2) - 2;\n      #{$default-float}: auto;\n      z-index: 88;\n    }\n\n  }\n\n  @if $triangle == top {\n    margin-top: -$f-dropdown-margin-bottom;\n    margin-left: 0;\n\n    &:before {\n      @include css-triangle($f-dropdown-triangle-size, $f-dropdown-triangle-color, top);\n      position: absolute;\n      top: auto;\n      bottom: -($f-dropdown-triangle-size * 2);\n      #{$default-float}: $f-dropdown-triangle-side-offset;\n      #{$opposite-direction}: auto;\n      z-index: 89;\n    }\n    &:after {\n      @include css-triangle($f-dropdown-triangle-size + 1, $f-dropdown-border-color, top);\n      position: absolute;\n      top: auto;\n      bottom: -($f-dropdown-triangle-size * 2) - 2;\n      #{$default-float}: $f-dropdown-triangle-side-offset - 1;\n      #{$opposite-direction}: auto;\n      z-index: 88;\n    }\n\n  }\n\n  @if $max-width { max-width: $max-width; }\n  @else { max-width: $f-dropdown-max-width; }\n\n}\n\n// @MIXIN\n//\n// We use this to style the list elements or content inside the dropdown.\n\n@mixin dropdown-style {\n  font-size: $f-dropdown-font-size;\n  cursor: $cursor-pointer-value;\n\n  line-height: $f-dropdown-line-height;\n  margin: 0;\n\n  &:hover,\n  &:focus { background: $f-dropdown-list-hover-bg; }\n\n  &.radius { @include radius($f-dropdown-radius); }\n\n  a {\n    display: block;\n    padding: $f-dropdown-list-padding;\n    color: $f-dropdown-font-color;\n  }\n}\n\n@include exports(\"dropdown\") {\n  @if $include-html-dropdown-classes {\n\n    /* Foundation Dropdowns */\n    .f-dropdown {\n      @include dropdown-container(list, bottom);\n\n      &.drop-#{$opposite-direction} {\n        @include dropdown-container(list, #{$default-float});\n      }\n\n      &.drop-#{$default-float} {\n        @include dropdown-container(list, #{$opposite-direction});\n      }\n\n      &.drop-top {\n        @include dropdown-container(list, top);\n      }\n      // max-width: none;\n\n      li { @include dropdown-style; }\n\n      // You can also put custom content in these dropdowns\n      &.content { @include dropdown-container(content, $triangle:false); }\n\n      // Sizes\n      &.tiny    { max-width: 200px; }\n      &.small   { max-width: 300px; }\n      &.medium  { max-width: 500px; }\n      &.large   { max-width: 800px; }\n      &.mega    {\n        width:100%!important;\n        max-width:100%!important;\n\n        &.open{\n          left:0!important;\n        }\n      }\n    }\n\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-button-classes: $include-html-classes !default;\n\n// We use these to set the color of the pip in dropdown buttons\n$dropdown-button-pip-color: $white !default;\n$dropdown-button-pip-color-alt: $oil !default;\n\n$button-pip-tny: rem-calc(6) !default;\n$button-pip-sml: rem-calc(7) !default;\n$button-pip-med: rem-calc(9) !default;\n$button-pip-lrg: rem-calc(11) !default;\n\n// We use these to style tiny dropdown buttons\n$dropdown-button-padding-tny: $button-pip-tny * 7 !default;\n$dropdown-button-pip-size-tny: $button-pip-tny !default;\n$dropdown-button-pip-opposite-tny: $button-pip-tny * 3 !default;\n$dropdown-button-pip-top-tny: calc(-1 * $button-pip-tny / 2) + rem-calc(1) !default;\n\n// We use these to style small dropdown buttons\n$dropdown-button-padding-sml: $button-pip-sml * 7 !default;\n$dropdown-button-pip-size-sml: $button-pip-sml !default;\n$dropdown-button-pip-opposite-sml: $button-pip-sml * 3 !default;\n$dropdown-button-pip-top-sml: calc(-1 * $button-pip-sml / 2) + rem-calc(1) !default;\n\n// We use these to style medium dropdown buttons\n$dropdown-button-padding-med: $button-pip-med * 6 + rem-calc(3) !default;\n$dropdown-button-pip-size-med: $button-pip-med - rem-calc(3) !default;\n$dropdown-button-pip-opposite-med: $button-pip-med * 2.5 !default;\n$dropdown-button-pip-top-med: calc(-1 * $button-pip-med / 2) + rem-calc(2) !default;\n\n// We use these to style large dropdown buttons\n$dropdown-button-padding-lrg: $button-pip-lrg * 5 + rem-calc(3) !default;\n$dropdown-button-pip-size-lrg: $button-pip-lrg - rem-calc(6) !default;\n$dropdown-button-pip-opposite-lrg: $button-pip-lrg * 2.5 !default;\n$dropdown-button-pip-top-lrg: calc(-1 * $button-pip-lrg / 2) + rem-calc(3) !default;\n\n// @mixins\n//\n// Dropdown Button Mixin\n//\n// We use this mixin to build off of the button mixin and add dropdown button styles\n//\n// $padding - Determines the size of button you're working with. Default: medium. Options [tiny, small, medium, large]\n// $pip-color - Color of the little triangle that points to the dropdown. Default: $white.\n// $base-style - Add in base-styles. This can be set to false. Default:true\n\n@mixin dropdown-button($padding: medium, $pip-color: $white, $base-style: true) {\n\n  // We add in base styles, but they can be negated by setting to 'false'.\n  @if $base-style {\n    position: relative;\n    outline: none;\n\n    // This creates the base styles for the triangle pip\n    &::after {\n      position: absolute;\n      content: \"\";\n      width: 0;\n      height: 0;\n      display: block;\n      border-style: solid;\n      border-color: $dropdown-button-pip-color transparent transparent transparent;\n      top: 50%;\n    }\n  }\n\n  // If we're dealing with tiny buttons, use these styles\n  @if $padding ==tiny {\n    padding-#{$opposite-direction}: $dropdown-button-padding-tny;\n\n    &:after {\n      border-width: $dropdown-button-pip-size-tny;\n      #{$opposite-direction}: $dropdown-button-pip-opposite-tny;\n      margin-top: $dropdown-button-pip-top-tny;\n    }\n  }\n\n  // If we're dealing with small buttons, use these styles\n  @if $padding ==small {\n    padding-#{$opposite-direction}: $dropdown-button-padding-sml;\n\n    &::after {\n      border-width: $dropdown-button-pip-size-sml;\n      #{$opposite-direction}: $dropdown-button-pip-opposite-sml;\n      margin-top: $dropdown-button-pip-top-sml;\n    }\n  }\n\n  // If we're dealing with default (medium) buttons, use these styles\n  @if $padding ==medium {\n    padding-#{$opposite-direction}: $dropdown-button-padding-med;\n\n    &::after {\n      border-width: $dropdown-button-pip-size-med;\n      #{$opposite-direction}: $dropdown-button-pip-opposite-med;\n      margin-top: $dropdown-button-pip-top-med;\n    }\n  }\n\n  // If we're dealing with large buttons, use these styles\n  @if $padding ==large {\n    padding-#{$opposite-direction}: $dropdown-button-padding-lrg;\n\n    &::after {\n      border-width: $dropdown-button-pip-size-lrg;\n      #{$opposite-direction}: $dropdown-button-pip-opposite-lrg;\n      margin-top: $dropdown-button-pip-top-lrg;\n    }\n  }\n\n  // We can control the pip color. We didn't use logic in this case, just set it and forget it.\n  @if $pip-color {\n    &::after {\n      border-color: $pip-color transparent transparent transparent;\n    }\n  }\n}\n\n@include exports(\"dropdown-button\") {\n  @if $include-html-button-classes {\n\n    .dropdown.button,\n    button.dropdown {\n      @include dropdown-button;\n\n      &.tiny {\n        @include dropdown-button(tiny, $base-style: false);\n      }\n\n      &.small {\n        @include dropdown-button(small, $base-style: false);\n      }\n\n      &.large {\n        @include dropdown-button(large, $base-style: false);\n      }\n\n      &.secondary:after {\n        border-color: $dropdown-button-pip-color-alt transparent transparent transparent;\n      }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-media-classes: $include-html-classes !default;\n\n// We use these to control video container padding and margins\n$flex-video-padding-top: rem-calc(25) !default;\n$flex-video-padding-bottom: 67.5% !default;\n$flex-video-margin-bottom: rem-calc(16) !default;\n\n// We use this to control widescreen bottom padding\n$flex-video-widescreen-padding-bottom: 56.34% !default;\n\n//\n// @mixins\n//\n\n@mixin flex-video-container {\n  position: relative;\n  padding-top: $flex-video-padding-top;\n  padding-bottom: $flex-video-padding-bottom;\n  height: 0;\n  margin-bottom: $flex-video-margin-bottom;\n  overflow: hidden;\n\n  &.widescreen { padding-bottom: $flex-video-widescreen-padding-bottom; }\n  &.vimeo { padding-top: 0; }\n\n  iframe,\n  object,\n  embed,\n  video {\n    position: absolute;\n    top: 0;\n    #{$default-float}: 0;\n    width: 100%;\n    height: 100%;\n  }\n}\n\n@include exports(\"flex-video\") {\n  @if $include-html-media-classes {\n    .flex-video { @include flex-video-container; }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-inline-list-classes: $include-html-classes !default;\n\n// We use this to control the margins and padding of the inline list.\n$inline-list-top-margin: 0 !default;\n$inline-list-opposite-margin: 0 !default;\n$inline-list-bottom-margin: rem-calc(17) !default;\n$inline-list-default-float-margin: rem-calc(-22) !default;\n$inline-list-default-float-list-margin: rem-calc(22) !default;\n\n$inline-list-padding: 0 !default;\n\n// We use this to control the overflow of the inline list.\n$inline-list-overflow: hidden !default;\n\n// We use this to control the list items\n$inline-list-display: block !default;\n\n// We use this to control any elements within list items\n$inline-list-children-display: block !default;\n\n//\n// @mixins\n//\n// We use this mixin to create inline lists\n@mixin inline-list {\n  margin: $inline-list-top-margin auto $inline-list-bottom-margin auto;\n  margin-#{$default-float}: $inline-list-default-float-margin;\n  margin-#{$opposite-direction}: $inline-list-opposite-margin;\n  padding: $inline-list-padding;\n  list-style: none;\n  overflow: $inline-list-overflow;\n\n  & > li {\n    list-style: none;\n    float: $default-float;\n    margin-#{$default-float}: $inline-list-default-float-list-margin;\n    display: $inline-list-display;\n    &>* { display: $inline-list-children-display; }\n  }\n}\n\n@include exports(\"inline-list\") {\n  @if $include-html-inline-list-classes {\n    .inline-list {\n      @include inline-list();\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-keystroke-classes: $include-html-classes !default;\n\n// We use these to control text styles.\n$keystroke-font: \"Consolas\", \"Menlo\", \"Courier\", monospace !default;\n$keystroke-font-size: inherit !default;\n$keystroke-font-color: $jet !default;\n$keystroke-font-color-alt: $white !default;\n$keystroke-function-factor: -7% !default;\n\n// We use this to control keystroke padding.\n$keystroke-padding: rem-calc(2 4 0) !default;\n\n// We use these to control background and border styles.\n$keystroke-bg: scale-color($white, $lightness: $keystroke-function-factor) !default;\n$keystroke-border-style: solid !default;\n$keystroke-border-width: 1px !default;\n$keystroke-border-color: scale-color($keystroke-bg, $lightness: $keystroke-function-factor) !default;\n$keystroke-radius: $global-radius !default;\n\n//\n// @mixins\n//\n// We use this mixin to create keystroke styles.\n// $bg - Default: $keystroke-bg || scale-color($white, $lightness: $keystroke-function-factor) !default;\n@mixin keystroke($bg:$keystroke-bg) {\n  // This find the lightness percentage of the background color.\n  $bg-lightness: lightness($bg);\n\n  background-color: $bg;\n  border-color: scale-color($bg, $lightness: $keystroke-function-factor);\n\n  // We adjust the font color based on the brightness of the background.\n  @if $bg-lightness > 70% { color: $keystroke-font-color; }\n  @else { color: $keystroke-font-color-alt; }\n\n  border-style: $keystroke-border-style;\n  border-width: $keystroke-border-width;\n  margin: 0;\n  font-family: $keystroke-font;\n  font-size: $keystroke-font-size;\n  padding: $keystroke-padding;\n}\n\n@include exports(\"keystroke\") {\n  @if $include-html-keystroke-classes  {\n    .keystroke,\n    kbd {\n      @include keystroke;\n      @include radius($keystroke-radius);\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n$include-html-panel-classes: $include-html-classes !default;\n\n// We use these to control the background and border styles\n$panel-bg: scale-color($white, $lightness: -5%) !default;\n$panel-border-style: solid !default;\n$panel-border-size: 1px !default;\n\n// We use this % to control how much we darken things on hover\n$panel-function-factor: -11% !default;\n$panel-border-color: scale-color($panel-bg, $lightness: $panel-function-factor) !default;\n\n// We use these to set default inner padding and bottom margin\n$panel-margin-bottom: rem-calc(20) !default;\n$panel-padding: rem-calc(20) !default;\n\n// We use these to set default font colors\n$panel-font-color: $oil !default;\n$panel-font-color-alt: $white !default;\n\n$panel-header-adjust: true !default;\n$callout-panel-link-color: $primary-color !default;\n$callout-panel-link-color-hover: scale-color($callout-panel-link-color, $lightness: -14%) !default;\n\n//\n// @mixins\n//\n// We use this mixin to create panels.\n// $bg - Sets the panel background color. Default: $panel-pg || scale-color($white, $lightness: -5%) !default\n// $padding - Sets the panel padding amount. Default: $panel-padding || rem-calc(20)\n// $adjust - Sets the font color based on the darkness of the bg & resets header line-heights for panels. Default: $panel-header-adjust || true\n@mixin panel($bg: $panel-bg, $padding: $panel-padding, $adjust: $panel-header-adjust) {\n\n  @if $bg {\n    $bg-lightness: lightness($bg);\n\n    border-style: $panel-border-style;\n    border-width: $panel-border-size;\n    border-color: scale-color($bg, $lightness: $panel-function-factor);\n    margin-bottom: $panel-margin-bottom;\n    padding: $padding;\n\n    background: $bg;\n\n    @if $bg-lightness >=50% {\n      color: $panel-font-color;\n    }\n\n    @else {\n      color: $panel-font-color-alt;\n    }\n\n    // Respect the padding, fool.\n    &>:first-child {\n      margin-top: 0;\n    }\n\n    &>:last-child {\n      margin-bottom: 0;\n    }\n\n    @if $adjust {\n\n      // We set the font color based on the darkness of the bg.\n      @if $bg-lightness >=50% {\n\n        h1,\n        h2,\n        h3,\n        h4,\n        h5,\n        h6,\n        p,\n        li,\n        dl {\n          color: $panel-font-color;\n        }\n      }\n\n      @else {\n\n        h1,\n        h2,\n        h3,\n        h4,\n        h5,\n        h6,\n        p,\n        li,\n        dl {\n          color: $panel-font-color-alt;\n        }\n      }\n\n      // reset header line-heights for panels\n      h1,\n      h2,\n      h3,\n      h4,\n      h5,\n      h6 {\n        line-height: 1;\n        margin-bottom: calc(rem-calc(20) / 2);\n\n        &.subheader {\n          line-height: 1.4;\n        }\n      }\n    }\n  }\n}\n\n@include exports(\"panel\") {\n  @if $include-html-panel-classes {\n\n    /* Panels */\n    .panel {\n      @include panel;\n\n      &.callout {\n        @include panel(scale-color($primary-color, $lightness: 94%));\n\n        a:not(.button) {\n          color: $callout-panel-link-color;\n\n          &:hover,\n          &:focus {\n            color: $callout-panel-link-color-hover;\n          }\n        }\n      }\n\n      &.radius {\n        @include radius;\n      }\n\n    }\n\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n@import \"grid\";\n\n//\n// @name _reveal.scss\n// @dependencies _global.scss\n//\n\n$include-html-reveal-classes: $include-html-classes !default;\n\n// We use these to control the style of the reveal overlay.\n$reveal-overlay-bg: rgba($black, .45) !default;\n$reveal-overlay-bg-old: $black !default;\n\n// We use these to control the style of the modal itself.\n$reveal-modal-bg: $white !default;\n$reveal-position-top: rem-calc(250) !default;\n$reveal-default-width: 80% !default;\n$reveal-max-width: $row-width !default;\n$reveal-modal-padding: rem-calc(20) !default;\n$reveal-box-shadow: 0 0 10px rgba($black,.4) !default;\n\n// We use these to style the reveal close button\n$reveal-close-font-size: rem-calc(40) !default;\n$reveal-close-top: rem-calc(10) !default;\n$reveal-close-side: rem-calc(22) !default;\n$reveal-close-color: $base !default;\n$reveal-close-weight: $font-weight-bold !default;\n\n// We use this to set the default radius used throughout the core.\n$reveal-radius: $global-radius !default;\n$reveal-round: $global-rounded !default;\n\n// We use these to control the modal border\n$reveal-border-style: solid !default;\n$reveal-border-width: 1px !default;\n$reveal-border-color: $steel !default;\n\n$reveal-modal-class: \"reveal-modal\" !default;\n$close-reveal-modal-class: \"close-reveal-modal\" !default;\n\n//\n// @mixins\n//\n\n// We use this to create the reveal background overlay styles\n@mixin reveal-bg( $include-z-index-value: true ) {\n  //position: fixed;\n  position: absolute; // allows modal background to extend beyond window position\n  top: 0;\n  bottom: 0;\n  left: 0;\n  right: 0;\n  background: $reveal-overlay-bg-old; // Autoprefixer should be used to avoid such variables needed when Foundation for Sites can do so in the near future.\n  background: $reveal-overlay-bg;\n  z-index: if( $include-z-index-value, 1004, auto );\n  display: none;\n  #{$default-float}: 0;\n}\n\n// We use this mixin to create the structure of a reveal modal\n//\n// $base-style - Provides reveal base styles, can be set to false to override. Default: true, Options: false\n// $width - Sets reveal width Default: $reveal-default-width || 80%\n//\n@mixin reveal-modal-base( $base-style: true, $width:$reveal-default-width, $max-width:$reveal-max-width, $border-radius: $reveal-radius) {\n  @if $base-style {\n    visibility: hidden;\n    display: none;\n    position: absolute;\n    z-index: 1005;\n    width: 100vw;\n    top:0;\n    border-radius: $border-radius;\n    #{$default-float}: 0;\n\n    @media #{$small-only} {\n      min-height:100vh;\n    }\n\n    // Make sure rows don't have a min-width on them\n    .column, .columns { min-width: 0; }\n\n    // Get rid of margin from first and last element inside modal\n    & > :first-child { margin-top: 0; }\n\n    & > :last-child { margin-bottom: 0; }\n  }\n\n  @if $width {\n    @media #{$medium-up} {\n      width: $width;\n      max-width: $max-width;\n      left: 0;\n      right: 0;\n      margin: 0 auto;\n    }\n  }\n}\n\n// We use this to style the reveal modal defaults\n//\n// $bg - Sets background color of reveal modal. Default: $reveal-modal-bg || $white\n// $padding - Padding to apply to reveal modal. Default: $reveal-modal-padding.\n// $border - Choose whether reveal uses a border. Default: true, Options: false\n// $border-style - Set reveal border style. Default: $reveal-border-style || solid\n// $border-width - Width of border (i.e. 1px). Default: $reveal-border-width.\n// $border-color - Color of border. Default: $reveal-border-color.\n// $box-shadow - Choose whether or not to include the default box-shadow. Default: true, Options: false\n// $radius - If true, set to modal radius which is $global-radius || explicitly set radius amount in px (ex. $radius:10px). Default: false\n// $top-offset - Default: $reveal-position-top || 50px\n@mixin reveal-modal-style(\n  $bg:false,\n  $padding:false,\n  $border:false,\n  $border-style:$reveal-border-style,\n  $border-width:$reveal-border-width,\n  $border-color:$reveal-border-color,\n  $box-shadow:false,\n  $radius:false,\n  $top-offset:false) {\n\n  @if $bg { background-color: $bg; }\n  @if $padding != false { padding: $padding; }\n\n  @if $border { border: $border-style $border-width $border-color; }\n\n  // We can choose whether or not to include the default box-shadow.\n  @if $box-shadow {\n    box-shadow: $reveal-box-shadow;\n  }\n\n  // We can control how much radius is used on the modal\n  @if $radius == true { @include radius($reveal-radius); }\n  @else if $radius { @include radius($radius); }\n\n  @if $top-offset {\n    @media #{$medium-up} {\n      top: $top-offset;\n    }\n  }\n}\n\n// We use this to create a close button for the reveal modal\n//\n// $color - Default: $reveal-close-color || $base\n@mixin reveal-close($color:$reveal-close-color) {\n  font-size: $reveal-close-font-size;\n  line-height: 1;\n  position: absolute;\n  top: $reveal-close-top;\n  #{$opposite-direction}: $reveal-close-side;\n  color: $color;\n  font-weight: $reveal-close-weight;\n  cursor: $cursor-pointer-value;\n}\n\n@include exports(\"reveal\") {\n  @if $include-html-reveal-classes {\n\n    // Reveal Modals\n    .reveal-modal-bg { @include reveal-bg; }\n\n    .#{$reveal-modal-class} {\n      @include reveal-modal-base;\n      @include reveal-modal-style(\n        $bg:$reveal-modal-bg,\n        $padding:$reveal-modal-padding,\n        $border:true,\n        $box-shadow:true,\n        $radius:false,\n        $top-offset:$reveal-position-top\n      );\n      @include reveal-modal-style($padding:$reveal-modal-padding * 1.5);\n\n      &.radius { @include reveal-modal-style($radius:true); }\n      &.round  { @include reveal-modal-style($radius:$reveal-round); }\n      &.collapse { @include reveal-modal-style($padding:0); }\n      &.tiny  { @include reveal-modal-base(false, 30%); }\n      &.small { @include reveal-modal-base(false, 40%); }\n      &.medium  { @include reveal-modal-base(false, 60%); }\n      &.large { @include reveal-modal-base(false, 70%); }\n      &.xlarge { @include reveal-modal-base(false, 95%); }\n      &.full {\n        @include reveal-modal-base(false, 100vw);\n        top:0;\n        left:0;\n        height:100%;\n        height: 100vh;\n        min-height:100vh;\n        max-width: none !important;\n        margin-left: 0 !important;\n      }\n\n      .#{$close-reveal-modal-class} { @include reveal-close; }\n    }\n\n    dialog {\n      @extend .#{$reveal-modal-class};\n      display: none;\n\n      &::backdrop, & + .backdrop {\n        @include reveal-bg(false);\n      }\n\n      &[open]{\n        display: block;\n      }\n    }\n\n    // Reveal Print Styles: It should be invisible, adds no value being printed.\n    @media print {\n      dialog, .#{$reveal-modal-class} { \n        display: none;\n        background: $white !important;\n      }\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @variables\n//\n\n$include-html-nav-classes: $include-html-classes !default;\n\n// We use this to control padding.\n$side-nav-padding: rem-calc(14 0) !default;\n\n// We use these to control list styles.\n$side-nav-list-type: none !default;\n$side-nav-list-position: outside !default;\n$side-nav-list-margin: rem-calc(0 0 7 0) !default;\n\n// We use these to control link styles.\n$side-nav-link-color: $primary-color !default;\n$side-nav-link-color-active: scale-color($side-nav-link-color, $lightness: 30%) !default;\n$side-nav-link-color-hover: scale-color($side-nav-link-color, $lightness: 30%) !default;\n$side-nav-link-bg-hover: hsla(0deg, 0%, 0%, 0.025) !default;\n$side-nav-link-margin: 0 !default;\n$side-nav-link-padding: rem-calc(7 14) !default;\n$side-nav-font-size: rem-calc(14) !default;\n$side-nav-font-weight: $font-weight-normal !default;\n$side-nav-font-weight-active: $side-nav-font-weight !default;\n$side-nav-font-family: $body-font-family !default;\n$side-nav-font-family-active: $side-nav-font-family !default;\n\n// We use these to control heading styles.\n$side-nav-heading-color: $side-nav-link-color !default;\n$side-nav-heading-font-size: $side-nav-font-size !default;\n$side-nav-heading-font-weight: bold !default;\n$side-nav-heading-text-transform: uppercase !default;\n\n// We use these to control border styles\n$side-nav-divider-size: 1px !default;\n$side-nav-divider-style: solid !default;\n$side-nav-divider-color: scale-color($white, $lightness: 10%) !default;\n\n\n//\n// @mixins\n//\n\n\n// We use this to style the side-nav\n//\n// $divider-color - Border color of divider. Default: $side-nav-divider-color.\n// $font-size - Font size of nav items. Default: $side-nav-font-size.\n// $link-color - Color of navigation links. Default: $side-nav-link-color.\n// $link-color-hover - Color of navigation links when hovered. Default: $side-nav-link-color-hover.\n@mixin side-nav($divider-color: $side-nav-divider-color,\n  $font-size: $side-nav-font-size,\n  $link-color: $side-nav-link-color,\n  $link-color-hover: $side-nav-link-color-hover,\n  $link-bg-hover: $side-nav-link-bg-hover) {\n  display: block;\n  margin: 0;\n  padding: $side-nav-padding;\n  list-style-type: $side-nav-list-type;\n  list-style-position: $side-nav-list-position;\n  font-family: $side-nav-font-family;\n\n  li {\n    margin: $side-nav-list-margin;\n    font-size: $font-size;\n    font-weight: $side-nav-font-weight;\n\n    a:not(.button) {\n      display: block;\n      color: $link-color;\n      margin: $side-nav-link-margin;\n      padding: $side-nav-link-padding;\n\n      &:hover,\n      &:focus {\n        background: $link-bg-hover;\n        color: $link-color-hover;\n      }\n    }\n\n    &.active>a:first-child:not(.button) {\n      color: $side-nav-link-color-active;\n      font-weight: $side-nav-font-weight-active;\n      font-family: $side-nav-font-family-active;\n    }\n\n    &.divider {\n      border-top: $side-nav-divider-size $side-nav-divider-style;\n      height: 0;\n      padding: 0;\n      list-style: none;\n      border-top-color: $divider-color;\n    }\n\n    &.heading {\n      color: $side-nav-heading-color;\n\n      font: {\n        size: $side-nav-heading-font-size;\n        weight: $side-nav-heading-font-weight;\n      }\n\n      text-transform: $side-nav-heading-text-transform;\n    }\n  }\n}\n\n@include exports(\"side-nav\") {\n  @if $include-html-nav-classes {\n    .side-nav {\n      @include side-nav;\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @name _sub-nav.scss\n// @dependencies _global.scss\n//\n\n//\n// @variables\n//\n\n$include-html-nav-classes: $include-html-classes !default;\n\n// We use these to control margin and padding\n$sub-nav-list-margin: rem-calc(-4 0 18) !default;\n$sub-nav-list-padding-top: rem-calc(4) !default;\n\n// We use this to control the definition\n$sub-nav-font-family: $body-font-family !default;\n$sub-nav-font-size: rem-calc(14) !default;\n$sub-nav-font-color: $aluminum !default;\n$sub-nav-font-weight: $font-weight-normal !default;\n$sub-nav-text-decoration: none !default;\n$sub-nav-padding: rem-calc(3 16) !default;\n$sub-nav-border-radius: 3px !default;\n$sub-nav-font-color-hover: scale-color($sub-nav-font-color, $lightness: -25%) !default;\n\n\n// We use these to control the active item styles\n\n$sub-nav-active-font-weight: $font-weight-normal !default;\n$sub-nav-active-bg: $primary-color !default;\n$sub-nav-active-bg-hover: scale-color($sub-nav-active-bg, $lightness: -14%) !default;\n$sub-nav-active-color: $white !default;\n$sub-nav-active-padding: $sub-nav-padding !default;\n$sub-nav-active-cursor: default !default;\n\n$sub-nav-item-divider: \"\" !default;\n$sub-nav-item-divider-margin: rem-calc(12) !default;\n\n//\n// @mixins\n//\n\n\n// Create a sub-nav item\n//\n// $font-color - Font color. Default: $sub-nav-font-color.\n// $font-size - Font size. Default: $sub-nav-font-size.\n// $active-bg - Background of active nav item. Default: $sub-nav-active-bg.\n// $active-bg-hover - Background of active nav item, when hovered. Default: $sub-nav-active-bg-hover.\n@mixin sub-nav(\n  $font-color: $sub-nav-font-color,\n  $font-size: $sub-nav-font-size,\n  $active-bg: $sub-nav-active-bg,\n  $active-bg-hover: $sub-nav-active-bg-hover) {\n  display: block;\n  width: auto;\n  overflow: hidden;\n  margin: $sub-nav-list-margin;\n  padding-top: $sub-nav-list-padding-top;\n\n  dt {\n    text-transform: uppercase;\n  }\n\n  dt,\n  dd,\n  li {\n    float: $default-float;\n    display: inline;\n    margin-#{$default-float}: rem-calc(16);\n    margin-bottom: 0;\n    font-family: $sub-nav-font-family;\n    font-weight: $sub-nav-font-weight;\n    font-size: $font-size;\n    color: $font-color;\n\n    a {\n      text-decoration: $sub-nav-text-decoration;\n      color: $sub-nav-font-color;\n      padding: $sub-nav-padding;\n      &:hover {\n        color: $sub-nav-font-color-hover;\n      }\n    }\n\n    &.active a {\n      @include radius($sub-nav-border-radius);\n      font-weight: $sub-nav-active-font-weight;\n      background: $active-bg;\n      padding: $sub-nav-active-padding;\n      cursor: $sub-nav-active-cursor;\n      color: $sub-nav-active-color;\n      &:hover {\n        background: $active-bg-hover;\n      }\n    }\n    @if $sub-nav-item-divider != \"\" {\n      margin-#{$default-float}: 0;\n\n      &:before {\n        content: \"#{$sub-nav-item-divider}\";\n        margin: 0 $sub-nav-item-divider-margin;\n      }\n\n      &:first-child:before {\n        content: \"\";\n        margin: 0;\n      }\n    }\n  }\n}\n\n@include exports(\"sub-nav\") {\n  @if $include-html-nav-classes {\n    .sub-nav { @include sub-nav; }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @name _tables.scss\n// @dependencies _global.scss\n//\n\n//\n// @variables\n//\n\n$include-html-table-classes: $include-html-classes !default;\n\n// These control the background color for the table and even rows\n$table-bg: $white !default;\n$table-even-row-bg: $snow !default;\n\n// These control the table cell border style\n$table-border-style: solid !default;\n$table-border-size: 1px !default;\n$table-border-color: $gainsboro !default;\n\n// These control the table head styles\n$table-head-bg: $white-smoke !default;\n$table-head-font-size: rem-calc(14) !default;\n$table-head-font-color: $jet !default;\n$table-head-font-weight: $font-weight-bold !default;\n$table-head-padding: rem-calc(8 10 10) !default;\n\n// These control the table foot styles\n$table-foot-bg: $table-head-bg !default;\n$table-foot-font-size: $table-head-font-size !default;\n$table-foot-font-color: $table-head-font-color !default;\n$table-foot-font-weight: $table-head-font-weight !default;\n$table-foot-padding: $table-head-padding !default;\n\n// These control the caption\n$table-caption-bg: transparent !default;\n$table-caption-font-color: $table-head-font-color !default;\n$table-caption-font-size: rem-calc(16) !default;\n$table-caption-font-weight: bold !default;\n\n// These control the row padding and font styles\n$table-row-padding: rem-calc(9 10) !default;\n$table-row-font-size: rem-calc(14) !default;\n$table-row-font-color: $jet !default;\n$table-line-height: rem-calc(18) !default;\n\n// These are for controlling the layout, display and margin of tables\n$table-layout: auto !default;\n$table-display: table-cell !default;\n$table-margin-bottom: rem-calc(20) !default;\n\n\n//\n// @mixins\n//\n\n@mixin table {\n  background: $table-bg;\n  margin-bottom: $table-margin-bottom;\n  border: $table-border-style $table-border-size $table-border-color;\n  table-layout: $table-layout;\n\n  caption {\n    background: $table-caption-bg;\n    color: $table-caption-font-color;\n    font: {\n      size: $table-caption-font-size;\n      weight: $table-caption-font-weight;\n    }\n  }\n\n  thead {\n    background: $table-head-bg;\n\n    tr {\n      th,\n      td {\n        padding: $table-head-padding;\n        font-size: $table-head-font-size;\n        font-weight: $table-head-font-weight;\n        color: $table-head-font-color;\n      }\n    }\n  }\n\n  tfoot {\n    background: $table-foot-bg;\n\n    tr {\n      th,\n      td {\n        padding: $table-foot-padding;\n        font-size: $table-foot-font-size;\n        font-weight: $table-foot-font-weight;\n        color: $table-foot-font-color;\n      }\n    }\n  }\n\n  tr {\n    th,\n    td {\n      padding: $table-row-padding;\n      font-size: $table-row-font-size;\n      color: $table-row-font-color;\n      text-align: $default-float;\n    }\n\n    &.even,\n    &.alt,\n    &:nth-of-type(even) { background: $table-even-row-bg; }\n  }\n\n  thead tr th,\n  tfoot tr th,\n  tfoot tr td,\n  tbody tr th,\n  tbody tr td,\n  tr td { display: $table-display; line-height: $table-line-height; }\n}\n\n\n@include exports(\"table\") {\n  @if $include-html-table-classes {\n    table {\n      @include table;\n    }\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// @name _thumbs.scss\n// @dependencies _globals.scss\n//\n\n//\n// @variables\n//\n\n$include-html-media-classes: $include-html-classes !default;\n\n// We use these to control border styles\n$thumb-border-style: solid !default;\n$thumb-border-width: 4px !default;\n$thumb-border-color: $white !default;\n$thumb-box-shadow: 0 0 0 1px rgba($black,.2) !default;\n$thumb-box-shadow-hover: 0 0 6px 1px rgba($primary-color,0.5) !default;\n\n// Radius and transition speed for thumbs\n$thumb-radius: $global-radius !default;\n$thumb-transition-speed: 200ms !default;\n\n//\n// @mixins\n//\n\n// We use this to create image thumbnail styles.\n//\n// $border-width - Width of border around thumbnail. Default: $thumb-border-width.\n// $box-shadow - Box shadow to apply to thumbnail. Default: $thumb-box-shadow.\n// $box-shadow-hover - Box shadow to apply on hover. Default: $thumb-box-shadow-hover.\n@mixin thumb(\n  $border-width:$thumb-border-width, \n  $box-shadow:$thumb-box-shadow, \n  $box-shadow-hover:$thumb-box-shadow-hover) {\n  line-height: 0;\n  display: inline-block;\n  border: $thumb-border-style $border-width $thumb-border-color;\n  max-width: 100%;\n  box-shadow: $box-shadow;\n\n  &:hover,\n  &:focus {\n    box-shadow: $box-shadow-hover;\n  }\n}\n\n\n@include exports(\"thumb\") {\n  @if $include-html-media-classes {\n\n    /* Image Thumbnails */\n    .th {\n      @include thumb;\n      @include single-transition(all,$thumb-transition-speed,ease-out);\n\n      &.radius { @include radius($thumb-radius); }\n    }\n  }\n}","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n$include-html-type-classes: $include-html-classes !default;\n\n// We use these to control header font styles\n$header-font-family: $body-font-family !default;\n$header-font-weight: $font-weight-normal !default;\n$header-font-style: $font-weight-normal !default;\n$header-font-color: $jet !default;\n$header-line-height: 1.4 !default;\n$header-top-margin: .2rem !default;\n$header-bottom-margin: .5rem !default;\n$header-text-rendering: optimizeLegibility !default;\n\n// We use these to control header font sizes\n$h1-font-size: rem-calc(44) !default;\n$h2-font-size: rem-calc(37) !default;\n$h3-font-size: rem-calc(27) !default;\n$h4-font-size: rem-calc(23) !default;\n$h5-font-size: rem-calc(18) !default;\n$h6-font-size: 1rem !default;\n\n// We use these to control header size reduction on small screens\n$h1-font-reduction: rem-calc(10) !default;\n$h2-font-reduction: rem-calc(10) !default;\n$h3-font-reduction: rem-calc(5) !default;\n$h4-font-reduction: rem-calc(5) !default;\n$h5-font-reduction: 0 !default;\n$h6-font-reduction: 0 !default;\n\n// These control how subheaders are styled.\n$subheader-line-height: 1.4 !default;\n$subheader-font-color: scale-color($header-font-color, $lightness: 35%) !default;\n$subheader-font-weight: $font-weight-normal !default;\n$subheader-top-margin: .2rem !default;\n$subheader-bottom-margin: .5rem !default;\n\n// A general <small> styling\n$small-font-size: 60% !default;\n$small-font-color: scale-color($header-font-color, $lightness: 35%) !default;\n\n// We use these to style paragraphs\n$paragraph-font-family: inherit !default;\n$paragraph-font-weight: $font-weight-normal !default;\n$paragraph-font-size: 1rem !default;\n$paragraph-line-height: 1.6 !default;\n$paragraph-margin-bottom: rem-calc(20) !default;\n$paragraph-aside-font-size: rem-calc(14) !default;\n$paragraph-aside-line-height: 1.35 !default;\n$paragraph-aside-font-style: italic !default;\n$paragraph-text-rendering: optimizeLegibility !default;\n\n// We use these to style <code> tags\n$code-color: $oil !default;\n$code-font-family: $font-family-monospace !default;\n$code-font-weight: $font-weight-normal !default;\n$code-background-color: scale-color($secondary-color, $lightness: 70%) !default;\n$code-border-size: 0px !default;\n$code-border-style: solid !default;\n$code-border-color: scale-color($code-background-color, $lightness: -10%) !default;\n$code-padding: rem-calc(2) rem-calc(5) rem-calc(1) !default;\n\n// We use these to style anchors\n$anchor-text-decoration: none !default;\n$anchor-text-decoration-hover: none !default;\n$anchor-font-color: $primary-color !default;\n$anchor-font-color-hover: scale-color($anchor-font-color, $lightness: -14%) !default;\n\n// We use these to style the <hr> element\n$hr-border-width: 1px !default;\n$hr-border-style: solid !default;\n$hr-border-color: $gainsboro !default;\n$hr-margin: rem-calc(20) !default;\n\n// We use these to style lists\n$list-font-family: $paragraph-font-family !default;\n$list-font-size: $paragraph-font-size !default;\n$list-line-height: $paragraph-line-height !default;\n$list-margin-bottom: $paragraph-margin-bottom !default;\n$list-style-position: outside !default;\n$list-side-margin: 1.1rem !default;\n$list-ordered-side-margin: 1.4rem !default;\n$list-side-margin-no-bullet: 0 !default;\n$list-nested-margin: rem-calc(20) !default;\n$definition-list-header-weight: $font-weight-bold !default;\n$definition-list-header-margin-bottom: .3rem !default;\n$definition-list-margin-bottom: rem-calc(12) !default;\n\n// We use these to style blockquotes\n$blockquote-font-color: scale-color($header-font-color, $lightness: 35%) !default;\n$blockquote-padding: rem-calc(9 20 0 19) !default;\n$blockquote-border: 1px solid $gainsboro !default;\n$blockquote-cite-font-size: rem-calc(13) !default;\n$blockquote-cite-font-color: scale-color($header-font-color, $lightness: 23%) !default;\n$blockquote-cite-link-color: $blockquote-cite-font-color !default;\n\n// Acronym styles\n$acronym-underline: 1px dotted $gainsboro !default;\n\n// We use these to control padding and margin\n$microformat-padding: rem-calc(10 12) !default;\n$microformat-margin: rem-calc(0 0 20 0) !default;\n\n// We use these to control the border styles\n$microformat-border-width: 1px !default;\n$microformat-border-style: solid !default;\n$microformat-border-color: $gainsboro !default;\n\n// We use these to control full name font styles\n$microformat-fullname-font-weight: $font-weight-bold !default;\n$microformat-fullname-font-size: rem-calc(15) !default;\n\n// We use this to control the summary font styles\n$microformat-summary-font-weight: $font-weight-bold !default;\n\n// We use this to control abbr padding\n$microformat-abbr-padding: rem-calc(0 1) !default;\n\n// We use this to control abbr font styles\n$microformat-abbr-font-weight: $font-weight-bold !default;\n$microformat-abbr-font-decoration: none !default;\n\n// Text alignment class names\n$align-class-names:\n  small-only,\n  small,\n  medium-only,\n  medium,\n  large-only,\n  large,\n  xlarge-only,\n  xlarge,\n  xxlarge-only,\n  xxlarge;\n\n// Text alignment breakpoints\n$align-class-breakpoints:\n  $small-only,\n  $small-up,\n  $medium-only,\n  $medium-up,\n  $large-only,\n  $large-up,\n  $xlarge-only,\n  $xlarge-up,\n  $xxlarge-only,\n  $xxlarge-up;\n\n// Generates text align and justify classes\n@mixin align-classes{\n  .text-left    { text-align: left !important; }\n  .text-right   { text-align: right !important; }\n  .text-center  { text-align: center !important; }\n  .text-justify { text-align: justify !important; }\n\n  @for $i from 1 through length($align-class-names) {\n    @media #{(nth($align-class-breakpoints, $i))} {\n      .#{(nth($align-class-names, $i))}-text-left { text-align: left !important; }\n      .#{(nth($align-class-names, $i))}-text-right   { text-align: right !important; }\n      .#{(nth($align-class-names, $i))}-text-center  { text-align: center !important; }\n      .#{(nth($align-class-names, $i))}-text-justify { text-align: justify !important; }\n    }\n  }\n}\n\n//\n// Typography Placeholders\n//\n\n// These will throw a deprecation warning if used within a media query.\n@mixin lead {\n  font-size: $paragraph-font-size + rem-calc(3.5);\n  line-height: 1.6;\n}\n\n@mixin subheader {\n  line-height: $subheader-line-height;\n  color: $subheader-font-color;\n  font-weight: $subheader-font-weight;\n  margin-top: $subheader-top-margin;\n  margin-bottom: $subheader-bottom-margin;\n}\n@include exports(\"type\") {\n  @if $include-html-type-classes {\n    // Responsive Text alignment\n    @include align-classes;\n\n    /* Typography resets */\n    div,\n    dl,\n    dt,\n    dd,\n    ul,\n    ol,\n    li,\n    h1,\n    h2,\n    h3,\n    h4,\n    h5,\n    h6,\n    pre,\n    form,\n    p,\n    blockquote,\n    th,\n    td {\n      margin:0;\n      padding:0;\n    }\n\n    /* Default Link Styles */\n    a {\n      color: $anchor-font-color;\n      text-decoration: $anchor-text-decoration;\n      line-height: inherit;\n\n      &:hover,\n      &:focus {\n        color: $anchor-font-color-hover;\n        @if $anchor-text-decoration-hover != $anchor-text-decoration {\n        \ttext-decoration: $anchor-text-decoration-hover;\n        }\n      }\n\n      img { border:none; }\n    }\n\n    /* Default paragraph styles */\n    p {\n      font-family: $paragraph-font-family;\n      font-weight: $paragraph-font-weight;\n      font-size: $paragraph-font-size;\n      line-height: $paragraph-line-height;\n      margin-bottom: $paragraph-margin-bottom;\n      text-rendering: $paragraph-text-rendering;\n\n      &.lead { @include lead; }\n\n      & aside {\n        font-size: $paragraph-aside-font-size;\n        line-height: $paragraph-aside-line-height;\n        font-style: $paragraph-aside-font-style;\n      }\n    }\n\n    /* Default header styles */\n    h1, h2, h3, h4, h5, h6 {\n      font-family: $header-font-family;\n      font-weight: $header-font-weight;\n      font-style: $header-font-style;\n      color: $header-font-color;\n      text-rendering: $header-text-rendering;\n      margin-top: $header-top-margin;\n      margin-bottom: $header-bottom-margin;\n      line-height: $header-line-height;\n\n      small {\n        font-size: $small-font-size;\n        color: $small-font-color;\n        line-height: 0;\n      }\n    }\n\n    h1 { font-size: $h1-font-size - $h1-font-reduction; }\n    h2 { font-size: $h2-font-size - $h2-font-reduction; }\n    h3 { font-size: $h3-font-size - $h3-font-reduction; }\n    h4 { font-size: $h4-font-size - $h4-font-reduction; }\n    h5 { font-size: $h5-font-size - $h5-font-reduction; }\n    h6 { font-size: $h6-font-size - $h6-font-reduction; }\n\n    .subheader { @include subheader; }\n\n    hr {\n      border: $hr-border-style $hr-border-color;\n      border-width: $hr-border-width 0 0;\n      clear: both;\n      margin: $hr-margin 0 ($hr-margin - rem-calc($hr-border-width));\n      height: 0;\n    }\n\n    /* Helpful Typography Defaults */\n    em,\n    i {\n      font-style: italic;\n      line-height: inherit;\n    }\n\n    strong,\n    b {\n      font-weight: $font-weight-bold;\n      line-height: inherit;\n    }\n\n    small {\n      font-size: $small-font-size;\n      line-height: inherit;\n    }\n\n    code {\n      font-family: $code-font-family;\n      font-weight: $code-font-weight;\n      color: $code-color;\n      background-color: $code-background-color;\n      border-width: $code-border-size;\n      border-style: $code-border-style;\n      border-color: $code-border-color;\n      padding: $code-padding;\n    }\n\n    /* Lists */\n    ul,\n    ol,\n    dl {\n      font-size: $list-font-size;\n      line-height: $list-line-height;\n      margin-bottom: $list-margin-bottom;\n      list-style-position: $list-style-position;\n      font-family: $list-font-family;\n    }\n\n    ul {\n      margin-#{$default-float}: $list-side-margin;\n      &.no-bullet {\n        margin-#{$default-float}: $list-side-margin-no-bullet;\n        li {\n          ul,\n          ol {\n            margin-#{$default-float}: $list-nested-margin;\n            margin-bottom: 0;\n            list-style: none;\n          }\n        }\n      }\n    }\n\n    /* Unordered Lists */\n    ul {\n      li {\n        ul,\n        ol {\n          margin-#{$default-float}: $list-nested-margin;\n          margin-bottom: 0;\n        }\n      }\n      &.square,\n      &.circle,\n      &.disc {\n        li ul { list-style: inherit; }\n      }\n\n      &.square { list-style-type: square; margin-#{$default-float}: $list-side-margin;}\n      &.circle { list-style-type: circle; margin-#{$default-float}: $list-side-margin;}\n      &.disc { list-style-type: disc; margin-#{$default-float}: $list-side-margin;}\n      &.no-bullet { list-style: none; }\n    }\n\n    /* Ordered Lists */\n    ol {\n      margin-#{$default-float}: $list-ordered-side-margin;\n      li {\n        ul,\n        ol {\n          margin-#{$default-float}: $list-nested-margin;\n          margin-bottom: 0;\n        }\n      }\n    }\n\n    /* Definition Lists */\n    dl {\n      dt {\n        margin-bottom: $definition-list-header-margin-bottom;\n        font-weight: $definition-list-header-weight;\n      }\n      dd { margin-bottom: $definition-list-margin-bottom; }\n    }\n\n    /* Abbreviations */\n    abbr,\n    acronym {\n      text-transform: uppercase;\n      font-size: 90%;\n      color: $body-font-color;\n      cursor: $cursor-help-value;\n    }\n    abbr {\n      text-transform: none;\n      &[title] {\n        border-bottom: $acronym-underline;\n      }\n    }\n\n    /* Blockquotes */\n    blockquote {\n      margin: 0 0 $paragraph-margin-bottom;\n      padding: $blockquote-padding;\n      border-#{$default-float}: $blockquote-border;\n\n      cite {\n        display: block;\n        font-size: $blockquote-cite-font-size;\n        color: $blockquote-cite-font-color;\n        &:before {\n          content: \"\\2014 \\0020\";\n        }\n\n        a,\n        a:visited {\n          color: $blockquote-cite-link-color;\n        }\n      }\n    }\n    blockquote,\n    blockquote p {\n      line-height: $paragraph-line-height;\n      color: $blockquote-font-color;\n    }\n\n    /* Microformats */\n    .vcard {\n      display: inline-block;\n      margin: $microformat-margin;\n      border: $microformat-border-width $microformat-border-style $microformat-border-color;\n      padding: $microformat-padding;\n\n      li {\n        margin: 0;\n        display: block;\n      }\n      .fn {\n        font-weight: $microformat-fullname-font-weight;\n        font-size: $microformat-fullname-font-size;\n      }\n    }\n\n    .vevent {\n      .summary { font-weight: $microformat-summary-font-weight; }\n\n      abbr {\n        cursor: $cursor-default-value;\n        text-decoration: $microformat-abbr-font-decoration;\n        font-weight: $microformat-abbr-font-weight;\n        border: none;\n        padding: $microformat-abbr-padding;\n      }\n    }\n\n\n    @media #{$medium-up} {\n      h1,h2,h3,h4,h5,h6 { line-height: $header-line-height; }\n      h1 { font-size: $h1-font-size; }\n      h2 { font-size: $h2-font-size; }\n      h3 { font-size: $h3-font-size; }\n      h4 { font-size: $h4-font-size; }\n      h5 { font-size: $h5-font-size; }\n      h6 { font-size: $h6-font-size; }\n    }\n\n    // Only include these styles if you want them.\n    @if $include-print-styles {\n      /*\n       * Print styles.\n       *\n       * Inlined to avoid required HTTP connection: www.phpied.com/delay-loading-your-print-css/\n       * Credit to Paul Irish and HTML5 Boilerplate (html5boilerplate.com)\n      */\n      .print-only { display: none !important; }\n      @media print {\n        * {\n          background: transparent !important;\n          color: $black !important; /* Black prints faster: h5bp.com/s */\n          box-shadow: none !important;\n          text-shadow: none !important;\n        }\n\n        a,\n        a:visited { text-decoration: underline;}\n        a[href]:after { content: \" (\" attr(href) \")\"; }\n\n        abbr[title]:after { content: \" (\" attr(title) \")\"; }\n\n        // Don't show links for images, or javascript/internal links\n        .ir a:after,\n        a[href^=\"javascript:\"]:after,\n        a[href^=\"#\"]:after { content: \"\"; }\n\n        pre,\n        blockquote {\n          border: 1px solid $aluminum;\n          page-break-inside: avoid;\n        }\n\n        thead { display: table-header-group; /* h5bp.com/t */ }\n\n        tr,\n        img { page-break-inside: avoid; }\n\n        img { max-width: 100% !important; }\n\n        @page { margin: 0.5cm; }\n\n        p,\n        h2,\n        h3 {\n          orphans: 3;\n          widows: 3;\n        }\n\n        h2,\n        h3 { page-break-after: avoid; }\n\n        .hide-on-print { display: none !important; }\n        .print-only { display: block !important; }\n        .hide-for-print { display: none !important; }\n        .show-for-print { display: inherit !important; }\n      }\n    }\n\n  }\n}\n","// Foundation by ZURB\n// foundation.zurb.com\n// Licensed under MIT Open Source\n\n@import \"global\";\n\n//\n// Foundation Visibility Classes\n//\n$include-html-visibility-classes: $include-html-classes !default;\n$include-accessibility-classes: true !default;\n$include-table-visibility-classes: true !default;\n$include-legacy-visibility-classes: true !default;\n\n//\n// Media Class Names\n//\n// Visibility Breakpoints\n$visibility-breakpoint-sizes:\n  small,\n  medium,\n  large,\n  xlarge,\n  xxlarge;\n\n$visibility-breakpoint-queries:\n  unquote($small-up),\n  unquote($medium-up),\n  unquote($large-up),\n  unquote($xlarge-up),\n  unquote($xxlarge-up);\n\n@mixin visibility-loop {\n  @each $current-visibility-breakpoint in $visibility-breakpoint-sizes {\n    $visibility-inherit-list: ();\n    $visibility-none-list: ();\n\n    $visibility-visible-list: ();\n    $visibility-hidden-list: ();\n\n    $visibility-table-list: ();\n    $visibility-table-header-group-list: ();\n    $visibility-table-row-group-list: ();\n    $visibility-table-row-list: ();\n    $visibility-table-cell-list: ();\n\n    @each $visibility-comparison-breakpoint in $visibility-breakpoint-sizes {\n      @if index($visibility-breakpoint-sizes, $visibility-comparison-breakpoint) < index($visibility-breakpoint-sizes, $current-visibility-breakpoint) {\n        // Smaller than current breakpoint\n\n        $visibility-inherit-list: append($visibility-inherit-list, unquote(\n          '.hide-for-#{$visibility-comparison-breakpoint}-only, .show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-none-list: append($visibility-none-list, unquote(\n          '.show-for-#{$visibility-comparison-breakpoint}-only, .hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-visible-list: append($visibility-visible-list, unquote(\n          '.hidden-for-#{$visibility-comparison-breakpoint}-only, .visible-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-hidden-list: append($visibility-hidden-list, unquote(\n          '.visible-for-#{$visibility-comparison-breakpoint}-only, .hidden-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-list: append($visibility-table-list, unquote(\n          'table.hide-for-#{$visibility-comparison-breakpoint}-only, table.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n          'thead.hide-for-#{$visibility-comparison-breakpoint}-only, thead.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n          'tbody.hide-for-#{$visibility-comparison-breakpoint}-only, tbody.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-list: append($visibility-table-row-list, unquote(\n          'tr.hide-for-#{$visibility-comparison-breakpoint}-only, tr.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n          'th.hide-for-#{$visibility-comparison-breakpoint}-only, td.hide-for-#{$visibility-comparison-breakpoint}-only, th.show-for-#{$visibility-comparison-breakpoint}-up, td.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n\n        // Foundation 4 compatibility:\n        // Include .show/hide-for-[size] and .show/hide-for-[size]-down classes\n        // for small, medium, and large breakpoints only\n        @if $include-legacy-visibility-classes and index((small, medium, large), $visibility-comparison-breakpoint) != false {\n          $visibility-inherit-list: append($visibility-inherit-list, unquote(\n            '.hide-for-#{$visibility-comparison-breakpoint}, .hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-none-list: append($visibility-none-list, unquote(\n            '.show-for-#{$visibility-comparison-breakpoint}, .show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-visible-list: append($visibility-visible-list, unquote(\n            '.hidden-for-#{$visibility-comparison-breakpoint}, .hidden-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-hidden-list: append($visibility-hidden-list, unquote(\n            '.visible-for-#{$visibility-comparison-breakpoint}, .visible-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-list: append($visibility-table-list, unquote(\n            'table.hide-for-#{$visibility-comparison-breakpoint}, table.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n            'thead.hide-for-#{$visibility-comparison-breakpoint}, thead.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n            'tbody.hide-for-#{$visibility-comparison-breakpoint}, tbody.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-list: append($visibility-table-row-list, unquote(\n            'tr.hide-for-#{$visibility-comparison-breakpoint}, tr.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n            'th.hide-for-#{$visibility-comparison-breakpoint}, td.hide-for-#{$visibility-comparison-breakpoint}, th.hide-for-#{$visibility-comparison-breakpoint}-down, td.hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n        }\n\n      } @else if index($visibility-breakpoint-sizes, $visibility-comparison-breakpoint) > index($visibility-breakpoint-sizes, $current-visibility-breakpoint) {\n        // Larger than current breakpoint\n\n        $visibility-inherit-list: append($visibility-inherit-list, unquote(\n          '.hide-for-#{$visibility-comparison-breakpoint}-only, .hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-none-list: append($visibility-none-list, unquote(\n          '.show-for-#{$visibility-comparison-breakpoint}-only, .show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-visible-list: append($visibility-visible-list, unquote(\n          '.hidden-for-#{$visibility-comparison-breakpoint}-only, .hidden-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-hidden-list: append($visibility-hidden-list, unquote(\n          '.visible-for-#{$visibility-comparison-breakpoint}-only, .visible-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-list: append($visibility-table-list, unquote(\n          'table.hide-for-#{$visibility-comparison-breakpoint}-only, table.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n          'thead.hide-for-#{$visibility-comparison-breakpoint}-only, thead.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n          'tbody.hide-for-#{$visibility-comparison-breakpoint}-only, tbody.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-list: append($visibility-table-row-list, unquote(\n          'tr.hide-for-#{$visibility-comparison-breakpoint}-only, tr.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n          'th.hide-for-#{$visibility-comparison-breakpoint}-only, td.hide-for-#{$visibility-comparison-breakpoint}-only, th.hide-for-#{$visibility-comparison-breakpoint}-up, td.hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n\n        // Foundation 4 compatibility:\n        // Include .show/hide-for-[size] and .show/hide-for-[size]-down classes\n        // for small, medium, and large breakpoints only\n        @if $include-legacy-visibility-classes and index((small, medium, large), $visibility-comparison-breakpoint) != false {\n          $visibility-inherit-list: append($visibility-inherit-list, unquote(\n            '.hide-for-#{$visibility-comparison-breakpoint}, .show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-none-list: append($visibility-none-list, unquote(\n            '.show-for-#{$visibility-comparison-breakpoint}, .hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-visible-list: append($visibility-visible-list, unquote(\n            '.hidden-for-#{$visibility-comparison-breakpoint}, .visible-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-hidden-list: append($visibility-hidden-list, unquote(\n            '.visible-for-#{$visibility-comparison-breakpoint}, .hidden-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-list: append($visibility-table-list, unquote(\n            'table.hide-for-#{$visibility-comparison-breakpoint}, table.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n            'thead.hide-for-#{$visibility-comparison-breakpoint}, thead.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n            'tbody.hide-for-#{$visibility-comparison-breakpoint}, tbody.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-list: append($visibility-table-row-list, unquote(\n            'tr.hide-for-#{$visibility-comparison-breakpoint}, tr.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n            'th.hide-for-#{$visibility-comparison-breakpoint}, td.hide-for-#{$visibility-comparison-breakpoint}, th.show-for-#{$visibility-comparison-breakpoint}-down, td.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n        }\n\n      } @else {\n        // Current breakpoint\n\n        $visibility-inherit-list: append($visibility-inherit-list, unquote(\n          '.show-for-#{$visibility-comparison-breakpoint}-only, .show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-none-list: append($visibility-none-list, unquote(\n          '.hide-for-#{$visibility-comparison-breakpoint}-only, .hide-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-visible-list: append($visibility-visible-list, unquote(\n          '.visible-for-#{$visibility-comparison-breakpoint}-only, .visible-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-hidden-list: append($visibility-hidden-list, unquote(\n          '.hidden-for-#{$visibility-comparison-breakpoint}-only, .hidden-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-list: append($visibility-table-list, unquote(\n          'table.show-for-#{$visibility-comparison-breakpoint}-only, table.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n          'thead.show-for-#{$visibility-comparison-breakpoint}-only, thead.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n          'tbody.show-for-#{$visibility-comparison-breakpoint}-only, tbody.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-row-list: append($visibility-table-row-list, unquote(\n          'tr.show-for-#{$visibility-comparison-breakpoint}-only, tr.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n        $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n          'th.show-for-#{$visibility-comparison-breakpoint}-only, td.show-for-#{$visibility-comparison-breakpoint}-only, th.show-for-#{$visibility-comparison-breakpoint}-up, td.show-for-#{$visibility-comparison-breakpoint}-up'\n        ), comma);\n\n        // Foundation 4 compatibility:\n        // Include .show/hide-for-[size] and .show/hide-for-[size]-down classes\n        // for small, medium, and large breakpoints only\n        @if $include-legacy-visibility-classes and index((small, medium, large), $visibility-comparison-breakpoint) != false {\n          $visibility-inherit-list: append($visibility-inherit-list, unquote(\n            '.show-for-#{$visibility-comparison-breakpoint}, .show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-none-list: append($visibility-none-list, unquote(\n            '.hide-for-#{$visibility-comparison-breakpoint}, .hide-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-visible-list: append($visibility-visible-list, unquote(\n            '.visible-for-#{$visibility-comparison-breakpoint}, .visible-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-hidden-list: append($visibility-hidden-list, unquote(\n            '.hidden-for-#{$visibility-comparison-breakpoint}, .hidden-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-list: append($visibility-table-list, unquote(\n            'table.show-for-#{$visibility-comparison-breakpoint}, table.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-header-group-list: append($visibility-table-header-group-list, unquote(\n            'thead.show-for-#{$visibility-comparison-breakpoint}, thead.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-group-list: append($visibility-table-row-group-list, unquote(\n            'tbody.show-for-#{$visibility-comparison-breakpoint}, tbody.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-row-list: append($visibility-table-row-list, unquote(\n            'tr.show-for-#{$visibility-comparison-breakpoint}, tr.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n          $visibility-table-cell-list: append($visibility-table-cell-list, unquote(\n            'th.show-for-#{$visibility-comparison-breakpoint}, td.show-for-#{$visibility-comparison-breakpoint}, th.show-for-#{$visibility-comparison-breakpoint}-down, td.show-for-#{$visibility-comparison-breakpoint}-down'\n          ), comma);\n        }\n      }\n    }\n\n    /* #{$current-visibility-breakpoint} displays */\n    @media #{nth($visibility-breakpoint-queries, index($visibility-breakpoint-sizes, $current-visibility-breakpoint))} {\n      #{$visibility-inherit-list} {\n        display: inherit !important;\n      }\n      #{$visibility-none-list} {\n        display: none !important;\n      }\n      @if $include-accessibility-classes != false {\n        #{$visibility-visible-list} {\n          @include element-invisible-off;\n        }\n        #{$visibility-hidden-list} {\n          @include element-invisible;\n        }\n      }\n      @if $include-table-visibility-classes != false {\n        #{$visibility-table-list} {\n          display: table !important;\n        }\n        #{$visibility-table-header-group-list} {\n          display: table-header-group !important;\n        }\n        #{$visibility-table-row-group-list} {\n          display: table-row-group !important;\n        }\n        #{$visibility-table-row-list} {\n          display: table-row !important;\n        }\n        #{$visibility-table-cell-list} {\n          display: table-cell !important;\n        }\n      }\n    }\n  }\n}\n\n\n@if $include-html-visibility-classes != false {\n\n  @include visibility-loop;\n\n  /* Orientation targeting */\n  .show-for-landscape,\n  .hide-for-portrait { display: inherit !important; }\n  .hide-for-landscape,\n  .show-for-portrait { display: none !important; }\n\n  /* Specific visibility for tables */\n  table {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table !important; }\n  }\n  thead {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table-header-group !important; }\n  }\n  tbody {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table-row-group !important; }\n  }\n  tr {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table-row !important; }\n  }\n  td,\n  th {\n    &.hide-for-landscape,\n    &.show-for-portrait { display: table-cell !important; }\n  }\n\n  @media #{$landscape} {\n    .show-for-landscape,\n    .hide-for-portrait { display: inherit !important; }\n    .hide-for-landscape,\n    .show-for-portrait { display: none !important; }\n\n    /* Specific visibility for tables */\n    table {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table !important; }\n    }\n    thead {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table-header-group !important; }\n    }\n    tbody {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table-row-group !important; }\n    }\n    tr {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table-row !important; }\n    }\n    td,\n    th {\n      &.show-for-landscape,\n      &.hide-for-portrait { display: table-cell !important; }\n    }\n  }\n\n  @media #{$portrait} {\n    .show-for-portrait,\n    .hide-for-landscape { display: inherit !important; }\n    .hide-for-portrait,\n    .show-for-landscape { display: none !important; }\n\n    /* Specific visibility for tables */\n    table {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table !important; }\n    }\n    thead {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table-header-group !important; }\n    }\n    tbody {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table-row-group !important; }\n    }\n    tr {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table-row !important; }\n    }\n    td,\n    th {\n      &.show-for-portrait,\n      &.hide-for-landscape { display: table-cell !important; }\n    }\n  }\n\n  /* Touch-enabled device targeting */\n  .show-for-touch { display: none !important; }\n  .hide-for-touch { display: inherit !important; }\n  .touch .show-for-touch { display: inherit !important; }\n  .touch .hide-for-touch { display: none !important; }\n\n  /* Specific visibility for tables */\n  table.hide-for-touch { display: table !important; }\n  .touch table.show-for-touch { display: table !important; }\n  thead.hide-for-touch { display: table-header-group !important; }\n  .touch thead.show-for-touch { display: table-header-group !important; }\n  tbody.hide-for-touch { display: table-row-group !important; }\n  .touch tbody.show-for-touch { display: table-row-group !important; }\n  tr.hide-for-touch { display: table-row !important; }\n  .touch tr.show-for-touch { display: table-row !important; }\n  td.hide-for-touch { display: table-cell !important; }\n  .touch td.show-for-touch { display: table-cell !important; }\n  th.hide-for-touch { display: table-cell !important; }\n  .touch th.show-for-touch { display: table-cell !important; }\n\n\n  /* Print visibility */\n  @media print {\n    .show-for-print { display: block; }\n    .hide-for-print { display: none; }\n\n    table.show-for-print { display: table !important; }\n    thead.show-for-print { display: table-header-group !important; }\n    tbody.show-for-print { display: table-row-group !important; }\n    tr.show-for-print { display: table-row !important; }\n    td.show-for-print { display: table-cell !important; }\n    th.show-for-print { display: table-cell !important; }\n\n  }\n\n}\n","@charset \"utf-8\";\n/* TOC – Typography\n\nCheck typography variables › _3_typography_settings.scss\n\n- Links\n- Customize Foundation Typography\n- Headlines\n- Images\n- Lists\n- Tables\n- Code\n- Quotes\n- Typography for Articles\n- Smaller Fontsize for Bigteaser on small devices\n- Additional typographical elements\n- Footnotes\n- Icon Font\n\n*/\n\n\n\n/* Links\n------------------------------------------------------------------- */\n\na,\na:link {\n    transition: all .4s;\n    color: $link-unvisited;\n}\n\na:visited {\n    border-bottom: $grey-2;\n    color: $link-visited;\n}\n\na:hover {\n    color: $link-hover;\n}\n\na:focus {\n    color: $link-focus;\n}\n\na:active {\n    color: $link-active;\n}\n\n\n\n/* Customize Foundation Typography\n------------------------------------------------------------------- */\n\np {\n    -webkit-hyphens: auto;\n    -moz-hyphens: auto;\n    -ms-hyphens: auto;\n    hyphens: auto;\n    -ms-word-break: normal;\n    /* Non standard for webkit */\n    word-break: normal;\n}\np a,\narticle a {\n    font-weight: bold;\n    border-bottom: 1px dotted;\n}\np a:hover,\narticle a:hover {\n    border-bottom: 2px solid;\n}\np a.button,\n.button,\n.button:hover {\n    border: 0;\n    color: #fff;\n}\np.button a {\n    border: 0;\n    color: #fff;\n    text-shadow: 0 1px 3px rgba(0, 0, 0, 0.5);\n}\n\n\n\n/* Headlines\n   The hK::before logic is to accomodate a vert. offset for persistent\n   top of page menu. The logic is copied from\n   https://css-tricks.com/hash-tag-links-padding/\n------------------------------------------------------------------- */\n\nh1, h2, h3, h4, h5, h6 {\n    font-family: $header-font-family;\n    font-weight: normal;\n    padding: 0;\n}\nh1 {\n    font-size: $font-size-h1;\n    margin-top: 0;\n}\nh2 {\n    font-size: $font-size-h2;\n    margin: 1.563em 0 0 0;\n}\n    .blog-index h2 {\n        margin-top: 0;\n    }\nh3 {\n    font-size: $font-size-h3;\n    margin: 1.152em 0 0 0;\n}\nh4 {\n    font-size: $font-size-h4;\n    margin: 1.152em 0 0 0;\n}\nh5 {\n    font-size: $font-size-h5;\n    margin: 1em 0 0 0;\n}\n\n\n\n/* Images\n------------------------------------------------------------------- */\n\nimg { border-radius: $global-radius;}\n    img.alignleft,\n    img.left        { float: left; margin:5px 15px 5px 0; }\n    img.alignright,\n    img.right       { float: right; margin:5px 0 5px 15px; }\n    img.aligncenter,\n    img.center      { display: block; margin:0 auto 10px; }\n\nfigure {\n    margin: 0 0 rem-calc(30) 0;\n}\n#masthead-with-background-color figure,\n#masthead-with-pattern figure {\n    margin: 0;\n}\nfigcaption,\n.masthead-caption {\n    color: $grey-10;\n    font-family: $font-family-sans-serif;\n    font-size: rem-calc(13);\n    padding-top: rem-calc(2);\n}\nfigcaption a,\n.masthead-caption a {\n    border-bottom: 1px dotted $grey-4;\n    color: $grey-10;\n}\nfigcaption a:hover,\n.masthead-caption a:hover {\n    border-bottom: 2px solid $primary-color;\n    color: $primary-color;\n}\n.masthead-caption {\n    padding-right: 10px;\n    text-align: right;\n}\n\n\n\n/* Tables\n------------------------------------------------------------------- */\n\ntd {\n    vertical-align: top;\n}\n\n\n\n/* Code\n------------------------------------------------------------------- */\n\npre {\n    overflow: auto;\n    margin-bottom: rem-calc(20);\n    padding: 5px;\n    background-color: $code-background-color;\n    border-radius: $global-radius;\n}\npre code {\n    padding: rem-calc(2) rem-calc(5) rem-calc(1) rem-calc(0);\n    border: 0;\n}\n\ncode {\n    font-size: rem-calc(14);\n    line-height: 1.5;\n}\n\n\n\n/* Lists\n------------------------------------------------------------------- */\n\nul, ol {\n    margin-left: 20px;\n    padding: 0;\n}\nli {\n    margin-left: 0;\n}\n\n.no-bullet {\n    list-style: none;\n    margin-left: 0;\n}\n\nli {\n    > ul,\n    > ol {\n         margin-bottom: 0;\n    }\n}\n\ndl {\n\n}\ndt:first-child {\n    padding-top: 0px;\n}\ndt {\n    font-weight: bold;\n    padding-top: 30px;\n}\ndd {\n}\narticle dl dt   { line-height: 1.3; }\narticle dl dd   { line-height: 1.6; margin-bottom: rem-calc(12); margin-left: rem-calc(24); }\n\n\n\n/* Quotes\n------------------------------------------------------------------- */\n\nblockquote {\n    font-style: italic;\n    position: relative;\n    border: none;\n    margin: 0 30px 30px 30px;\n    color:  $grey-11;\n}\n\n    blockquote p {font-style: italic; color: $grey-10; }\n\n    blockquote:before {\n        display:block;content:\"\\00BB\";\n        font-size:80px;\n        line-height: 0;\n        position:absolute;\n        left:-25px;\n        top: auto;\n        color: $grey-11;\n    }\n    blockquote:after {\n        display:block;\n        content:\"\\00AB\";\n        font-size:80px;\n        line-height: 0;\n        position:absolute;\n        right:-10px;\n        bottom: 20px;\n        color: $grey-11;\n    }\n    blockquote cite:before {\n        content:\"\\2014 \\0020\"\n    }\n    blockquote cite a,blockquote cite a:visited {\n        color: $grey-10;\n    }\ncite {\n    padding-top: 5px;\n}\n\nbutton, .button {\n    letter-spacing: 1px;\n}\n\nmark {\n    background-color: scale-color($warning-color, $lightness: 60%);\n}\n\n\n\n/* Typography for Articles\n------------------------------------------------------------------- */\n\n.subheadline {\n    font-size: rem-calc(16);\n    margin: 0;\n    text-transform: uppercase;\n}\n.teaser {\n    font-size: rem-calc(20);\n}\n.big-teaser {\n    font-style: italic; font-weight: 300;\n}\n.big-teaser a {\n    font-style: italic; font-weight: 400;\n}\n\n/* Smaller Fontsize for Bigteaser on small devices */\n@media only screen {\n    .big-teaser {\n        font-size: rem-calc(20);\n    }\n}\n@media only screen and (min-width: 40.063em) {\n    .big-teaser         {\n        font-size: rem-calc(29);\n    }\n}\n\n\n\n/* Additional typographical elements\n------------------------------------------------------------------- */\n\n.sans           { font-family: $font-family-sans-serif; }\n.serif          { font-family: $font-family-serif; }\n\n.font-size-h1   { font-size: $font-size-h1; }\n.font-size-h2   { font-size: $font-size-h2; }\n.font-size-h3   { font-size: $font-size-h3; }\n.font-size-h4   { font-size: $font-size-h4; }\n.font-size-h5   { font-size: $font-size-h5; }\n.font-size-p    { font-size: $font-size-p; }\n\n\n\n/* Footnotes\n------------------------------------------------------------------- */\n\n.footnotes:before {\n    content: \"\";\n    position: absolute;\n    height: 1px;\n    width: 60px;\n    margin-top: -10px;\n    border-bottom: 1px solid $grey-2;\n}\n.footnotes {\n    margin-top: 60px;\n}\n.footnotes ol {\n    font-size: $font-size-small;\n}\n.footnotes p {\n    font-size: inherit;\n    margin-bottom: 0;\n}\n\n\n\n\n/* Icon Font\n   See the icon-set/preview in /assets/fonts/iconfont-preview.html\n------------------------------------------------------------------- */\n\n@font-face {\n  font-family: 'iconfont';\n  src: url('../fonts/iconfont.eot'); /* IE9 Compat Modes */\n  src: url('../fonts/iconfont.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */\n       url('../fonts/iconfont.woff') format('woff'), /* Pretty Modern Browsers */\n       url('../fonts/iconfont.ttf')  format('truetype'), /* Safari, Android, iOS */\n       url('../fonts/iconfont.svg#svgFontName') format('svg'); /* Legacy iOS */\n}\n\n.iconfont       { font-family: iconfont; }\n.iconfont-48    { font-size: 48px; }\n\n\n[data-icon]:before { content: attr(data-icon); }\n\n[data-icon]:before,\n.icon-archive:before,\n.icon-browser:before,\n.icon-calendar:before,\n.icon-camera:before,\n.icon-chat:before,\n.icon-check:before,\n.icon-chevron-down:before,\n.icon-chevron-left:before,\n.icon-chevron-right:before,\n.icon-chevron-up:before,\n.icon-circle-with-cross:before,\n.icon-circle-with-minus:before,\n.icon-circle-with-plus:before,\n.icon-cloud:before,\n.icon-code:before,\n.icon-cog:before,\n.icon-dropbox:before,\n.icon-edit:before,\n.icon-export:before,\n.icon-eye:before,\n.icon-facebook:before,\n.icon-feather:before,\n.icon-github:before,\n.icon-globe:before,\n.icon-googleplus:before,\n.icon-heart:before,\n.icon-heart-outlined:before,\n.icon-home:before,\n.icon-instagram:before,\n.icon-lab-flask:before,\n.icon-leaf:before,\n.icon-linkedin:before,\n.icon-mail:before,\n.icon-message:before,\n.icon-mic:before,\n.icon-network:before,\n.icon-paper-plane:before,\n.icon-pinterest:before,\n.icon-price-tag:before,\n.icon-rocket:before,\n.icon-rss:before,\n.icon-soundcloud:before,\n.icon-star:before,\n.icon-star-outlined:before,\n.icon-thumbs-down:before,\n.icon-thumbs-up:before,\n.icon-tree:before,\n.icon-tumblr:before,\n.icon-twitter:before,\n.icon-upload-to-cloud:before,\n.icon-video:before,\n.icon-vimeo:before,\n.icon-warning:before,\n.icon-xing:before,\n.icon-youtube:before {\n  display: inline-block;\nfont-family: \"iconfont\";\nfont-style: normal;\nfont-weight: normal;\nfont-variant: normal;\nline-height: 1;\ntext-decoration: inherit;\ntext-rendering: optimizeLegibility;\ntext-transform: none;\n-moz-osx-font-smoothing: grayscale;\n-webkit-font-smoothing: antialiased;\nfont-smoothing: antialiased;\n}\n\n.icon-archive:before { content: \"\\f100\"; }\n.icon-browser:before { content: \"\\f101\"; }\n.icon-calendar:before { content: \"\\f133\"; }\n.icon-camera:before { content: \"\\f102\"; }\n.icon-chat:before { content: \"\\f103\"; }\n.icon-check:before { content: \"\\f104\"; }\n.icon-chevron-down:before { content: \"\\f105\"; }\n.icon-chevron-left:before { content: \"\\f106\"; }\n.icon-chevron-right:before { content: \"\\f107\"; }\n.icon-chevron-up:before { content: \"\\f108\"; }\n.icon-circle-with-cross:before { content: \"\\f109\"; }\n.icon-circle-with-minus:before { content: \"\\f10a\"; }\n.icon-circle-with-plus:before { content: \"\\f10b\"; }\n.icon-cloud:before { content: \"\\f10c\"; }\n.icon-code:before { content: \"\\f10d\"; }\n.icon-cog:before { content: \"\\f10e\"; }\n.icon-dropbox:before { content: \"\\f10f\"; }\n.icon-edit:before { content: \"\\f110\"; }\n.icon-export:before { content: \"\\f111\"; }\n.icon-eye:before { content: \"\\f112\"; }\n.icon-facebook:before { content: \"\\f113\"; }\n.icon-feather:before { content: \"\\f114\"; }\n.icon-github:before { content: \"\\f115\"; }\n.icon-globe:before { content: \"\\f116\"; }\n.icon-googleplus:before { content: \"\\f136\"; }\n.icon-heart:before { content: \"\\f117\"; }\n.icon-heart-outlined:before { content: \"\\f118\"; }\n.icon-home:before { content: \"\\f119\"; }\n.icon-instagram:before { content: \"\\f11a\"; }\n.icon-lab-flask:before { content: \"\\f11b\"; }\n.icon-leaf:before { content: \"\\f11c\"; }\n.icon-linkedin:before { content: \"\\f11d\"; }\n.icon-mail:before { content: \"\\f11e\"; }\n.icon-message:before { content: \"\\f11f\"; }\n.icon-mic:before { content: \"\\f120\"; }\n.icon-network:before { content: \"\\f121\"; }\n.icon-paper-plane:before { content: \"\\f122\"; }\n.icon-pinterest:before { content: \"\\f123\"; }\n.icon-price-tag:before { content: \"\\f124\"; }\n.icon-rocket:before { content: \"\\f125\"; }\n.icon-rss:before { content: \"\\f126\"; }\n.icon-soundcloud:before { content: \"\\f127\"; }\n.icon-star:before { content: \"\\f128\"; }\n.icon-star-outlined:before { content: \"\\f129\"; }\n.icon-thumbs-down:before { content: \"\\f12a\"; }\n.icon-thumbs-up:before { content: \"\\f12b\"; }\n.icon-tree:before { content: \"\\f134\"; }\n.icon-tumblr:before { content: \"\\f12c\"; }\n.icon-twitter:before { content: \"\\f12d\"; }\n.icon-upload-to-cloud:before { content: \"\\f12e\"; }\n.icon-video:before { content: \"\\f12f\"; }\n.icon-vimeo:before { content: \"\\f130\"; }\n.icon-warning:before { content: \"\\f131\"; }\n.icon-xing:before { content: \"\\f135\"; }\n.icon-youtube:before { content: \"\\f132\"; }\n","@charset \"utf-8\";\n/* TOC\n\n- Adjustments: Video Layout\n- Navigation\n- Search\n- Masthead\n- Masthead › small-only\n- Masthead › medium-only\n- Masthead › large-only\n- Masthead › xlarge-up\n- Breadcrumb\n- Meta\n- Jump to top\n- Footer\n- Subfooter\n- CSS-Classes to add margin at top or bottom\n\n*/\n\n\n\n/* Adjustments: Video Layout\n------------------------------------------------------------------- */\n\nbody.video,\nbody.video #masthead-no-image-header { background: #000; }\nbody.video #masthead-no-image-header { margin-bottom: 60px; }\nbody.video h1,\nbody.video h2,\nbody.video h3,\nbody.video h4,\nbody.video h5,\nbody.video h6,\nbody.video p,\nbody.video a,\nbody.video blockquote:before,\nbody.video blockquote:after,\nbody.video cite a, { color: #fff; }\nbody.video cite a:visited, { color: #fff; }\nbody.video cite { color: #fff; }\n\n\n\n/* Navigation\n------------------------------------------------------------------- */\n\n#navigation {\n    -webkit-box-shadow: 0 2px 2px 0 rgba(0,0,0,.2);\n    box-shadow: 0 2px 3px 0 rgba(0,0,0,.2);\n\n    [class^='icon-']:before, [class*=' icon-']:before {\n        margin-right: rem-calc(8);\n    }\n}\n\n\n\n/* Search\n------------------------------------------------------------------- */\n\n.no-js form#search {\n  display: none;\n}\n\n\n\n/* Masthead\n------------------------------------------------------------------- */\n\n#masthead {\n    background-color: $primary-color;\n}\n#masthead-no-image-header {\n    background-color: $primary-color;\n}\n#masthead-with-text {\n    text-align: center;\n    font-size: rem-calc(54);\n    font-family: $header-font-family;\n    color: #fff;\n    text-transform: uppercase;\n    text-shadow: 0 2px 3px rgba(0,0,0,.4);\n}\n#masthead-no-image-header {\n    height: 100px;\n    background-color: rgba(63,175,70,1);\n}\n#masthead-no-image-header #logo img {\n    margin-top: 10px;\n}\n\n// Made height/margin-top smaller for what wanted and half on small screen.\n\n/* Masthead › small-only\n------------------------------------------------------------------- */\n\n// Wanted to keep logo even on small screen so disable.\n@media #{$small-only} {\n    // #logo img {\n        // display: none;\n    // }\n    #logo img {\n        margin-top: 30px;\n    }\n    #masthead {\n        height: 100px;\n    }\n    #masthead-with-pattern {\n        padding: 15px 0;\n    }\n    #masthead-with-background-color {\n        padding: 15px 0;\n    }\n    #masthead-with-text {\n        height: 220px;\n        padding: 30px 0;\n        font-size: rem-calc(36);\n    }\n    // #masthead-no-image-header {\n    //     display: none;\n    // }\n    #masthead-no-image-header #logo img {\n        margin-top: 35px;\n    }\n}\n\n\n/* Masthead › medium-only\n------------------------------------------------------------------- */\n\n@media #{$medium-only} {\n    #logo img {\n        margin-top: 60px;\n    }\n    #masthead {\n        height: 200px;\n    }\n    #masthead-with-pattern {\n        padding: 20px 0;\n    }\n    #masthead-with-background-color {\n        padding: 20px 0;\n    }\n    #masthead-with-text {\n        padding: 60px 0;\n        height: 300px;\n    }\n    #masthead-no-image-header #logo img {\n        margin-top: 20px;\n    }\n}\n\n\n/* Masthead › large-only\n------------------------------------------------------------------- */\n\n@media #{$large-only} {\n    #logo img {\n        margin-top: 60px;\n    }\n    #masthead {\n        height: 200px;\n    }\n    #masthead-with-pattern {\n        padding: 30px 0;\n    }\n    #masthead-with-background-color {\n        padding: 30px 0;\n    }\n    #masthead-with-text {\n        height: 330px;\n        padding: 60px 0;\n    }\n}\n\n\n/* Masthead › xlarge-up\n------------------------------------------------------------------- */\n\n@media #{$xlarge-up} {\n    #logo img {\n        margin-top: 60px;\n    }\n    #masthead {\n        height: 200px;\n    }\n    #masthead-with-pattern {\n        padding: 45px 0;\n    }\n    #masthead-with-background-color {\n        padding: 45px 0;\n    }\n    #masthead-with-text {\n        padding: 95px 0;\n        height: 400px;\n    }\n}\n\n\n#title-image-small {\n    height: 240px;\n}\n#title-image-large {\n    height: 520px;\n}\n#title-image-index-small {\n    height: 120px;\n}\n#title-image-index-large {\n    height: 260px;\n}\n\n\n\n/* Breadcrumb\n------------------------------------------------------------------- */\n\n#breadcrumb {\n    background: scale-color($grey-1, $lightness: 55%);\n    border-top: 1px solid scale-color($grey-1, $lightness: 45%);\n    border-bottom: 1px solid scale-color($grey-1, $lightness: 45%);\n}\n.breadcrumbs>.current {\n  font-weight: bold;\n}\n\n\n/* Meta\n------------------------------------------------------------------- */\n\n#page-meta, #page-meta a {\n    color: $grey-5;\n}\n\n#page-meta .button {\n    background: $grey-5;\n    border: 0;\n}\n#page-meta .button {\n    color: #fff;\n}\n#page-meta .button:hover {\n    background: $primary-color;\n}\n.meta-info p {\n  font-size: rem-calc(13);\n  color: scale-color($grey-1, $lightness: 40%);\n}\n  .meta-info a {\n    text-decoration: underline;\n    color: scale-color($grey-1, $lightness: 40%);\n  }\n  .meta-info a:hover {\n    text-decoration: none;\n    color: $secondary-color;\n  }\n\n\n\n/* Jump to top\n------------------------------------------------------------------- */\n\n#up-to-top {\n    padding: 30px 0 10px 0;\n}\n#up-to-top a {\n    font-size: 24px;\n    padding: 5px;\n    border-radius: 3px;\n}\n#up-to-top a:hover {\n    background: $grey-2;\n}\n\n\n\n/* Footer\n------------------------------------------------------------------- */\n\n#footer-content p,\n#footer-content li {\n    font-size: rem-calc(13);\n    font-weight: 300;\n}\n\n#footer {\n    padding-top: 30px;\n    padding-bottom: 20px;\n    background: $footer-bg;\n    color: $footer-color;\n    }\n\n    #footer a {\n        color: $footer-link-color;\n    }\n    #footer h4,\n    #footer h5 {\n        letter-spacing: 1px;\n        color: #fff;\n        text-transform: uppercase;\n    }\n\n\n\n/* Subfooter\n------------------------------------------------------------------- */\n\n#subfooter {\n    background: $subfooter-bg;\n    color: $subfooter-color;\n    padding-top: 30px;\n}\n\n#subfooter-left ul.inline-list {\n    float: left;\n}\n\n.credits a {\n    color: $subfooter-link-color;\n    border: 0;\n    text-transform: uppercase;\n    &:hover {\n        color: #fff;\n  }\n}\n\n.social-icons {\n    margin-bottom: 10px !important;\n\n// Beware of SCSS-Syntax here\n  li {\n    padding: 0 0 20px 0;\n  }\n  a {\n    font-size: rem-calc(23);\n    display: block;\n    width: 36px;\n    border-radius: 50%;\n    color: $subfooter-bg;\n    background: $subfooter-color;\n    text-align: center;\n    &:hover {\n      background: $subfooter-bg;\n      color: #fff;\n    }\n  }\n}\n\n\n\n/* CSS-Classes to add margin at top or bottom\n------------------------------------------------------------------- */\n\n.t10 { margin-top: 10px !important; }\n.t15 { margin-top: 15px !important; }\n.t20 { margin-top: 20px !important; }\n.t30 { margin-top: 30px !important; }\n.t50 { margin-top: 50px !important; }\n.t60 { margin-top: 60px !important; }\n.t70 { margin-top: 70px !important; }\n.t80 { margin-top: 80px !important; }\n.t90 { margin-top: 90px !important; }\n\n.b15 { margin-bottom: 15px !important; }\n.b20 { margin-bottom: 20px !important; }\n.b30 { margin-bottom: 30px !important; }\n.b60 { margin-bottom: 60px !important; }\n\n.l15 { margin-left: 15px !important; }\n.r15 { margin-right: 15px !important; }\n\n.pl20 { padding-left: 20px !important; }\n.pr5  { padding-right: 5px !important; }\n.pr10 { padding-right: 10px !important; }\n.pr20 { padding-right: 20px !important; }\n","@charset \"utf-8\";\n/* TOC\n\n- Table of Contents (Index)\n- Panel\n- Shadows\n- Alerts\n- Breadcrumb\n- Button\n- Side-Nav\n- Accordion\n- Lazy Load XT\n- Frontpage Widget\n\n*/\n\n\n\n/* Table of Contents (Index)\n------------------------------------------------------------------- */\n\n#toc ul,\n#toc ul ul,\n#toc ul ul ul, {\n    list-style: none;\n    margin-left: 30px;\n}\n#toc ul {\n    margin-left: 0;\n    margin-top: $spacing-unit;\n}\n\n\n\n/* Panel\n------------------------------------------------------------------- */\n\n.border-dotted {\n  border: 1px dotted $grey-5;\n  padding: rem-calc(20);\n  border-radius: $global-radius;\n}\n\n\n\n/* Shadows\n------------------------------------------------------------------- */\n\n.shadow-no      {text-shadow: rgba(0, 0, 0, 0) 0 0 0;}\n.shadow-black   {text-shadow: rgba(0, 0, 0, 0.498039) 0px 1px 2px;}\n.shadow-white   {text-shadow: rgba(255, 255, 255, 0.498039) 0px 1px 2px;}\n\n\n\n/* Alerts\n------------------------------------------------------------------- */\n\n.alert-box {\n  font-family: $font-family-sans-serif;\n  text-shadow: 0px 1px 1px rgba(0,0,0,0.9);\n}\n  .alert-box p {\n    margin-bottom: 0;\n  }\n  .alert-box a {\n    text-shadow: 1px 1px 0px rgba(0, 0, 0, 1);\n    color: #fff;\n    border-bottom: 1px dotted #fff;\n  }\n  .alert-box a:hover {\n    border-bottom: 1px solid #fff;\n  }\n  .alert-box.terminal {\n    background: $grey-12; \n    color: #fff; \n    border-color: scale-color($grey-12, $lightness: -14%);\n    font-family: $font-family-monospace;\n  }\n  .alert-box.terminal::before {\n    content: \"$ \";\n    color: $ci-6;\n    float: left;\n    margin: .25em .5em 0 0;\n  }\n  .alert-box.text {\n    background-color: $grey-2;\n    text-shadow: 0px 0px 0px rgba(0,0,0,0.9);\n    border-color: scale-color($grey-2, $lightness: -14%);\n    color: $grey-12;\n  }\n  .alert-box.windowsOS {\n    @include alert-style(darkblue);\n  }\n  .alert-box.windowsOS::before {\n    content: \"Windows OS Information\";\n    color: $ci-4;\n  }\n\n\n/* Button\n------------------------------------------------------------------- */\n\nbutton, .button         { letter-spacing: 1px; }\n  button.grey, .button.grey { background: $grey-10; }\n  button.grey:hover,\n  button.grey:focus,\n  .button.grey:hover,\n  .button.grey:focus      { background-color: $grey-16; }\n\n\n\n/* Side-Nav\n------------------------------------------------------------------- */\n\n.side-nav li.title { text-transform: uppercase;}\n.side-nav li { border-top: 1px solid $grey-3;}\n.side-nav li a:not(.button) { border-bottom: 0; padding: 0.4375rem 0rem; }\n.side-nav li a:not(.button):hover, .side-nav li a:not(.button):focus { background: $grey-1; }\n\n.homepage p { margin: 0; padding: 0; color: $grey-10; }\n\n\n\n/* Accordion\n------------------------------------------------------------------- */\n\ndl.accordion  { border-top: 1px solid $grey-2;  }\n.accordion dd   { border-bottom: 1px solid $grey-2;  }\ndd.accordion-navigation span { padding-right: 12px; }\ndd.accordion-navigation span:before { content: \"\\F107\" }\ndd.accordion-navigation.active span:before { content: \"\\F105\" }\ndd.accordion-navigation.active span:before { content: \"\\F105\" }\n\n\n\n/* Lazy Load XT\n------------------------------------------------------------------- */\n\n/*! Lazy Load XT v1.0.6 2014-11-19\n * http://ressio.github.io/lazy-load-xt\n * (C) 2014 RESS.io\n * Licensed under MIT */\nimg.lazy {\n  display: none;\n}\n.lazy-hidden {\n    opacity: 0;\n}\n.lazy-loaded {\n    -webkit-transition: opacity 0.7s;\n    -moz-transition: opacity 0.7s;\n    -ms-transition: opacity 0.7s;\n    -o-transition: opacity 0.7s;\n    transition: opacity 0.7s;\n    opacity: 1;\n}\n\n*:target:not([id^='fn:']):not([id^='fnref:']) {\n  &::before {\n    content: \" \";\n    width: 0;\n    height: 0;\n\n    display: block;\n    padding-top: 50px;\n    margin-top: -50px;\n  }\n}\n","@charset \"utf-8\";\n/* Syntax highlighting styles\n------------------------------------------------------------------- */\n\n.highlight {\n    background: #fff;\n    [data-lang]::before {\n    content: attr(data-lang);\n    display: block;\n    text-align: right;\n    margin-right: 5px;\n    text-transform: uppercase;\n    }\n    .c     { color: #998; font-style: italic } // Comment\n    .err   { color: #a61717; background-color: #e3d2d2 } // Error\n    .k     { font-weight: bold } // Keyword\n    .o     { font-weight: bold } // Operator\n    .cm    { color: #998; font-style: italic } // Comment.Multiline\n    .cp    { color: #999; font-weight: bold } // Comment.Preproc\n    .c1    { color: #998; font-style: italic } // Comment.Single\n    .cs    { color: #999; font-weight: bold; font-style: italic } // Comment.Special\n    .gd    { color: #000; background-color: #fdd } // Generic.Deleted\n    .gd .x { color: #000; background-color: #faa } // Generic.Deleted.Specific\n    .ge    { font-style: italic } // Generic.Emph\n    .gr    { color: #a00 } // Generic.Error\n    .gh    { color: #999 } // Generic.Heading\n    .gi    { color: #000; background-color: #dfd } // Generic.Inserted\n    .gi .x { color: #000; background-color: #afa } // Generic.Inserted.Specific\n    .go    { color: #888 } // Generic.Output\n    .gp    { color: #555 } // Generic.Prompt\n    .gs    { font-weight: bold } // Generic.Strong\n    .gu    { color: #aaa } // Generic.Subheading\n    .gt    { color: #a00 } // Generic.Traceback\n    .kc    { font-weight: bold } // Keyword.Constant\n    .kd    { font-weight: bold } // Keyword.Declaration\n    .kp    { font-weight: bold } // Keyword.Pseudo\n    .kr    { font-weight: bold } // Keyword.Reserved\n    .kt    { color: #458; font-weight: bold } // Keyword.Type\n    .m     { color: #099 } // Literal.Number\n    .s     { color: #d14 } // Literal.String\n    .na    { color: #008080 } // Name.Attribute\n    .nb    { color: #0086B3 } // Name.Builtin\n    .nc    { color: #458; font-weight: bold } // Name.Class\n    .no    { color: #008080 } // Name.Constant\n    .ni    { color: #800080 } // Name.Entity\n    .ne    { color: #900; font-weight: bold } // Name.Exception\n    .nf    { color: #900; font-weight: bold } // Name.Function\n    .nn    { color: #555 } // Name.Namespace\n    .nt    { color: #000080 } // Name.Tag\n    .nv    { color: #008080 } // Name.Variable\n    .ow    { font-weight: bold } // Operator.Word\n    .w     { color: #bbb } // Text.Whitespace\n    .mf    { color: #099 } // Literal.Number.Float\n    .mh    { color: #099 } // Literal.Number.Hex\n    .mi    { color: #099 } // Literal.Number.Integer\n    .mo    { color: #099 } // Literal.Number.Oct\n    .sb    { color: #d14 } // Literal.String.Backtick\n    .sc    { color: #d14 } // Literal.String.Char\n    .sd    { color: #d14 } // Literal.String.Doc\n    .s2    { color: #d14 } // Literal.String.Double\n    .se    { color: #d14 } // Literal.String.Escape\n    .sh    { color: #d14 } // Literal.String.Heredoc\n    .si    { color: #d14 } // Literal.String.Interpol\n    .sx    { color: #d14 } // Literal.String.Other\n    .sr    { color: #009926 } // Literal.String.Regex\n    .s1    { color: #d14 } // Literal.String.Single\n    .ss    { color: #990073 } // Literal.String.Symbol\n    .bp    { color: #999 } // Name.Builtin.Pseudo\n    .vc    { color: #008080 } // Name.Variable.Class\n    .vg    { color: #008080 } // Name.Variable.Global\n    .vi    { color: #008080 } // Name.Variable.Instance\n    .il    { color: #099 } // Literal.Number.Integer.Long\n}\n"],"file":"styles_feeling_responsive.css"}
\ No newline at end of file
diff --git a/developer/cla/index.html b/developer/cla/index.html
index 02d438f9..a55b650f 100644
--- a/developer/cla/index.html
+++ b/developer/cla/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>CLA</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. A Contributor License Agreement (CLA) is an agreement between an open source project and someone working on that project. Here are some key points about the OED CLA: You agree to give the OED project unlimited and free use of any work you submit. This guarantees that OED will remain free and someone cannot later decide to revoke permission which can cause serious issues for the project. You retain the copyright and are allowed to use your work in any way you wish. You are giving us your work &quot;as-is&quot;. You are not under any obligation to give support for what you provide. Your agreeing to the CLA is under the terms of the Mozilla Public License (MPL). The OED project guarantees that all its work will remain under the MPL so you are assured that your contributions will always be free and open source under the MPL terms. The wording of this CLA is consistent and similar to other CLA agreements and not something unique to the OED project. Please visit the OED CLA to review what it says and agree to its terms before you make a contribution to the project. Thanks!"><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/cla/"><meta property="og:title" content="CLA"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. A Contributor License Agreement (CLA) is an agreement between an open source project and someone working on that project. Here are some key points about the OED CLA: You agree to give the OED project unlimited and free use of any work you submit. This guarantees that OED will remain free and someone cannot later decide to revoke permission which can cause serious issues for the project. You retain the copyright and are allowed to use your work in any way you wish. You are giving us your work &quot;as-is&quot;. You are not under any obligation to give support for what you provide. Your agreeing to the CLA is under the terms of the Mozilla Public License (MPL). The OED project guarantees that all its work will remain under the MPL so you are assured that your contributions will always be free and open source under the MPL terms. The wording of this CLA is consistent and similar to other CLA agreements and not something unique to the OED project. Please visit the OED CLA to review what it says and agree to its terms before you make a contribution to the project. Thanks!"><meta property="og:url" content="https://openenergydashboard.org/developer/cla/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Contributor License Agreement</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Contributor License Agreement</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>A Contributor License Agreement (CLA) is an agreement between an open source project and someone working on that project. Here are some key points about the OED CLA:<ul><li>You agree to give the OED project unlimited and free use of any work you submit. This guarantees that OED will remain free and someone cannot later decide to revoke permission which can cause serious issues for the project.<li>You retain the copyright and are allowed to use your work in any way you wish.<li>You are giving us your work "as-is". You are not under any obligation to give support for what you provide.<li>Your agreeing to the CLA is under the terms of the Mozilla Public License (MPL). The OED project guarantees that all its work will remain under the MPL so you are assured that your contributions will always be free and open source under the MPL terms.<li>The wording of this CLA is consistent and similar to other CLA agreements and not something unique to the OED project.</ul><p>Please visit the <a href="https://docs.google.com/forms/d/e/1FAIpQLSc2zdF2PqJ14FljfQIyQn_X70xDhnpv-zCda1wU0xIOQ5mp_w/viewform" target="_blank">OED CLA</a> to review what it says and agree to its terms before you make a contribution to the project. Thanks!</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>CLA</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. A Contributor License Agreement (CLA) is an agreement between an open source project and someone working on that project. Here are some key points about the OED CLA: You agree to give the OED project unlimited and free use of any work you submit. This guarantees that OED will remain free and someone cannot later decide to revoke permission which can cause serious issues for the project. You retain the copyright and are allowed to use your work in any way you wish. You are giving us your work &quot;as-is&quot;. You are not under any obligation to give support for what you provide. Your agreeing to the CLA is under the terms of the Mozilla Public License (MPL). The OED project guarantees that all its work will remain under the MPL so you are assured that your contributions will always be free and open source under the MPL terms. The wording of this CLA is consistent and similar to other CLA agreements and not something unique to the OED project. Please visit the OED CLA to review what it says and agree to its terms before you make a contribution to the project. Thanks!"><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/cla/"><meta property="og:title" content="CLA"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. A Contributor License Agreement (CLA) is an agreement between an open source project and someone working on that project. Here are some key points about the OED CLA: You agree to give the OED project unlimited and free use of any work you submit. This guarantees that OED will remain free and someone cannot later decide to revoke permission which can cause serious issues for the project. You retain the copyright and are allowed to use your work in any way you wish. You are giving us your work &quot;as-is&quot;. You are not under any obligation to give support for what you provide. Your agreeing to the CLA is under the terms of the Mozilla Public License (MPL). The OED project guarantees that all its work will remain under the MPL so you are assured that your contributions will always be free and open source under the MPL terms. The wording of this CLA is consistent and similar to other CLA agreements and not something unique to the OED project. Please visit the OED CLA to review what it says and agree to its terms before you make a contribution to the project. Thanks!"><meta property="og:url" content="https://openenergydashboard.org/developer/cla/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Contributor License Agreement</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Contributor License Agreement</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>A Contributor License Agreement (CLA) is an agreement between an open source project and someone working on that project. Here are some key points about the OED CLA:<ul><li>You agree to give the OED project unlimited and free use of any work you submit. This guarantees that OED will remain free and someone cannot later decide to revoke permission which can cause serious issues for the project.<li>You retain the copyright and are allowed to use your work in any way you wish.<li>You are giving us your work "as-is". You are not under any obligation to give support for what you provide.<li>Your agreeing to the CLA is under the terms of the Mozilla Public License (MPL). The OED project guarantees that all its work will remain under the MPL so you are assured that your contributions will always be free and open source under the MPL terms.<li>The wording of this CLA is consistent and similar to other CLA agreements and not something unique to the OED project.</ul><p>Please visit the <a href="https://docs.google.com/forms/d/e/1FAIpQLSc2zdF2PqJ14FljfQIyQn_X70xDhnpv-zCda1wU0xIOQ5mp_w/viewform" target="_blank">OED CLA</a> to review what it says and agree to its terms before you make a contribution to the project. Thanks!</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/codeGuidelines/index.html b/developer/codeGuidelines/index.html
index a554e877..a6f6db2d 100644
--- a/developer/codeGuidelines/index.html
+++ b/developer/codeGuidelines/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Documentation Expectations</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Documentation We appreciate documentation contributions, especially if they follow the common format. We acknowledge that these suggestions are far from complete and welcome input from developers. Each file should begin with a short summary of its contents; for instance: /* This file contains the React component which lists and allows * selections of pairs of {id, name}, e.g. for groups and meters * in the chart UI. */ Every function should have JSDoc comments, beginning with /**, which should include the @param and @return tags to describe parameters and functions. In TypeScript code, it&#39;s unnecessary to declare types for @param tags. /** * Converts pairs of timestamps into an array of TimeIntervals. * @param tspairs {[[number, number]]} the pairs of timestamps to be processed * @returns {[TimeInterval]} */ function tspairsToTimeIntervals(tspairs) { Do your best to use full English sentences. For example, the following could be rewritten: /** * Middleware function to force authentication * Requires a route to have a valid token or 401 */ async function authenticate(req, res, next) { as the more readable: /** * This middleware function forces requests to provide a valid * token. Requests without a valid token will reject with a 401. */ async function authenticate(req, res, next) { OED prefers comments on the line preceding (above) the line of code. Placing comments at the end of lines makes the line longer and that can lead to formatting issues, esp. if more code is added later. Thus, OED wants: // Stores the number of items let numItems; rather than: let numItems; // Stores the number of items Imports To keep consistency, OED desires to list imports in a standard way. Since the majority of developers use Visual Studio Code, OED uses the organize imports command in VSC to order the imports."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/codeGuidelines/"><meta property="og:title" content="Documentation Expectations"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Documentation We appreciate documentation contributions, especially if they follow the common format. We acknowledge that these suggestions are far from complete and welcome input from developers. Each file should begin with a short summary of its contents; for instance: /* This file contains the React component which lists and allows * selections of pairs of {id, name}, e.g. for groups and meters * in the chart UI. */ Every function should have JSDoc comments, beginning with /**, which should include the @param and @return tags to describe parameters and functions. In TypeScript code, it&#39;s unnecessary to declare types for @param tags. /** * Converts pairs of timestamps into an array of TimeIntervals. * @param tspairs {[[number, number]]} the pairs of timestamps to be processed * @returns {[TimeInterval]} */ function tspairsToTimeIntervals(tspairs) { Do your best to use full English sentences. For example, the following could be rewritten: /** * Middleware function to force authentication * Requires a route to have a valid token or 401 */ async function authenticate(req, res, next) { as the more readable: /** * This middleware function forces requests to provide a valid * token. Requests without a valid token will reject with a 401. */ async function authenticate(req, res, next) { OED prefers comments on the line preceding (above) the line of code. Placing comments at the end of lines makes the line longer and that can lead to formatting issues, esp. if more code is added later. Thus, OED wants: // Stores the number of items let numItems; rather than: let numItems; // Stores the number of items Imports To keep consistency, OED desires to list imports in a standard way. Since the majority of developers use Visual Studio Code, OED uses the organize imports command in VSC to order the imports."><meta property="og:url" content="https://openenergydashboard.org/developer/codeGuidelines/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Documentation Expectations</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Documentation Expectations</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><h2>Documentation</h2><p>We appreciate documentation contributions, especially if they follow the common format. We acknowledge that these suggestions are far from complete and welcome input from developers.<p>Each file should begin with a short summary of its contents; for instance:<pre>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Documentation Expectations</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Documentation We appreciate documentation contributions, especially if they follow the common format. We acknowledge that these suggestions are far from complete and welcome input from developers. Each file should begin with a short summary of its contents; for instance: /* This file contains the React component which lists and allows * selections of pairs of {id, name}, e.g. for groups and meters * in the chart UI. */ Every function should have JSDoc comments, beginning with /**, which should include the @param and @return tags to describe parameters and functions. In TypeScript code, it&#39;s unnecessary to declare types for @param tags. /** * Converts pairs of timestamps into an array of TimeIntervals. * @param tspairs {[[number, number]]} the pairs of timestamps to be processed * @returns {[TimeInterval]} */ function tspairsToTimeIntervals(tspairs) { Do your best to use full English sentences. For example, the following could be rewritten: /** * Middleware function to force authentication * Requires a route to have a valid token or 401 */ async function authenticate(req, res, next) { as the more readable: /** * This middleware function forces requests to provide a valid * token. Requests without a valid token will reject with a 401. */ async function authenticate(req, res, next) { OED prefers comments on the line preceding (above) the line of code. Placing comments at the end of lines makes the line longer and that can lead to formatting issues, esp. if more code is added later. Thus, OED wants: // Stores the number of items let numItems; rather than: let numItems; // Stores the number of items Imports To keep consistency, OED desires to list imports in a standard way. Since the majority of developers use Visual Studio Code, OED uses the organize imports command in VSC to order the imports."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/codeGuidelines/"><meta property="og:title" content="Documentation Expectations"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Documentation We appreciate documentation contributions, especially if they follow the common format. We acknowledge that these suggestions are far from complete and welcome input from developers. Each file should begin with a short summary of its contents; for instance: /* This file contains the React component which lists and allows * selections of pairs of {id, name}, e.g. for groups and meters * in the chart UI. */ Every function should have JSDoc comments, beginning with /**, which should include the @param and @return tags to describe parameters and functions. In TypeScript code, it&#39;s unnecessary to declare types for @param tags. /** * Converts pairs of timestamps into an array of TimeIntervals. * @param tspairs {[[number, number]]} the pairs of timestamps to be processed * @returns {[TimeInterval]} */ function tspairsToTimeIntervals(tspairs) { Do your best to use full English sentences. For example, the following could be rewritten: /** * Middleware function to force authentication * Requires a route to have a valid token or 401 */ async function authenticate(req, res, next) { as the more readable: /** * This middleware function forces requests to provide a valid * token. Requests without a valid token will reject with a 401. */ async function authenticate(req, res, next) { OED prefers comments on the line preceding (above) the line of code. Placing comments at the end of lines makes the line longer and that can lead to formatting issues, esp. if more code is added later. Thus, OED wants: // Stores the number of items let numItems; rather than: let numItems; // Stores the number of items Imports To keep consistency, OED desires to list imports in a standard way. Since the majority of developers use Visual Studio Code, OED uses the organize imports command in VSC to order the imports."><meta property="og:url" content="https://openenergydashboard.org/developer/codeGuidelines/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Documentation Expectations</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Documentation Expectations</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><h2>Documentation</h2><p>We appreciate documentation contributions, especially if they follow the common format. We acknowledge that these suggestions are far from complete and welcome input from developers.<p>Each file should begin with a short summary of its contents; for instance:<pre>
 /* This file contains the React component which lists and allows 
  * selections of pairs of {id, name}, e.g. for groups and meters
  * in the chart UI. */
diff --git a/developer/codeOrganization/index.html b/developer/codeOrganization/index.html
index f408d887..fc00f80f 100644
--- a/developer/codeOrganization/index.html
+++ b/developer/codeOrganization/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Code Organization</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The OED code base is organized into directories. Understanding the structure of this layout can help in working on the code. The project is organized into a number of subdirectories. The primary division is among: Metadata, configs, and deployment information Frontend code Backend code Common code Other directories Metadata In the root directory, OED has several metadata files. These are further organized by technology or purpose. For Humans CODE_OF_CONDUCT describes conduct expectations and how to report any concerns. CONTRIBUTING.md provides information on contributing to OED. License.txt describes the legal aspect of the project. OED is licensed under the Mozilla Public License version 2.0. README.md is an overview of the project, displayed on the GitHub front page for the project. Security.md describes how to report security concerns to OED. Support.md describes where to get information on support related to OED. USAGE.md describes how to install, configure, and use the project from a sysadmin&#39;s point of view. For Development Tools .devcontainer/ has files to set up the Visual Studio Code container. .github/ ISSUE_TEMPLATE/ has GitHub issue template, workflows/ has two .yml files for GitHub Actions: one for CI and one for static and dependabot.yml controls GitHub automated pull requests. .vscode/ contains (currently nonworking) instructions to run OED within Visual Studio Code. .dockerignore defines files that Docker ignores. .editorconfig conveys some of our basic style rules to most common code editors. .eslintignore defines files to include in ESLint checking. .eslintrc.json defines the ESLint rules .gitattributes informs Git about how to properly show diffs for our files. .gitignore informs the Git Version Control System about files that it should not track. client.js does database setup for GitHub Action CI. tslint.json configures the TSLint code quality tool and style checker For Code Transformers babel.config.json configures the Babel JavaScript compiler webpack.config.js configures the WebPack JavaScript uglifier, optimizer, and packer For Dependency Management Tools .npmrc tells node package versions to allow on install docker-compose.yml specifies how to collect the database and web/vsc Docker containers together into a working deployment the containers/ directory contains everything needed to build the Docker containers with subdirectories for the database and web (along with proxy if needed). .dockerignore tells the Docker containerization engine which files to ignore package.json specifies direct dependencies and some package metadata package-lock.json specifies working direct and transitive dependencies used on the last build committed Frontend Code All frontend code is stored in src/client/app/. This is the code that actually runs in the user&#39;s web browser. See the technologies page for a diagram showing how this code is transpiled and minified prior to delivery. This code is contained in several directories: actions/ are the messages that components send to reducers to change the application state. components/ are the React.js components which generate HTML that is displayed on the page. Components can be combined and composed to create the UI that is displayed to the user. containers/ connect the React.js components to the application state (managed by Redux) through props and dispatched actions. reducers/ accept messages sent by components and change the global application state accordingly. style/ CSS files for the website. translations/ defines the strings used to make OED multilingual. types/ define the datatypes used throughout the frontend. utils/ defines functions used across the application and some APIs. Backend Code All backend code is stored in src/server/, except for the executable server, which is src/bin/www/. Beneath that, there are several folders: data/ functions to generate test data (not used directly by the application but for testing). middleware/ middleware for dealing with web requests. migrations/ contains SQL files that are used to upgrade between database versions. models/ contains classes which connect JavaScript code to the database so that routes can actually interact with data. routes/ contains functions defining the actual URLs that the server provides, which is how the frontend interacts with the server. services/ contains scripts used by developers and administrators to modify the data in ways that are inaccessible through the web interface. sql/ contains the database queries used by models to talk to the PostgreSQL database. test/ contains the test code run for validation of OED. utils/ contains utility functions and constants. Common Code All common code is stored in src/common/. This code defines data types which are in shared use between the client and the server. Scripts Scripts are stored in src/scripts/. The scripts are as follows: checkHeader.sh verifies that all source files have the MPLv2 legal header. It is run in CI. checkMeters.sh verifies if a file of IP addresses has meters that respond. Used for testing meters or before input of meters into OED. Mostly targets MAMAC meters that are web based. checkTypescript.sh verifies that there are no untyped JavaScript files in the client tree. It is run in CI. devcheck.sh runs all the checks (header, typescript, types and lint) in one easy step. devstart.sh starts both the webserver and Webpack, in dev mode (watches files and shows interactive). This isn not normally used to start OED for developers. installOED.sh sets up OED, either for development or production, creating the database schema and installing dependencies. This is often run using docker compose up or some variant of this. It should be automatically run inside toe VSC container. oed.service is a sample systemd unit file which allows Linux system administrators to start OED on startup. refreshReadingViewsCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates the daily view table that is needed to graph OED data. refreshDailyReadingViewsCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates the hourly view table that is needed to graph OED data. sendLogEmailCron.bash is a script meant to be run at regular intervals (for instance, with cron) which sends an email with information from OED logging since the last time this ran. updateEgaugeMetersOEDCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates eGauge-brand meters. updateMamacMetersOEDCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates Mamac-brand pull-type meters. updateOED.sh To be run after pulling the latest version from Git. Grabs new dependencies and migrates the database. Other directories One will see other directories in the OED code base after install and work with OED. These are not normally changed by someone. A few noticeable ones are: node_modules/ is created during the npm install process and contains information on all node packages used. postgres-data/ is created during the PostgreSQL install process and contains the information about the database and all records stored. It is the one set of files that exist between runs of the Docker container and are linked from the Docker container to the regular file system. This is done so that the database settings and records exist between runs."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/codeOrganization/"><meta property="og:title" content="Code Organization"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The OED code base is organized into directories. Understanding the structure of this layout can help in working on the code. The project is organized into a number of subdirectories. The primary division is among: Metadata, configs, and deployment information Frontend code Backend code Common code Other directories Metadata In the root directory, OED has several metadata files. These are further organized by technology or purpose. For Humans CODE_OF_CONDUCT describes conduct expectations and how to report any concerns. CONTRIBUTING.md provides information on contributing to OED. License.txt describes the legal aspect of the project. OED is licensed under the Mozilla Public License version 2.0. README.md is an overview of the project, displayed on the GitHub front page for the project. Security.md describes how to report security concerns to OED. Support.md describes where to get information on support related to OED. USAGE.md describes how to install, configure, and use the project from a sysadmin&#39;s point of view. For Development Tools .devcontainer/ has files to set up the Visual Studio Code container. .github/ ISSUE_TEMPLATE/ has GitHub issue template, workflows/ has two .yml files for GitHub Actions: one for CI and one for static and dependabot.yml controls GitHub automated pull requests. .vscode/ contains (currently nonworking) instructions to run OED within Visual Studio Code. .dockerignore defines files that Docker ignores. .editorconfig conveys some of our basic style rules to most common code editors. .eslintignore defines files to include in ESLint checking. .eslintrc.json defines the ESLint rules .gitattributes informs Git about how to properly show diffs for our files. .gitignore informs the Git Version Control System about files that it should not track. client.js does database setup for GitHub Action CI. tslint.json configures the TSLint code quality tool and style checker For Code Transformers babel.config.json configures the Babel JavaScript compiler webpack.config.js configures the WebPack JavaScript uglifier, optimizer, and packer For Dependency Management Tools .npmrc tells node package versions to allow on install docker-compose.yml specifies how to collect the database and web/vsc Docker containers together into a working deployment the containers/ directory contains everything needed to build the Docker containers with subdirectories for the database and web (along with proxy if needed). .dockerignore tells the Docker containerization engine which files to ignore package.json specifies direct dependencies and some package metadata package-lock.json specifies working direct and transitive dependencies used on the last build committed Frontend Code All frontend code is stored in src/client/app/. This is the code that actually runs in the user&#39;s web browser. See the technologies page for a diagram showing how this code is transpiled and minified prior to delivery. This code is contained in several directories: actions/ are the messages that components send to reducers to change the application state. components/ are the React.js components which generate HTML that is displayed on the page. Components can be combined and composed to create the UI that is displayed to the user. containers/ connect the React.js components to the application state (managed by Redux) through props and dispatched actions. reducers/ accept messages sent by components and change the global application state accordingly. style/ CSS files for the website. translations/ defines the strings used to make OED multilingual. types/ define the datatypes used throughout the frontend. utils/ defines functions used across the application and some APIs. Backend Code All backend code is stored in src/server/, except for the executable server, which is src/bin/www/. Beneath that, there are several folders: data/ functions to generate test data (not used directly by the application but for testing). middleware/ middleware for dealing with web requests. migrations/ contains SQL files that are used to upgrade between database versions. models/ contains classes which connect JavaScript code to the database so that routes can actually interact with data. routes/ contains functions defining the actual URLs that the server provides, which is how the frontend interacts with the server. services/ contains scripts used by developers and administrators to modify the data in ways that are inaccessible through the web interface. sql/ contains the database queries used by models to talk to the PostgreSQL database. test/ contains the test code run for validation of OED. utils/ contains utility functions and constants. Common Code All common code is stored in src/common/. This code defines data types which are in shared use between the client and the server. Scripts Scripts are stored in src/scripts/. The scripts are as follows: checkHeader.sh verifies that all source files have the MPLv2 legal header. It is run in CI. checkMeters.sh verifies if a file of IP addresses has meters that respond. Used for testing meters or before input of meters into OED. Mostly targets MAMAC meters that are web based. checkTypescript.sh verifies that there are no untyped JavaScript files in the client tree. It is run in CI. devcheck.sh runs all the checks (header, typescript, types and lint) in one easy step. devstart.sh starts both the webserver and Webpack, in dev mode (watches files and shows interactive). This isn not normally used to start OED for developers. installOED.sh sets up OED, either for development or production, creating the database schema and installing dependencies. This is often run using docker compose up or some variant of this. It should be automatically run inside toe VSC container. oed.service is a sample systemd unit file which allows Linux system administrators to start OED on startup. refreshReadingViewsCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates the daily view table that is needed to graph OED data. refreshDailyReadingViewsCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates the hourly view table that is needed to graph OED data. sendLogEmailCron.bash is a script meant to be run at regular intervals (for instance, with cron) which sends an email with information from OED logging since the last time this ran. updateEgaugeMetersOEDCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates eGauge-brand meters. updateMamacMetersOEDCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates Mamac-brand pull-type meters. updateOED.sh To be run after pulling the latest version from Git. Grabs new dependencies and migrates the database. Other directories One will see other directories in the OED code base after install and work with OED. These are not normally changed by someone. A few noticeable ones are: node_modules/ is created during the npm install process and contains information on all node packages used. postgres-data/ is created during the PostgreSQL install process and contains the information about the database and all records stored. It is the one set of files that exist between runs of the Docker container and are linked from the Docker container to the regular file system. This is done so that the database settings and records exist between runs."><meta property="og:url" content="https://openenergydashboard.org/developer/codeOrganization/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Code Organization</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Code Organization</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>The OED code base is organized into directories. Understanding the structure of this layout can help in working on the code.<p>The project is organized into a number of subdirectories. The primary division is among:<ul><li>Metadata, configs, and deployment information<li>Frontend code<li>Backend code<li>Common code<li>Other directories</ul><h2>Metadata</h2><p>In the root directory, OED has several metadata files. These are further organized by technology or purpose.<h3>For Humans</h3><ul><li><strong>CODE_OF_CONDUCT</strong> describes conduct expectations and how to report any concerns.<li> <strong>CONTRIBUTING.md</strong> provides information on contributing to OED.<li> <strong>License.txt</strong> describes the legal aspect of the project. OED is licensed under the <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">Mozilla Public License version 2.0</a>.<li> <strong>README.md</strong> is an overview of the project, displayed on the GitHub front page for the project.<li><strong>Security.md</strong> describes how to report security concerns to OED.<li><strong>Support.md</strong> describes where to get information on support related to OED.<li> <strong>USAGE.md</strong> describes how to install, configure, and use the project from a sysadmin's point of view.</ul><h3>For Development Tools</h3><ul><li><strong>.devcontainer/</strong> has files to set up the Visual Studio Code container.<li><strong>.github/</strong> ISSUE_TEMPLATE/ has GitHub issue template, workflows/ has two .yml files for GitHub Actions: one for CI and one for static and dependabot.yml controls GitHub automated pull requests.<li><strong>.vscode/</strong> contains (currently nonworking) instructions to run OED within Visual Studio Code.<li><strong>.dockerignore</strong> defines files that Docker ignores.<li> <strong>.editorconfig</strong> conveys some of our basic style rules to most common code editors.<li><strong>.eslintignore</strong> defines files to include in ESLint checking.<li><strong>.eslintrc.json</strong> defines the ESLint rules<li> <strong>.gitattributes</strong> informs Git about how to properly show diffs for our files.<li> <strong>.gitignore</strong> informs the Git Version Control System about files that it should not track.<li><strong>client.js</strong> does database setup for GitHub Action CI.<li> <strong>tslint.json</strong> configures the TSLint code quality tool and style checker</ul><h3>For Code Transformers</h3><ul><li> <strong>babel.config.json</strong> configures the Babel JavaScript compiler<li> <strong>webpack.config.js</strong> configures the WebPack JavaScript uglifier, optimizer, and packer</ul><h3>For Dependency Management Tools</h3><ul><li><strong>.npmrc</strong> tells node package versions to allow on install<li> <strong>docker-compose.yml</strong> specifies how to collect the database and web/vsc Docker containers together into a working deployment<li>the <strong>containers/</strong> directory contains everything needed to build the Docker containers with subdirectories for the database and web (along with proxy if needed).<li> <strong>.dockerignore</strong> tells the Docker containerization engine which files to ignore<li> <strong>package.json</strong> specifies direct dependencies and some package metadata<li> <strong>package-lock.json</strong> specifies working direct and transitive dependencies used on the last build committed</ul><h2>Frontend Code</h2><p>All frontend code is stored in <code>src/client/app/</code>. This is the code that actually runs in the user's web browser. See the <a href="../technologies/">technologies</a> page for a diagram showing how this code is transpiled and minified prior to delivery.<p>This code is contained in several directories:<ul><li> <strong>actions/</strong> are the messages that components send to reducers to change the application state.<li> <strong>components/</strong> are the React.js components which generate HTML that is displayed on the page. Components can be combined and composed to create the UI that is displayed to the user.<li> <strong>containers/</strong> connect the React.js components to the application state (managed by Redux) through props and dispatched actions.<li> <strong>reducers/</strong> accept messages sent by components and change the global application state accordingly.<li> <strong>style/</strong> CSS files for the website.<li> <strong>translations/</strong> defines the strings used to make OED multilingual.<li> <strong>types/</strong> define the datatypes used throughout the frontend.<li> <strong>utils/</strong> defines functions used across the application and some APIs.</ul><h2>Backend Code</h2><p>All backend code is stored in <code>src/server/</code>, except for the executable server, which is <code>src/bin/www/</code>.<p>Beneath that, there are several folders:<ul><li> <strong>data/</strong> functions to generate test data (not used directly by the application but for testing).<li> <strong>middleware/</strong> middleware for dealing with web requests.<li> <strong>migrations/</strong> contains SQL files that are used to upgrade between database versions.<li> <strong>models/</strong> contains classes which connect JavaScript code to the database so that routes can actually interact with data.<li> <strong>routes/</strong> contains functions defining the actual URLs that the server provides, which is how the frontend interacts with the server.<li> <strong>services/</strong> contains scripts used by developers and administrators to modify the data in ways that are inaccessible through the web interface.<li> <strong>sql/</strong> contains the database queries used by models to talk to the PostgreSQL database.<li> <strong>test/</strong> contains the test code run for validation of OED.<li> <strong>utils/</strong> contains utility functions and constants.</ul><h2>Common Code</h2><p>All common code is stored in <code>src/common/</code>. This code defines data types which are in shared use between the client and the server.<h2>Scripts</h2><p>Scripts are stored in <code>src/scripts/</code>.<p>The scripts are as follows:<ul><li> <strong>checkHeader.sh</strong> verifies that all source files have the MPLv2 legal header. It is run in CI.<li> <strong>checkMeters.sh</strong> verifies if a file of IP addresses has meters that respond. Used for testing meters or before input of meters into OED. Mostly targets MAMAC meters that are web based.<li> <strong>checkTypescript.sh</strong> verifies that there are no untyped JavaScript files in the client tree. It is run in CI.<li> <strong>devcheck.sh</strong> runs all the checks (header, typescript, types and lint) in one easy step.<li> <strong>devstart.sh</strong> starts both the webserver and Webpack, in dev mode (watches files and shows interactive). This isn not normally used to start OED for developers.<li> <strong>installOED.sh</strong> sets up OED, either for development or production, creating the database schema and installing dependencies. This is often run using <code>docker compose up</code> or some variant of this. It should be automatically run inside toe VSC container.<li> <strong>oed.service</strong> is a sample <a href="https://www.freedesktop.org/wiki/Software/systemd/" rel="nofollow">systemd</a> unit file which allows Linux system administrators to start OED on startup.<li> <strong>refreshReadingViewsCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which updates the daily view table that is needed to graph OED data.<li> <strong>refreshDailyReadingViewsCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which updates the hourly view table that is needed to graph OED data.<li> <strong>sendLogEmailCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which sends an email with information from OED logging since the last time this ran.<li> <strong>updateEgaugeMetersOEDCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which updates eGauge-brand meters.<li> <strong>updateMamacMetersOEDCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which updates Mamac-brand pull-type meters.<li> <strong>updateOED.sh</strong> To be run after pulling the latest version from Git. Grabs new dependencies and migrates the database.</ul><h2>Other directories</h2><p>One will see other directories in the OED code base after install and work with OED. These are not normally changed by someone. A few noticeable ones are:<ul><li><strong>node_modules/</strong> is created during the npm install process and contains information on all node packages used.<li><strong>postgres-data/</strong> is created during the PostgreSQL install process and contains the information about the database and all records stored. It is the one set of files that exist between runs of the Docker container and are linked from the Docker container to the regular file system. This is done so that the database settings and records exist between runs.</ul></div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Code Organization</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The OED code base is organized into directories. Understanding the structure of this layout can help in working on the code. The project is organized into a number of subdirectories. The primary division is among: Metadata, configs, and deployment information Frontend code Backend code Common code Other directories Metadata In the root directory, OED has several metadata files. These are further organized by technology or purpose. For Humans CODE_OF_CONDUCT describes conduct expectations and how to report any concerns. CONTRIBUTING.md provides information on contributing to OED. License.txt describes the legal aspect of the project. OED is licensed under the Mozilla Public License version 2.0. README.md is an overview of the project, displayed on the GitHub front page for the project. Security.md describes how to report security concerns to OED. Support.md describes where to get information on support related to OED. USAGE.md describes how to install, configure, and use the project from a sysadmin&#39;s point of view. For Development Tools .devcontainer/ has files to set up the Visual Studio Code container. .github/ ISSUE_TEMPLATE/ has GitHub issue template, workflows/ has two .yml files for GitHub Actions: one for CI and one for static and dependabot.yml controls GitHub automated pull requests. .vscode/ contains (currently nonworking) instructions to run OED within Visual Studio Code. .dockerignore defines files that Docker ignores. .editorconfig conveys some of our basic style rules to most common code editors. .eslintignore defines files to include in ESLint checking. .eslintrc.json defines the ESLint rules .gitattributes informs Git about how to properly show diffs for our files. .gitignore informs the Git Version Control System about files that it should not track. client.js does database setup for GitHub Action CI. tslint.json configures the TSLint code quality tool and style checker For Code Transformers babel.config.json configures the Babel JavaScript compiler webpack.config.js configures the WebPack JavaScript uglifier, optimizer, and packer For Dependency Management Tools .npmrc tells node package versions to allow on install docker-compose.yml specifies how to collect the database and web/vsc Docker containers together into a working deployment the containers/ directory contains everything needed to build the Docker containers with subdirectories for the database and web (along with proxy if needed). .dockerignore tells the Docker containerization engine which files to ignore package.json specifies direct dependencies and some package metadata package-lock.json specifies working direct and transitive dependencies used on the last build committed Frontend Code All frontend code is stored in src/client/app/. This is the code that actually runs in the user&#39;s web browser. See the technologies page for a diagram showing how this code is transpiled and minified prior to delivery. This code is contained in several directories: actions/ are the messages that components send to reducers to change the application state. components/ are the React.js components which generate HTML that is displayed on the page. Components can be combined and composed to create the UI that is displayed to the user. containers/ connect the React.js components to the application state (managed by Redux) through props and dispatched actions. reducers/ accept messages sent by components and change the global application state accordingly. style/ CSS files for the website. translations/ defines the strings used to make OED multilingual. types/ define the datatypes used throughout the frontend. utils/ defines functions used across the application and some APIs. Backend Code All backend code is stored in src/server/, except for the executable server, which is src/bin/www/. Beneath that, there are several folders: data/ functions to generate test data (not used directly by the application but for testing). middleware/ middleware for dealing with web requests. migrations/ contains SQL files that are used to upgrade between database versions. models/ contains classes which connect JavaScript code to the database so that routes can actually interact with data. routes/ contains functions defining the actual URLs that the server provides, which is how the frontend interacts with the server. services/ contains scripts used by developers and administrators to modify the data in ways that are inaccessible through the web interface. sql/ contains the database queries used by models to talk to the PostgreSQL database. test/ contains the test code run for validation of OED. utils/ contains utility functions and constants. Common Code All common code is stored in src/common/. This code defines data types which are in shared use between the client and the server. Scripts Scripts are stored in src/scripts/. The scripts are as follows: checkHeader.sh verifies that all source files have the MPLv2 legal header. It is run in CI. checkMeters.sh verifies if a file of IP addresses has meters that respond. Used for testing meters or before input of meters into OED. Mostly targets MAMAC meters that are web based. checkTypescript.sh verifies that there are no untyped JavaScript files in the client tree. It is run in CI. devcheck.sh runs all the checks (header, typescript, types and lint) in one easy step. devstart.sh starts both the webserver and Webpack, in dev mode (watches files and shows interactive). This isn not normally used to start OED for developers. installOED.sh sets up OED, either for development or production, creating the database schema and installing dependencies. This is often run using docker compose up or some variant of this. It should be automatically run inside toe VSC container. oed.service is a sample systemd unit file which allows Linux system administrators to start OED on startup. refreshReadingViewsCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates the daily view table that is needed to graph OED data. refreshDailyReadingViewsCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates the hourly view table that is needed to graph OED data. sendLogEmailCron.bash is a script meant to be run at regular intervals (for instance, with cron) which sends an email with information from OED logging since the last time this ran. updateEgaugeMetersOEDCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates eGauge-brand meters. updateMamacMetersOEDCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates Mamac-brand pull-type meters. updateOED.sh To be run after pulling the latest version from Git. Grabs new dependencies and migrates the database. Other directories One will see other directories in the OED code base after install and work with OED. These are not normally changed by someone. A few noticeable ones are: node_modules/ is created during the npm install process and contains information on all node packages used. postgres-data/ is created during the PostgreSQL install process and contains the information about the database and all records stored. It is the one set of files that exist between runs of the Docker container and are linked from the Docker container to the regular file system. This is done so that the database settings and records exist between runs."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/codeOrganization/"><meta property="og:title" content="Code Organization"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The OED code base is organized into directories. Understanding the structure of this layout can help in working on the code. The project is organized into a number of subdirectories. The primary division is among: Metadata, configs, and deployment information Frontend code Backend code Common code Other directories Metadata In the root directory, OED has several metadata files. These are further organized by technology or purpose. For Humans CODE_OF_CONDUCT describes conduct expectations and how to report any concerns. CONTRIBUTING.md provides information on contributing to OED. License.txt describes the legal aspect of the project. OED is licensed under the Mozilla Public License version 2.0. README.md is an overview of the project, displayed on the GitHub front page for the project. Security.md describes how to report security concerns to OED. Support.md describes where to get information on support related to OED. USAGE.md describes how to install, configure, and use the project from a sysadmin&#39;s point of view. For Development Tools .devcontainer/ has files to set up the Visual Studio Code container. .github/ ISSUE_TEMPLATE/ has GitHub issue template, workflows/ has two .yml files for GitHub Actions: one for CI and one for static and dependabot.yml controls GitHub automated pull requests. .vscode/ contains (currently nonworking) instructions to run OED within Visual Studio Code. .dockerignore defines files that Docker ignores. .editorconfig conveys some of our basic style rules to most common code editors. .eslintignore defines files to include in ESLint checking. .eslintrc.json defines the ESLint rules .gitattributes informs Git about how to properly show diffs for our files. .gitignore informs the Git Version Control System about files that it should not track. client.js does database setup for GitHub Action CI. tslint.json configures the TSLint code quality tool and style checker For Code Transformers babel.config.json configures the Babel JavaScript compiler webpack.config.js configures the WebPack JavaScript uglifier, optimizer, and packer For Dependency Management Tools .npmrc tells node package versions to allow on install docker-compose.yml specifies how to collect the database and web/vsc Docker containers together into a working deployment the containers/ directory contains everything needed to build the Docker containers with subdirectories for the database and web (along with proxy if needed). .dockerignore tells the Docker containerization engine which files to ignore package.json specifies direct dependencies and some package metadata package-lock.json specifies working direct and transitive dependencies used on the last build committed Frontend Code All frontend code is stored in src/client/app/. This is the code that actually runs in the user&#39;s web browser. See the technologies page for a diagram showing how this code is transpiled and minified prior to delivery. This code is contained in several directories: actions/ are the messages that components send to reducers to change the application state. components/ are the React.js components which generate HTML that is displayed on the page. Components can be combined and composed to create the UI that is displayed to the user. containers/ connect the React.js components to the application state (managed by Redux) through props and dispatched actions. reducers/ accept messages sent by components and change the global application state accordingly. style/ CSS files for the website. translations/ defines the strings used to make OED multilingual. types/ define the datatypes used throughout the frontend. utils/ defines functions used across the application and some APIs. Backend Code All backend code is stored in src/server/, except for the executable server, which is src/bin/www/. Beneath that, there are several folders: data/ functions to generate test data (not used directly by the application but for testing). middleware/ middleware for dealing with web requests. migrations/ contains SQL files that are used to upgrade between database versions. models/ contains classes which connect JavaScript code to the database so that routes can actually interact with data. routes/ contains functions defining the actual URLs that the server provides, which is how the frontend interacts with the server. services/ contains scripts used by developers and administrators to modify the data in ways that are inaccessible through the web interface. sql/ contains the database queries used by models to talk to the PostgreSQL database. test/ contains the test code run for validation of OED. utils/ contains utility functions and constants. Common Code All common code is stored in src/common/. This code defines data types which are in shared use between the client and the server. Scripts Scripts are stored in src/scripts/. The scripts are as follows: checkHeader.sh verifies that all source files have the MPLv2 legal header. It is run in CI. checkMeters.sh verifies if a file of IP addresses has meters that respond. Used for testing meters or before input of meters into OED. Mostly targets MAMAC meters that are web based. checkTypescript.sh verifies that there are no untyped JavaScript files in the client tree. It is run in CI. devcheck.sh runs all the checks (header, typescript, types and lint) in one easy step. devstart.sh starts both the webserver and Webpack, in dev mode (watches files and shows interactive). This isn not normally used to start OED for developers. installOED.sh sets up OED, either for development or production, creating the database schema and installing dependencies. This is often run using docker compose up or some variant of this. It should be automatically run inside toe VSC container. oed.service is a sample systemd unit file which allows Linux system administrators to start OED on startup. refreshReadingViewsCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates the daily view table that is needed to graph OED data. refreshDailyReadingViewsCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates the hourly view table that is needed to graph OED data. sendLogEmailCron.bash is a script meant to be run at regular intervals (for instance, with cron) which sends an email with information from OED logging since the last time this ran. updateEgaugeMetersOEDCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates eGauge-brand meters. updateMamacMetersOEDCron.bash is a script meant to be run at regular intervals (for instance, with cron) which updates Mamac-brand pull-type meters. updateOED.sh To be run after pulling the latest version from Git. Grabs new dependencies and migrates the database. Other directories One will see other directories in the OED code base after install and work with OED. These are not normally changed by someone. A few noticeable ones are: node_modules/ is created during the npm install process and contains information on all node packages used. postgres-data/ is created during the PostgreSQL install process and contains the information about the database and all records stored. It is the one set of files that exist between runs of the Docker container and are linked from the Docker container to the regular file system. This is done so that the database settings and records exist between runs."><meta property="og:url" content="https://openenergydashboard.org/developer/codeOrganization/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Code Organization</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Code Organization</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>The OED code base is organized into directories. Understanding the structure of this layout can help in working on the code.<p>The project is organized into a number of subdirectories. The primary division is among:<ul><li>Metadata, configs, and deployment information<li>Frontend code<li>Backend code<li>Common code<li>Other directories</ul><h2>Metadata</h2><p>In the root directory, OED has several metadata files. These are further organized by technology or purpose.<h3>For Humans</h3><ul><li><strong>CODE_OF_CONDUCT</strong> describes conduct expectations and how to report any concerns.<li> <strong>CONTRIBUTING.md</strong> provides information on contributing to OED.<li> <strong>License.txt</strong> describes the legal aspect of the project. OED is licensed under the <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">Mozilla Public License version 2.0</a>.<li> <strong>README.md</strong> is an overview of the project, displayed on the GitHub front page for the project.<li><strong>Security.md</strong> describes how to report security concerns to OED.<li><strong>Support.md</strong> describes where to get information on support related to OED.<li> <strong>USAGE.md</strong> describes how to install, configure, and use the project from a sysadmin's point of view.</ul><h3>For Development Tools</h3><ul><li><strong>.devcontainer/</strong> has files to set up the Visual Studio Code container.<li><strong>.github/</strong> ISSUE_TEMPLATE/ has GitHub issue template, workflows/ has two .yml files for GitHub Actions: one for CI and one for static and dependabot.yml controls GitHub automated pull requests.<li><strong>.vscode/</strong> contains (currently nonworking) instructions to run OED within Visual Studio Code.<li><strong>.dockerignore</strong> defines files that Docker ignores.<li> <strong>.editorconfig</strong> conveys some of our basic style rules to most common code editors.<li><strong>.eslintignore</strong> defines files to include in ESLint checking.<li><strong>.eslintrc.json</strong> defines the ESLint rules<li> <strong>.gitattributes</strong> informs Git about how to properly show diffs for our files.<li> <strong>.gitignore</strong> informs the Git Version Control System about files that it should not track.<li><strong>client.js</strong> does database setup for GitHub Action CI.<li> <strong>tslint.json</strong> configures the TSLint code quality tool and style checker</ul><h3>For Code Transformers</h3><ul><li> <strong>babel.config.json</strong> configures the Babel JavaScript compiler<li> <strong>webpack.config.js</strong> configures the WebPack JavaScript uglifier, optimizer, and packer</ul><h3>For Dependency Management Tools</h3><ul><li><strong>.npmrc</strong> tells node package versions to allow on install<li> <strong>docker-compose.yml</strong> specifies how to collect the database and web/vsc Docker containers together into a working deployment<li>the <strong>containers/</strong> directory contains everything needed to build the Docker containers with subdirectories for the database and web (along with proxy if needed).<li> <strong>.dockerignore</strong> tells the Docker containerization engine which files to ignore<li> <strong>package.json</strong> specifies direct dependencies and some package metadata<li> <strong>package-lock.json</strong> specifies working direct and transitive dependencies used on the last build committed</ul><h2>Frontend Code</h2><p>All frontend code is stored in <code>src/client/app/</code>. This is the code that actually runs in the user's web browser. See the <a href="../technologies/">technologies</a> page for a diagram showing how this code is transpiled and minified prior to delivery.<p>This code is contained in several directories:<ul><li> <strong>actions/</strong> are the messages that components send to reducers to change the application state.<li> <strong>components/</strong> are the React.js components which generate HTML that is displayed on the page. Components can be combined and composed to create the UI that is displayed to the user.<li> <strong>containers/</strong> connect the React.js components to the application state (managed by Redux) through props and dispatched actions.<li> <strong>reducers/</strong> accept messages sent by components and change the global application state accordingly.<li> <strong>style/</strong> CSS files for the website.<li> <strong>translations/</strong> defines the strings used to make OED multilingual.<li> <strong>types/</strong> define the datatypes used throughout the frontend.<li> <strong>utils/</strong> defines functions used across the application and some APIs.</ul><h2>Backend Code</h2><p>All backend code is stored in <code>src/server/</code>, except for the executable server, which is <code>src/bin/www/</code>.<p>Beneath that, there are several folders:<ul><li> <strong>data/</strong> functions to generate test data (not used directly by the application but for testing).<li> <strong>middleware/</strong> middleware for dealing with web requests.<li> <strong>migrations/</strong> contains SQL files that are used to upgrade between database versions.<li> <strong>models/</strong> contains classes which connect JavaScript code to the database so that routes can actually interact with data.<li> <strong>routes/</strong> contains functions defining the actual URLs that the server provides, which is how the frontend interacts with the server.<li> <strong>services/</strong> contains scripts used by developers and administrators to modify the data in ways that are inaccessible through the web interface.<li> <strong>sql/</strong> contains the database queries used by models to talk to the PostgreSQL database.<li> <strong>test/</strong> contains the test code run for validation of OED.<li> <strong>utils/</strong> contains utility functions and constants.</ul><h2>Common Code</h2><p>All common code is stored in <code>src/common/</code>. This code defines data types which are in shared use between the client and the server.<h2>Scripts</h2><p>Scripts are stored in <code>src/scripts/</code>.<p>The scripts are as follows:<ul><li> <strong>checkHeader.sh</strong> verifies that all source files have the MPLv2 legal header. It is run in CI.<li> <strong>checkMeters.sh</strong> verifies if a file of IP addresses has meters that respond. Used for testing meters or before input of meters into OED. Mostly targets MAMAC meters that are web based.<li> <strong>checkTypescript.sh</strong> verifies that there are no untyped JavaScript files in the client tree. It is run in CI.<li> <strong>devcheck.sh</strong> runs all the checks (header, typescript, types and lint) in one easy step.<li> <strong>devstart.sh</strong> starts both the webserver and Webpack, in dev mode (watches files and shows interactive). This isn not normally used to start OED for developers.<li> <strong>installOED.sh</strong> sets up OED, either for development or production, creating the database schema and installing dependencies. This is often run using <code>docker compose up</code> or some variant of this. It should be automatically run inside toe VSC container.<li> <strong>oed.service</strong> is a sample <a href="https://www.freedesktop.org/wiki/Software/systemd/" rel="nofollow">systemd</a> unit file which allows Linux system administrators to start OED on startup.<li> <strong>refreshReadingViewsCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which updates the daily view table that is needed to graph OED data.<li> <strong>refreshDailyReadingViewsCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which updates the hourly view table that is needed to graph OED data.<li> <strong>sendLogEmailCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which sends an email with information from OED logging since the last time this ran.<li> <strong>updateEgaugeMetersOEDCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which updates eGauge-brand meters.<li> <strong>updateMamacMetersOEDCron.bash</strong> is a script meant to be run at regular intervals (for instance, with cron) which updates Mamac-brand pull-type meters.<li> <strong>updateOED.sh</strong> To be run after pulling the latest version from Git. Grabs new dependencies and migrates the database.</ul><h2>Other directories</h2><p>One will see other directories in the OED code base after install and work with OED. These are not normally changed by someone. A few noticeable ones are:<ul><li><strong>node_modules/</strong> is created during the npm install process and contains information on all node packages used.<li><strong>postgres-data/</strong> is created during the PostgreSQL install process and contains the information about the database and all records stored. It is the one set of files that exist between runs of the Docker container and are linked from the Docker container to the regular file system. This is done so that the database settings and records exist between runs.</ul></div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/devDetails/index.html b/developer/devDetails/index.html
index 05690256..17d9768c 100644
--- a/developer/devDetails/index.html
+++ b/developer/devDetails/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Developer Details</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. There are many details and good ideas to use as an OED developer. This page tries to give you some of them. The topics covered are: Stopping OED Seeing what is happening with OED Getting a running OED to recognize code changes Accessing the database Rapid testing of a one or a few test(s) Resetting the Postgres database OED environment variables OED Scripts Migrating OED Having multiple versions of OED Rebuild after Docker dependency changes Running without the database container TypeScript Wisdom Database timeout on testing check permission error (historical) Faster OED installation (historical) Stopping OED If you are running in a VSC container, then you can simply click the green icon for the Remote Container and select &quot;Close Remote Container&quot;. You can also shut the container down manually (by right clicking and choosing &quot;stop&quot;) but that is normally only done if something went wrong in shutting down the container in the usual way. If you are running OED outside of Visual Studio Code then go to the terminal where OED is running, you can type ^-c (control and letter c) together to stop OED. Note it is best to only do this once since a second time causes a force stop. An alternative is to use docker compose down in a second terminal that is in the same directory as where the install is happening. This can also be useful if you are having an issue with your docker container(s) since it cleans them all up. Normally, doing ^-z will put the process into the background. This does not work with a running OED. Seeing what is happening with OED Sometimes OED will not act as you expect and you want to know what is going on. There are two normal ways to do this: The &quot;nohup.out&quot; file in the main OED directory shows all the logged messages. (If running OED outside Visual Studio Code then it is in the terminal where you started OED.) It is a good idea to be able to see this while you are running a version you are developing so you can tell when something significant happens. The messages can be informational where these are normal and not an indication of a problem. Any server side console.log output will be here. Any console.log output on the client side will show up in the web browser console. OED has the log file &quot;log.txt&quot; in the main OED directory. All logged messages and errors should be placed in this file. The newest messages are at the end. This file can get large over time so you probably want to focus on lines in the time frame you are interested (they should be timestamped). Using the Redux debugging tools in the web browser is also very valuable. It can also help to look at the traces. To do this you must enable it in the code. Go to src/client/app/index.tsx and do what the comments say to enable traces (comment out one line and uncomment two lines below). Please make sure you do not commit this change/include in a pull request. As the comments indicate, it would be nice to automate this process and maybe a developer will do this work and submit a PR. Getting a running OED to recognize code changes As a developer, you are often changing the code to see what impact it has on a running version of OED. In general, the system should recognize these changes and update the running version. If you change code under the client/ directory, the output will include a rebuild of the code. When that happens, the output will show this line if it worked. This will be in the terminal where OED is running or in nohup.out if you are working inside VSC. oed-web-1 | webpack 5.62.0 compiled successfully in 24100 ms If it fails then you will see one or more failure lines (with failure in red) rather than success. It will also show that it is done rebuilding when you see the line: oed-web-1 | \ [webpack.Progress] 100% It is not safe to reload the new version in the web browser until the rebuild finishes. You must reload to see the new code. If you change code on the server side, you will not see a rebuild but after a few lines of output you will see: oed-web-1 | [INFO@2022-04-24T16:31:17.449Z] Listening on port 3000 and then you can see the changes. Since all these changes are on the server, you do not need to reload the web browser. Normally the output is seen quickly but it can take a little while for webpack to detect the changes. If it ever fails to do this you could shut down OED and restart it but it is generally much easier/faster to go into some file, add a space, remove the space and save the file. This change (that really does nothing) should cause webpack to start the rebuild. In several cases, developers on Windows have reported not having the code rebuild on save. It turned out that the code was not on the WSL/Linux partition (generally under /home). As described in WSL on Windows, it is important to do this properly. Accessing the database There are two ways to access the Postgres database that OED uses. Through the docker container or through pgAdmin To access the database from the docker database container (see info on accessing containers), execute the following command: psql -U oed. You will now be in the Postgres command line for the OED database. It is assumed that you know some SQL and Postgres command line controls if you use this method. One important one is \q which will get you back to the terminal by leaving the Postgres command system. You can also use the pgAdmin utility to access the database. For this method, you need to install pgAdmin on your device. The link to get the latest version is here. Once you have downloaded and installed the correct version for your operating system, you need to enable the port for the connection to pgAdmin. This can be done by going to the docker-compose.yml file in the main OED directory and uncommenting the lines ports: and -&quot;5432&quot;:&quot;5432&quot;. Note you must shut down and restart OED for this to take effect. You should now be able to open pgAdmin and access the database on localhost port 5432 by adding a New Server with these properties: General tab: Name: oed (or whatever desired) Connection tab: Host name/address: localhost Post: 5432 (should be default) Username: oed password: opened (unless changed in docker-compoe.yml) Save password?: enable if desired to log in again without password A screenshot of the setup: When Save, it will verify connection and then open up connection if all is correct. Note that no matter how you access the OED database it is the live system so you can make changes that the running application will see (and damage the information too!). There may be times you want to backup/restore the Postgres data for OED. You can do it by Take a database dump (in the database Docker container terminal) with pg_dump -U oed &amp;gt; dump_$(date +%Y-%m-%d&quot;_&quot;%H_%M_%S.sql) Restore a database dump by first copying the dump into the container with docker cp /path/to/dump.sql container_name:/dump.sql and then restoring it into the database with psql -U oed -f /dump.sql. The /path/to/dump.sql is the file with date &amp; time created in the dump step. TODO Note someone should test/see if you really need to put it into the container first and this has not been tested since we went to working in the database container. Rapid testing of a one or a few test(s) When you make changes to OED or develop new tests, it may be the case that only one or a few tests fail when you run testing (or you want to focus on one test at a time that fails). Running all the tests is much slower than running a single test file. Thus, to run a single test, in the web/vsc docker container (see info on accessing container) do: npm run testsome &amp;lt;first test&amp;gt; [&amp;lt;second test&amp;gt;] where you replace &amp;lt; xxxx test&amp;gt; with the path to the test file you want to run and [ ] indicates this is optional and you can repeat as many times as you want for more tests. For example, to run the web groups test, you would use: npm run testsome src/server/test/web/groups.js and to run the web groups test and the db baselineTests use: npm run testsome src/server/test/web/groups.js src/server/test/db/baselineTests.js If you are using VSC you can easily get the path to any open test file. Right click on the file name in the tab for that editor window and choose &quot;Copy Relative Path&quot;. This can then be pasted into the needed command. Resetting the Postgres database During the initial install of OED, Postgres detects that you have not run before for this install and initializes the database system. It keeps the information in the postgres-data/ directory in the main OED directory. If you or a pull changes the database configuration, it will not automatically be changed on the next OED install. When we change versions of OED we use a migration system to upgrade the database but this may not be available during the development cycle. Given this, it is often easiest to force Postgres to reinitialize the database. Note that doing this will wipe out any data (meter, readings, preferences, etc.) that you have for this instance of OED. If you wish to force Postgres to reinitialize then do the following: Remove the postgres-data/ directory from the main OED directory. While you can move it to keep a copy, some OSes will still use the moved directory as if it exists in the main OED directory (at least until a reboot). Thus, it is probably best to delete the directory. Also note that OED should not be running when you do this as it will cause all kinds of problems when it does not find this directory. OED will automatically recreate the next time you bring it up. To delete this on Linux, you can do rm -rf postgres-data in the main OED directory. Note you may need to be root to remove this directory. If this is the case, use sudo rm -rf postgres-data where you will be prompted for the root password. It is sometimes tricky to know/login as root on a Windows WSL system. In this case, open the PowerShell, and enter the command wsl -u root that will put you in your WSL/Linus terminal as root. You can then directly delete the postgres-data/ directory. You should be very careful using this terminal as you can do damage as the root user. After you delete the postgres-data/ directory on Windows WSL, you will need to delete both OED containers (can do via the Docker Desktop or Docker extension in VSC). Doing a docker compose down in a terminal in the main OED directory will also accomplish this. Otherwise, you are likely to get the following error when you restart OED: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting &quot;/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2&quot; to rootfs at &quot;/var/lib/postgresql/data/pgdata&quot;: mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2:/var/lib/postgresql/data/pgdata (via /proc/self/fd/14), flags: 0x5000: no such file or directory: unknown Do an install of OED by reopening it in the VSC container or doing it outside of VSC. Remember if package changes were made then it will reinstall the node_modules. Note the install will take longer do to the extra initializations. Sometimes the first attempt at installation will fail when you do this. Try it one or two times more to see if it will work. (We are trying to determine why this happens.) If not, replace the postgres-data/ directory with the one removed and this should get you running but will not give you a new version of the database. If you have this issue then contact us for help (see link at bottom of page). OED runs in the containerized Docker environment. This means the software and files created are within this container and disappear when you stop running OED (shut the container down). The one exception to this rule is the information stored in the PostgreSQL database. Because this information needs to exist between OED runs to keep the database initialization and OED data, the information is kept within your OED installation in the postgres-data/ directory on your machine&#39;s file system. This is why removing the postgres-data/ directory resets the database within the Docker container. OED environment variables If you want to know about the environment variables that control OED then see the environment page. OED Scripts OED has a number of scripts that are run via commands in the package.json file. A complete listing with descriptions is on the NPM script page. Migrating OED The script src/scripts/updateOED.sh should update all dependencies and migrate the OED database if changes are needed. This may not work (see ideas above) if migrations are not yet available or this has been done before for the same version of OED. Having multiple versions of OED Most developers keep one clone of the OED software. They switch between branches as needed. However, if you are working on multiple versions of OED, esp. where the node modules are changing or the database configuration changes, then you can avoid having to do a full install (see above) by cloning separate copies of OED. When you install it will do the clone you are currently located in (the current directory in your terminal). The database information and all code is kept separate for each installation as part of the Docker containerization. Note you cannot run multiple version of OED simultaneously unless you change the ports it uses (this is not common). Rebuild after Docker dependency changes If a &quot;From&quot; in a Dockerfile is changed, then the version of that software needs to be updated. Docker normally uses its cached version so the update will not happen. To force the update, do: Inside VSC run the command rebuild container. Outside VSC in a terminal do docker compose up --build where you can add other arguments (such as keeping the node modules). This is unusual in that it is done in a terminal on your own machine in the main OED directory and not in an OED Docker container (because you are resetting the Docker containers). This should make Docker use what is specified in the Dockerfile. If there are no changes then it will not download a new version of the needed software but it will be a little slower for the checks and potentially creating the container. OED tries to announce to the Docker channel for developers whenever a change is make to a Dockerfile that would require this action. This is not commonly done. Running without the database container On rare occasions, you may get a database failure during the startup of the database container during the install/startup of OED. (This is not the transient issues noted during the install where the script reports it is continuing). Generally OED will tell you an issue happened in the console output and Docker indicates the database container is not running. In general, the underlying issue should be addressed so you have a correct OED installation. (This happened, for example, during Windows WSL installs until an file permission issue was resolved.) In rare circumstances, you still want to run the OED web container knowing that any operations that touch the database will fail. There is a parameter to the install script that allows this and can be done with: install_args=&quot;--continue_on_db_error&quot; docker compose up or the full install script (not using docker compose up) of docker compose run --service-ports --rm web npm run src/scripts/installOED.sh --continue_on_db_error OED will still try to install the DB, fail and then continue to try to install the web container. You should see the regular messages in the console indicating the web container is running as expected. If you are working inside VSC, you will need to edit the src/scripts/installOED.sh script to add the --continue_on_db_error parameter. TypeScript Wisdom TypeScript is great, but sometimes it requires some rather strange incantations, especially when working with external libraries. We cannot provide information on everything you need to know but here is one of interest: Regarding InjectedIntlProps from react-intl When using react-intl&#39;s higher order component functionality, some incantations are required. When defining a component, it&#39;s necessary to express that the component&#39;s props are actually (your props) ∪ (internationalization injector). This can be done via the &amp;amp; operator, as follows: interfaceSomeProps { prop1: number; } interfaceSomeState { state1: number; } class SomeComponent extends React.Component&amp;lt;SomeProps &amp;amp; InjectedIntlProps, SomeState&amp;gt; { constructor(props: SomeProps: &amp;amp; InjectedIntlProps) { super(props); // ... } // ... } export default injectIntl&amp;lt;SomeProps&amp;gt;(SomeComponent); If the union type is used often, it might be cleaner to create a type alias: type SomePropsWithIntl = SomeProps &amp;amp; InjectedIntlProps; Database timeout on testing Sometimes when you run the OED tests for the first time in a while, you get an error about the database timing out. The message is normally something similar to &quot;Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure &quot;done()&quot; is called; if returning a Promise, ensure it resolves.&quot; If this happens, rerun the test command. It normally works the next time (or within a total or three tries). We are working to change our testing and installation so Postgres is ready before operations continue so this problem will go away. The current fix is to allow a test to take up toe 15,000 ms or 15 seconds to complete so Postgres has time to start up and that is why you see &quot;15000ms&quot; in the error message. We have also set the timeout to be longer in a few tests where the issue was happening. If the problem persists, you can go into package.json and change the 15000 to be a larger value (such as 30000). This means mocha will not terminate a test until 30 seconds have passed. The only known negative of doing this is that a test that will not complete due to an error will take longer for mocha to terminate. However, this is uncommon in OED tests so the change should be fine. check permission error (historical) A few developers have reported that when they run docker compose run --rm web npm run check they get an error similar to &quot;Error: EACCES: permission denied, scandir &#39;/root/.npm/_logs&quot;. We do not believe this will happen any longer now that developers are asked to work within the Docker container. For the historical record the only know fix was to run outside of docker by doing npm run check. It is believed that this issue is due to doing installs as root and then not being root when inside docker but this is not certain. However, at least one developer found that changing the file permissions did not fix the issue. If anyone has this issue or finds a solution then please let us know. Faster OED installation (historical) The installation process was updated in late February 2022 so the node modules are not updated unless needed. This means the node modules will only be updated if the package.json and/or package-lock.json file is update whether by directed edit or from pulling updating versions. As a result, the old method of install_args=&quot;--keep_node_modules&quot; docker compose up should not be needed if you are running current versions of OED software. The keep_node_modules parameter was left for backward compatibility and in the unlikely case where a developer wishes to use it. As expected, the steps and output is different when there is no node module installation as seen in skipping NPM install output."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/devDetails/"><meta property="og:title" content="Developer Details"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. There are many details and good ideas to use as an OED developer. This page tries to give you some of them. The topics covered are: Stopping OED Seeing what is happening with OED Getting a running OED to recognize code changes Accessing the database Rapid testing of a one or a few test(s) Resetting the Postgres database OED environment variables OED Scripts Migrating OED Having multiple versions of OED Rebuild after Docker dependency changes Running without the database container TypeScript Wisdom Database timeout on testing check permission error (historical) Faster OED installation (historical) Stopping OED If you are running in a VSC container, then you can simply click the green icon for the Remote Container and select &quot;Close Remote Container&quot;. You can also shut the container down manually (by right clicking and choosing &quot;stop&quot;) but that is normally only done if something went wrong in shutting down the container in the usual way. If you are running OED outside of Visual Studio Code then go to the terminal where OED is running, you can type ^-c (control and letter c) together to stop OED. Note it is best to only do this once since a second time causes a force stop. An alternative is to use docker compose down in a second terminal that is in the same directory as where the install is happening. This can also be useful if you are having an issue with your docker container(s) since it cleans them all up. Normally, doing ^-z will put the process into the background. This does not work with a running OED. Seeing what is happening with OED Sometimes OED will not act as you expect and you want to know what is going on. There are two normal ways to do this: The &quot;nohup.out&quot; file in the main OED directory shows all the logged messages. (If running OED outside Visual Studio Code then it is in the terminal where you started OED.) It is a good idea to be able to see this while you are running a version you are developing so you can tell when something significant happens. The messages can be informational where these are normal and not an indication of a problem. Any server side console.log output will be here. Any console.log output on the client side will show up in the web browser console. OED has the log file &quot;log.txt&quot; in the main OED directory. All logged messages and errors should be placed in this file. The newest messages are at the end. This file can get large over time so you probably want to focus on lines in the time frame you are interested (they should be timestamped). Using the Redux debugging tools in the web browser is also very valuable. It can also help to look at the traces. To do this you must enable it in the code. Go to src/client/app/index.tsx and do what the comments say to enable traces (comment out one line and uncomment two lines below). Please make sure you do not commit this change/include in a pull request. As the comments indicate, it would be nice to automate this process and maybe a developer will do this work and submit a PR. Getting a running OED to recognize code changes As a developer, you are often changing the code to see what impact it has on a running version of OED. In general, the system should recognize these changes and update the running version. If you change code under the client/ directory, the output will include a rebuild of the code. When that happens, the output will show this line if it worked. This will be in the terminal where OED is running or in nohup.out if you are working inside VSC. oed-web-1 | webpack 5.62.0 compiled successfully in 24100 ms If it fails then you will see one or more failure lines (with failure in red) rather than success. It will also show that it is done rebuilding when you see the line: oed-web-1 | \ [webpack.Progress] 100% It is not safe to reload the new version in the web browser until the rebuild finishes. You must reload to see the new code. If you change code on the server side, you will not see a rebuild but after a few lines of output you will see: oed-web-1 | [INFO@2022-04-24T16:31:17.449Z] Listening on port 3000 and then you can see the changes. Since all these changes are on the server, you do not need to reload the web browser. Normally the output is seen quickly but it can take a little while for webpack to detect the changes. If it ever fails to do this you could shut down OED and restart it but it is generally much easier/faster to go into some file, add a space, remove the space and save the file. This change (that really does nothing) should cause webpack to start the rebuild. In several cases, developers on Windows have reported not having the code rebuild on save. It turned out that the code was not on the WSL/Linux partition (generally under /home). As described in WSL on Windows, it is important to do this properly. Accessing the database There are two ways to access the Postgres database that OED uses. Through the docker container or through pgAdmin To access the database from the docker database container (see info on accessing containers), execute the following command: psql -U oed. You will now be in the Postgres command line for the OED database. It is assumed that you know some SQL and Postgres command line controls if you use this method. One important one is \q which will get you back to the terminal by leaving the Postgres command system. You can also use the pgAdmin utility to access the database. For this method, you need to install pgAdmin on your device. The link to get the latest version is here. Once you have downloaded and installed the correct version for your operating system, you need to enable the port for the connection to pgAdmin. This can be done by going to the docker-compose.yml file in the main OED directory and uncommenting the lines ports: and -&quot;5432&quot;:&quot;5432&quot;. Note you must shut down and restart OED for this to take effect. You should now be able to open pgAdmin and access the database on localhost port 5432 by adding a New Server with these properties: General tab: Name: oed (or whatever desired) Connection tab: Host name/address: localhost Post: 5432 (should be default) Username: oed password: opened (unless changed in docker-compoe.yml) Save password?: enable if desired to log in again without password A screenshot of the setup: When Save, it will verify connection and then open up connection if all is correct. Note that no matter how you access the OED database it is the live system so you can make changes that the running application will see (and damage the information too!). There may be times you want to backup/restore the Postgres data for OED. You can do it by Take a database dump (in the database Docker container terminal) with pg_dump -U oed &amp;gt; dump_$(date +%Y-%m-%d&quot;_&quot;%H_%M_%S.sql) Restore a database dump by first copying the dump into the container with docker cp /path/to/dump.sql container_name:/dump.sql and then restoring it into the database with psql -U oed -f /dump.sql. The /path/to/dump.sql is the file with date &amp; time created in the dump step. TODO Note someone should test/see if you really need to put it into the container first and this has not been tested since we went to working in the database container. Rapid testing of a one or a few test(s) When you make changes to OED or develop new tests, it may be the case that only one or a few tests fail when you run testing (or you want to focus on one test at a time that fails). Running all the tests is much slower than running a single test file. Thus, to run a single test, in the web/vsc docker container (see info on accessing container) do: npm run testsome &amp;lt;first test&amp;gt; [&amp;lt;second test&amp;gt;] where you replace &amp;lt; xxxx test&amp;gt; with the path to the test file you want to run and [ ] indicates this is optional and you can repeat as many times as you want for more tests. For example, to run the web groups test, you would use: npm run testsome src/server/test/web/groups.js and to run the web groups test and the db baselineTests use: npm run testsome src/server/test/web/groups.js src/server/test/db/baselineTests.js If you are using VSC you can easily get the path to any open test file. Right click on the file name in the tab for that editor window and choose &quot;Copy Relative Path&quot;. This can then be pasted into the needed command. Resetting the Postgres database During the initial install of OED, Postgres detects that you have not run before for this install and initializes the database system. It keeps the information in the postgres-data/ directory in the main OED directory. If you or a pull changes the database configuration, it will not automatically be changed on the next OED install. When we change versions of OED we use a migration system to upgrade the database but this may not be available during the development cycle. Given this, it is often easiest to force Postgres to reinitialize the database. Note that doing this will wipe out any data (meter, readings, preferences, etc.) that you have for this instance of OED. If you wish to force Postgres to reinitialize then do the following: Remove the postgres-data/ directory from the main OED directory. While you can move it to keep a copy, some OSes will still use the moved directory as if it exists in the main OED directory (at least until a reboot). Thus, it is probably best to delete the directory. Also note that OED should not be running when you do this as it will cause all kinds of problems when it does not find this directory. OED will automatically recreate the next time you bring it up. To delete this on Linux, you can do rm -rf postgres-data in the main OED directory. Note you may need to be root to remove this directory. If this is the case, use sudo rm -rf postgres-data where you will be prompted for the root password. It is sometimes tricky to know/login as root on a Windows WSL system. In this case, open the PowerShell, and enter the command wsl -u root that will put you in your WSL/Linus terminal as root. You can then directly delete the postgres-data/ directory. You should be very careful using this terminal as you can do damage as the root user. After you delete the postgres-data/ directory on Windows WSL, you will need to delete both OED containers (can do via the Docker Desktop or Docker extension in VSC). Doing a docker compose down in a terminal in the main OED directory will also accomplish this. Otherwise, you are likely to get the following error when you restart OED: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting &quot;/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2&quot; to rootfs at &quot;/var/lib/postgresql/data/pgdata&quot;: mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2:/var/lib/postgresql/data/pgdata (via /proc/self/fd/14), flags: 0x5000: no such file or directory: unknown Do an install of OED by reopening it in the VSC container or doing it outside of VSC. Remember if package changes were made then it will reinstall the node_modules. Note the install will take longer do to the extra initializations. Sometimes the first attempt at installation will fail when you do this. Try it one or two times more to see if it will work. (We are trying to determine why this happens.) If not, replace the postgres-data/ directory with the one removed and this should get you running but will not give you a new version of the database. If you have this issue then contact us for help (see link at bottom of page). OED runs in the containerized Docker environment. This means the software and files created are within this container and disappear when you stop running OED (shut the container down). The one exception to this rule is the information stored in the PostgreSQL database. Because this information needs to exist between OED runs to keep the database initialization and OED data, the information is kept within your OED installation in the postgres-data/ directory on your machine&#39;s file system. This is why removing the postgres-data/ directory resets the database within the Docker container. OED environment variables If you want to know about the environment variables that control OED then see the environment page. OED Scripts OED has a number of scripts that are run via commands in the package.json file. A complete listing with descriptions is on the NPM script page. Migrating OED The script src/scripts/updateOED.sh should update all dependencies and migrate the OED database if changes are needed. This may not work (see ideas above) if migrations are not yet available or this has been done before for the same version of OED. Having multiple versions of OED Most developers keep one clone of the OED software. They switch between branches as needed. However, if you are working on multiple versions of OED, esp. where the node modules are changing or the database configuration changes, then you can avoid having to do a full install (see above) by cloning separate copies of OED. When you install it will do the clone you are currently located in (the current directory in your terminal). The database information and all code is kept separate for each installation as part of the Docker containerization. Note you cannot run multiple version of OED simultaneously unless you change the ports it uses (this is not common). Rebuild after Docker dependency changes If a &quot;From&quot; in a Dockerfile is changed, then the version of that software needs to be updated. Docker normally uses its cached version so the update will not happen. To force the update, do: Inside VSC run the command rebuild container. Outside VSC in a terminal do docker compose up --build where you can add other arguments (such as keeping the node modules). This is unusual in that it is done in a terminal on your own machine in the main OED directory and not in an OED Docker container (because you are resetting the Docker containers). This should make Docker use what is specified in the Dockerfile. If there are no changes then it will not download a new version of the needed software but it will be a little slower for the checks and potentially creating the container. OED tries to announce to the Docker channel for developers whenever a change is make to a Dockerfile that would require this action. This is not commonly done. Running without the database container On rare occasions, you may get a database failure during the startup of the database container during the install/startup of OED. (This is not the transient issues noted during the install where the script reports it is continuing). Generally OED will tell you an issue happened in the console output and Docker indicates the database container is not running. In general, the underlying issue should be addressed so you have a correct OED installation. (This happened, for example, during Windows WSL installs until an file permission issue was resolved.) In rare circumstances, you still want to run the OED web container knowing that any operations that touch the database will fail. There is a parameter to the install script that allows this and can be done with: install_args=&quot;--continue_on_db_error&quot; docker compose up or the full install script (not using docker compose up) of docker compose run --service-ports --rm web npm run src/scripts/installOED.sh --continue_on_db_error OED will still try to install the DB, fail and then continue to try to install the web container. You should see the regular messages in the console indicating the web container is running as expected. If you are working inside VSC, you will need to edit the src/scripts/installOED.sh script to add the --continue_on_db_error parameter. TypeScript Wisdom TypeScript is great, but sometimes it requires some rather strange incantations, especially when working with external libraries. We cannot provide information on everything you need to know but here is one of interest: Regarding InjectedIntlProps from react-intl When using react-intl&#39;s higher order component functionality, some incantations are required. When defining a component, it&#39;s necessary to express that the component&#39;s props are actually (your props) ∪ (internationalization injector). This can be done via the &amp;amp; operator, as follows: interfaceSomeProps { prop1: number; } interfaceSomeState { state1: number; } class SomeComponent extends React.Component&amp;lt;SomeProps &amp;amp; InjectedIntlProps, SomeState&amp;gt; { constructor(props: SomeProps: &amp;amp; InjectedIntlProps) { super(props); // ... } // ... } export default injectIntl&amp;lt;SomeProps&amp;gt;(SomeComponent); If the union type is used often, it might be cleaner to create a type alias: type SomePropsWithIntl = SomeProps &amp;amp; InjectedIntlProps; Database timeout on testing Sometimes when you run the OED tests for the first time in a while, you get an error about the database timing out. The message is normally something similar to &quot;Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure &quot;done()&quot; is called; if returning a Promise, ensure it resolves.&quot; If this happens, rerun the test command. It normally works the next time (or within a total or three tries). We are working to change our testing and installation so Postgres is ready before operations continue so this problem will go away. The current fix is to allow a test to take up toe 15,000 ms or 15 seconds to complete so Postgres has time to start up and that is why you see &quot;15000ms&quot; in the error message. We have also set the timeout to be longer in a few tests where the issue was happening. If the problem persists, you can go into package.json and change the 15000 to be a larger value (such as 30000). This means mocha will not terminate a test until 30 seconds have passed. The only known negative of doing this is that a test that will not complete due to an error will take longer for mocha to terminate. However, this is uncommon in OED tests so the change should be fine. check permission error (historical) A few developers have reported that when they run docker compose run --rm web npm run check they get an error similar to &quot;Error: EACCES: permission denied, scandir &#39;/root/.npm/_logs&quot;. We do not believe this will happen any longer now that developers are asked to work within the Docker container. For the historical record the only know fix was to run outside of docker by doing npm run check. It is believed that this issue is due to doing installs as root and then not being root when inside docker but this is not certain. However, at least one developer found that changing the file permissions did not fix the issue. If anyone has this issue or finds a solution then please let us know. Faster OED installation (historical) The installation process was updated in late February 2022 so the node modules are not updated unless needed. This means the node modules will only be updated if the package.json and/or package-lock.json file is update whether by directed edit or from pulling updating versions. As a result, the old method of install_args=&quot;--keep_node_modules&quot; docker compose up should not be needed if you are running current versions of OED software. The keep_node_modules parameter was left for backward compatibility and in the unlikely case where a developer wishes to use it. As expected, the steps and output is different when there is no node module installation as seen in skipping NPM install output."><meta property="og:url" content="https://openenergydashboard.org/developer/devDetails/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Developer Details</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Developer Details</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>There are many details and good ideas to use as an OED developer. This page tries to give you some of them. The topics covered are:<ol><li><a href="#stopping">Stopping OED</a><li><a href="#goingOn">Seeing what is happening with OED</a><li><a href="#codeChange">Getting a running OED to recognize code changes</a><li><a href="#dbAccess">Accessing the database</a><li><a href="#singleTest">Rapid testing of a one or a few test(s)</a><li><a href="#resetDB">Resetting the Postgres database</a><li><a href="#environment">OED environment variables</a><li><a href="#scripts">OED Scripts</a><li><a href="#migrate">Migrating OED</a><li><a href="#versions">Having multiple versions of OED</a><li><a href="#rebuild">Rebuild after Docker dependency changes</a><li><a href="#noDb">Running without the database container</a><li><a href="#typescript">TypeScript Wisdom</a><li><a href="#testingTimeout">Database timeout on testing</a><li><a href="#npmPermission">check permission error (historical)</a><li><a href="#fastInstall">Faster OED installation (historical)</a></ol><h2 id="stopping">Stopping OED</h2><p>If you are running in a VSC container, then you can simply click the green icon for the Remote Container and select "Close Remote Container". You can also shut the container down manually (by right clicking and choosing "stop") but that is normally only done if something went wrong in shutting down the container in the usual way.<p>If you are running OED outside of Visual Studio Code then go to the terminal where OED is running, you can type ^-c (control and letter c) together to stop OED. Note it is best to only do this once since a second time causes a force stop. An alternative is to use <code>docker compose down</code> in a second terminal that is in the same directory as where the install is happening. This can also be useful if you are having an issue with your docker container(s) since it cleans them all up. Normally, doing ^-z will put the process into the background. This does not work with a running OED.<h2 id="goingOn">Seeing what is happening with OED</h2><p>Sometimes OED will not act as you expect and you want to know what is going on. There are two normal ways to do this:<ul><li>The "nohup.out" file in the main OED directory shows all the logged messages. (If running OED outside Visual Studio Code then it is in the terminal where you started OED.) It is a good idea to be able to see this while you are running a version you are developing so you can tell when something significant happens. The messages can be informational where these are normal and not an indication of a problem. Any server side console.log output will be here.<li>Any console.log output on the client side will show up in the web browser console.<li>OED has the log file "log.txt" in the main OED directory. All logged messages and errors should be placed in this file. The newest messages are at the end. This file can get large over time so you probably want to focus on lines in the time frame you are interested (they should be timestamped).<li>Using the Redux debugging tools in the web browser is also very valuable. It can also help to look at the traces. To do this you must enable it in the code. Go to src/client/app/index.tsx and do what the comments say to enable traces (comment out one line and uncomment two lines below). Please make sure you do not commit this change/include in a pull request. As the comments indicate, it would be nice to automate this process and maybe a developer will do this work and submit a PR.</ul><h2 id="codeChange">Getting a running OED to recognize code changes</h2><p>As a developer, you are often changing the code to see what impact it has on a running version of OED. In general, the system should recognize these changes and update the running version. If you change code under the client/ directory, the output will include a rebuild of the code. When that happens, the output will show this line if it worked. This will be in the terminal where OED is running or in nohup.out if you are working inside VSC.<br> <code>oed-web-1 | webpack 5.62.0 compiled successfully in 24100 ms</code><br> If it fails then you will see one or more failure lines (with failure in red) rather than success. It will also show that it is done rebuilding when you see the line:<br> <code>oed-web-1 | \<s\> [webpack.Progress] 100% </code><br> It is not safe to reload the new version in the web browser until the rebuild finishes. You must reload to see the new code. If you change code on the server side, you will not see a rebuild but after a few lines of output you will see:<br> <code>oed-web-1 | [INFO@2022-04-24T16:31:17.449Z] Listening on port 3000</code><br> and then you can see the changes. Since all these changes are on the server, you do not need to reload the web browser.<p>Normally the output is seen quickly but it can take a little while for webpack to detect the changes. If it ever fails to do this you could shut down OED and restart it but it is generally much easier/faster to go into some file, add a space, remove the space and save the file. This change (that really does nothing) should cause webpack to start the rebuild.<p>In several cases, developers on Windows have reported not having the code rebuild on save. It turned out that the code was not on the WSL/Linux partition (generally under /home). As described in <a href="../wslSteps/">WSL on Windows</a>, it is important to do this properly.<h2 id="dbAccess">Accessing the database</h2><p>There are two ways to access the Postgres database that OED uses. Through the docker container or through pgAdmin<ul><li> To access the database from the docker database container (see <a href="../gettingStarted/#VSCInfo">info on accessing containers)</a>, execute the following command: <code>psql -U oed</code>. You will now be in the Postgres command line for the OED database. It is assumed that you know some SQL and Postgres command line controls if you use this method. One important one is <code>\q</code> which will get you back to the terminal by leaving the Postgres command system.<li> You can also use the pgAdmin utility to access the database. For this method, you need to install pgAdmin on your device. The link to get the latest version is <a href="https://www.pgadmin.org/download/">here</a>. Once you have downloaded and installed the correct version for your operating system, you need to enable the port for the connection to pgAdmin. This can be done by going to the docker-compose.yml file in the main OED directory and uncommenting the lines <code>ports:</code> and <code>-"5432":"5432"</code>. Note you must shut down and restart OED for this to take effect. You should now be able to open pgAdmin and access the database on localhost port 5432 by adding a New Server with these properties:<ul><li>General tab:<ul><li>Name: oed (or whatever desired)</ul><li>Connection tab:<ul><li>Host name/address: localhost<li>Post: 5432 (should be default)<li>Username: oed<li>password: opened (unless changed in docker-compoe.yml)<li>Save password?: enable if desired to log in again without password</ul></ul><p>A screenshot of the setup:<p><img alt="PGAdmin setup" src="../images/pgAdminSetup.png"><p>When Save, it will verify connection and then open up connection if all is correct.</ul><p>Note that no matter how you access the OED database it is the live system so you can make changes that the running application will see (and damage the information too!).<p>There may be times you want to backup/restore the Postgres data for OED. You can do it by<ul><li>Take a database dump (in the database Docker container terminal) with <code>pg_dump -U oed &gt; dump_$(date +%Y-%m-%d"_"%H_%M_%S.sql)</code><li>Restore a database dump by first copying the dump into the container with <code>docker cp /path/to/dump.sql container_name:/dump.sql</code> and then restoring it into the database with <code>psql -U oed -f /dump.sql</code>. The /path/to/dump.sql is the file with date & time created in the dump step. TODO Note someone should test/see if you really need to put it into the container first and this has not been tested since we went to working in the database container.</ul><h2 id="singleTest">Rapid testing of a one or a few test(s)</h2><p>When you make changes to OED or develop new tests, it may be the case that only one or a few tests fail when you run testing (or you want to focus on one test at a time that fails). Running all the tests is much slower than running a single test file. Thus, to run a single test, in the web/vsc docker container (see <a href="../gettingStarted/#VSCInfo">info on accessing container</a>) do:<br> <code>npm run testsome &lt;first test&gt; [&lt;second test&gt;] </code><br> where you replace &lt; xxxx test&gt; with the path to the test file you want to run and [ ] indicates this is optional and you can repeat as many times as you want for more tests.<p>For example, to run the web groups test, you would use:<br> <code>npm run testsome src/server/test/web/groups.js</code><br> and to run the web groups test and the db baselineTests use:<br> <code>npm run testsome src/server/test/web/groups.js src/server/test/db/baselineTests.js</code><p>If you are using VSC you can easily get the path to any open test file. Right click on the file name in the tab for that editor window and choose "Copy Relative Path". This can then be pasted into the needed command.<h2 id="resetDB">Resetting the Postgres database</h2><p>During the initial install of OED, Postgres detects that you have not run before for this install and initializes the database system. It keeps the information in the postgres-data/ directory in the main OED directory. If you or a pull changes the database configuration, it will not automatically be changed on the next OED install. When we change versions of OED we use a migration system to upgrade the database but this may not be available during the development cycle. Given this, it is often easiest to force Postgres to reinitialize the database. Note that doing this will wipe out any data (meter, readings, preferences, etc.) that you have for this instance of OED. If you wish to force Postgres to reinitialize then do the following:<ol><li>Remove the postgres-data/ directory from the main OED directory. While you can move it to keep a copy, some OSes will still use the moved directory as if it exists in the main OED directory (at least until a reboot). Thus, it is probably best to delete the directory. Also note that OED should not be running when you do this as it will cause all kinds of problems when it does not find this directory. OED will automatically recreate the next time you bring it up.<ul><li>To delete this on Linux, you can do <code>rm -rf postgres-data</code> in the main OED directory. Note you may need to be root to remove this directory. If this is the case, use <code>sudo rm -rf postgres-data</code> where you will be prompted for the root password.<li>It is sometimes tricky to know/login as root on a Windows WSL system. In this case, open the PowerShell, and enter the command <code>wsl -u root</code> that will put you in your WSL/Linus terminal as root. You can then directly delete the postgres-data/ directory. You should be very careful using this terminal as you can do damage as the root user.<li>After you delete the postgres-data/ directory on Windows WSL, you will need to delete both OED containers (can do via the Docker Desktop or Docker extension in VSC). Doing a <code>docker compose down</code> in a terminal in the main OED directory will also accomplish this. Otherwise, you are likely to get the following error when you restart OED:<p> Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2" to rootfs at "/var/lib/postgresql/data/pgdata": mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2:/var/lib/postgresql/data/pgdata (via /proc/self/fd/14), flags: 0x5000: no such file or directory: unknown</ul><li>Do an install of OED by reopening it in the VSC container or doing it outside of VSC. Remember if package changes were made then it will reinstall the node_modules. Note the install will take longer do to the extra initializations.<li>Sometimes the first attempt at installation will fail when you do this. Try it one or two times more to see if it will work. (We are trying to determine why this happens.) If not, replace the postgres-data/ directory with the one removed and this should get you running but will not give you a new version of the database. If you have this issue then contact us for help (see link at bottom of page).</ol><p>OED runs in the containerized Docker environment. This means the software and files created are within this container and disappear when you stop running OED (shut the container down). The one exception to this rule is the information stored in the PostgreSQL database. Because this information needs to exist between OED runs to keep the database initialization and OED data, the information is kept within your OED installation in the postgres-data/ directory on your machine's file system. This is why removing the postgres-data/ directory resets the database within the Docker container.<h2 id="environment">OED environment variables</h2><p>If you want to know about the environment variables that control OED then see the <a href="../environment/">environment page</a>.<h2 id="scripts">OED Scripts</h2><p>OED has a number of scripts that are run via commands in the package.json file. A complete listing with descriptions is on the <a href="../npm/">NPM script</a> page.<h2 id="migrate">Migrating OED</h2><p>The script <code>src/scripts/updateOED.sh</code> should update all dependencies and migrate the OED database if changes are needed. This may not work (see ideas above) if migrations are not yet available or this has been done before for the same version of OED.<h2 id="versions">Having multiple versions of OED</h2><p>Most developers keep one clone of the OED software. They switch between branches as needed. However, if you are working on multiple versions of OED, esp. where the node modules are changing or the database configuration changes, then you can avoid having to do a full install (see above) by cloning separate copies of OED. When you install it will do the clone you are currently located in (the current directory in your terminal). The database information and all code is kept separate for each installation as part of the Docker containerization. Note you cannot run multiple version of OED simultaneously unless you change the ports it uses (this is not common).<h2 id="rebuild">Rebuild after Docker dependency changes</h2><p>If a "From" in a Dockerfile is changed, then the version of that software needs to be updated. Docker normally uses its cached version so the update will not happen. To force the update, do:<ul><li>Inside VSC run the command <code>rebuild container</code>.<li>Outside VSC in a terminal do <code>docker compose up --build</code> where you can add other arguments (such as keeping the node modules). This is unusual in that it is done in a terminal on your own machine in the main OED directory and not in an OED Docker container (because you are resetting the Docker containers).</ul><p>This should make Docker use what is specified in the Dockerfile. If there are no changes then it will not download a new version of the needed software but it will be a little slower for the checks and potentially creating the container. OED tries to announce to the Docker channel for developers whenever a change is make to a Dockerfile that would require this action. This is not commonly done.<h2 id="noDb">Running without the database container</h2><p>On rare occasions, you may get a database failure during the startup of the database container during the install/startup of OED. (This is not the transient issues noted during the install where the script reports it is continuing). Generally OED will tell you an issue happened in the console output and Docker indicates the database container is not running. In general, the underlying issue should be addressed so you have a correct OED installation. (This happened, for example, during Windows WSL installs until an file permission issue was resolved.) In rare circumstances, you still want to run the OED web container knowing that any operations that touch the database will fail. There is a parameter to the install script that allows this and can be done with: <br><code>install_args="--continue_on_db_error" docker compose up</code><br> or the full install script (not using docker compose up) of <br><code>docker compose run --service-ports --rm web npm run src/scripts/installOED.sh --continue_on_db_error</code><br> OED will still try to install the DB, fail and then continue to try to install the web container. You should see the regular messages in the console indicating the web container is running as expected. If you are working inside VSC, you will need to edit the src/scripts/installOED.sh script to add the --continue_on_db_error parameter.<h2 id="typescript">TypeScript Wisdom</h2><p>TypeScript is great, but sometimes it requires some rather strange incantations, especially when working with external libraries. We cannot provide information on everything you need to know but here is one of interest:<h3>Regarding <code>InjectedIntlProps</code> from <code>react-intl</code></h3><p>When using <code>react-intl</code>'s higher order component functionality, some incantations are required. When defining a component, it's necessary to express that the component's props are actually (your props) ∪ (internationalization injector). This can be done via the <code>&amp;</code> operator, as follows:<pre>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Developer Details</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. There are many details and good ideas to use as an OED developer. This page tries to give you some of them. The topics covered are: Stopping OED Seeing what is happening with OED Getting a running OED to recognize code changes Accessing the database Rapid testing of a one or a few test(s) Resetting the Postgres database OED environment variables OED Scripts Migrating OED Having multiple versions of OED Rebuild after Docker dependency changes Running without the database container TypeScript Wisdom Database timeout on testing check permission error (historical) Faster OED installation (historical) Stopping OED If you are running in a VSC container, then you can simply click the green icon for the Remote Container and select &quot;Close Remote Container&quot;. You can also shut the container down manually (by right clicking and choosing &quot;stop&quot;) but that is normally only done if something went wrong in shutting down the container in the usual way. If you are running OED outside of Visual Studio Code then go to the terminal where OED is running, you can type ^-c (control and letter c) together to stop OED. Note it is best to only do this once since a second time causes a force stop. An alternative is to use docker compose down in a second terminal that is in the same directory as where the install is happening. This can also be useful if you are having an issue with your docker container(s) since it cleans them all up. Normally, doing ^-z will put the process into the background. This does not work with a running OED. Seeing what is happening with OED Sometimes OED will not act as you expect and you want to know what is going on. There are two normal ways to do this: The &quot;nohup.out&quot; file in the main OED directory shows all the logged messages. (If running OED outside Visual Studio Code then it is in the terminal where you started OED.) It is a good idea to be able to see this while you are running a version you are developing so you can tell when something significant happens. The messages can be informational where these are normal and not an indication of a problem. Any server side console.log output will be here. Any console.log output on the client side will show up in the web browser console. OED has the log file &quot;log.txt&quot; in the main OED directory. All logged messages and errors should be placed in this file. The newest messages are at the end. This file can get large over time so you probably want to focus on lines in the time frame you are interested (they should be timestamped). Using the Redux debugging tools in the web browser is also very valuable. It can also help to look at the traces. To do this you must enable it in the code. Go to src/client/app/index.tsx and do what the comments say to enable traces (comment out one line and uncomment two lines below). Please make sure you do not commit this change/include in a pull request. As the comments indicate, it would be nice to automate this process and maybe a developer will do this work and submit a PR. Getting a running OED to recognize code changes As a developer, you are often changing the code to see what impact it has on a running version of OED. In general, the system should recognize these changes and update the running version. If you change code under the client/ directory, the output will include a rebuild of the code. When that happens, the output will show this line if it worked. This will be in the terminal where OED is running or in nohup.out if you are working inside VSC. oed-web-1 | webpack 5.62.0 compiled successfully in 24100 ms If it fails then you will see one or more failure lines (with failure in red) rather than success. It will also show that it is done rebuilding when you see the line: oed-web-1 | \ [webpack.Progress] 100% It is not safe to reload the new version in the web browser until the rebuild finishes. You must reload to see the new code. If you change code on the server side, you will not see a rebuild but after a few lines of output you will see: oed-web-1 | [INFO@2022-04-24T16:31:17.449Z] Listening on port 3000 and then you can see the changes. Since all these changes are on the server, you do not need to reload the web browser. Normally the output is seen quickly but it can take a little while for webpack to detect the changes. If it ever fails to do this you could shut down OED and restart it but it is generally much easier/faster to go into some file, add a space, remove the space and save the file. This change (that really does nothing) should cause webpack to start the rebuild. In several cases, developers on Windows have reported not having the code rebuild on save. It turned out that the code was not on the WSL/Linux partition (generally under /home). As described in the developer first steps page, it is important to do this properly. Accessing the database There are two ways to access the Postgres database that OED uses. Through the docker container or through pgAdmin To access the database from the docker database container (see info on accessing containers), execute the following command: psql -U oed. You will now be in the Postgres command line for the OED database. It is assumed that you know some SQL and Postgres command line controls if you use this method. One important one is \q which will get you back to the terminal by leaving the Postgres command system. You can also use the pgAdmin utility to access the database. For this method, you need to install pgAdmin on your device. The link to get the latest version is here. Once you have downloaded and installed the correct version for your operating system, you need to enable the port for the connection to pgAdmin. This can be done by going to the docker-compose.yml file in the main OED directory and uncommenting the lines ports: and -&quot;5432&quot;:&quot;5432&quot;. Note you must shut down and restart OED for this to take effect. You should now be able to open pgAdmin and access the database on localhost port 5432 by adding a New Server with these properties: General tab: Name: oed (or whatever desired) Connection tab: Host name/address: localhost Post: 5432 (should be default) Username: oed password: opened (unless changed in docker-compoe.yml) Save password?: enable if desired to log in again without password A screenshot of the setup: When Save, it will verify connection and then open up connection if all is correct. Note that no matter how you access the OED database it is the live system so you can make changes that the running application will see (and damage the information too!). There may be times you want to backup/restore the Postgres data for OED. You can do it by Take a database dump (in the database Docker container terminal) with pg_dump -U oed &amp;gt; dump_$(date +%Y-%m-%d&quot;_&quot;%H_%M_%S.sql) Restore a database dump by first copying the dump into the container with docker cp /path/to/dump.sql container_name:/dump.sql and then restoring it into the database with psql -U oed -f /dump.sql. The /path/to/dump.sql is the file with date &amp; time created in the dump step. TODO Note someone should test/see if you really need to put it into the container first and this has not been tested since we went to working in the database container. Rapid testing of a one or a few test(s) When you make changes to OED or develop new tests, it may be the case that only one or a few tests fail when you run testing (or you want to focus on one test at a time that fails). Running all the tests is much slower than running a single test file. Thus, to run a single test, in the web/vsc docker container (see info on accessing container) do: npm run testsome &amp;lt;first test&amp;gt; [&amp;lt;second test&amp;gt;] where you replace &amp;lt; xxxx test&amp;gt; with the path to the test file you want to run and [ ] indicates this is optional and you can repeat as many times as you want for more tests. For example, to run the web groups test, you would use: npm run testsome src/server/test/web/groups.js and to run the web groups test and the db baselineTests use: npm run testsome src/server/test/web/groups.js src/server/test/db/baselineTests.js If you are using VSC you can easily get the path to any open test file. Right click on the file name in the tab for that editor window and choose &quot;Copy Relative Path&quot;. This can then be pasted into the needed command. Resetting the Postgres database During the initial install of OED, Postgres detects that you have not run before for this install and initializes the database system. It keeps the information in the postgres-data/ directory in the main OED directory. If you or a pull changes the database configuration, it will not automatically be changed on the next OED install. When we change versions of OED we use a migration system to upgrade the database but this may not be available during the development cycle. Given this, it is often easiest to force Postgres to reinitialize the database. Note that doing this will wipe out any data (meter, readings, preferences, etc.) that you have for this instance of OED. If you wish to force Postgres to reinitialize then do the following: Remove the postgres-data/ directory from the main OED directory. While you can move it to keep a copy, some OSes will still use the moved directory as if it exists in the main OED directory (at least until a reboot). Thus, it is probably best to delete the directory. Also note that OED should not be running when you do this as it will cause all kinds of problems when it does not find this directory. OED will automatically recreate the next time you bring it up. To delete this on Linux, you can do rm -rf postgres-data in the main OED directory. Note you may need to be root to remove this directory. If this is the case, use sudo rm -rf postgres-data where you will be prompted for the root password. It is sometimes tricky to know/login as root on a Windows WSL system. In this case, open the PowerShell, and enter the command wsl -u root that will put you in your WSL/Linus terminal as root. You can then directly delete the postgres-data/ directory. You should be very careful using this terminal as you can do damage as the root user. After you delete the postgres-data/ directory on Windows WSL, you will need to delete both OED containers (can do via the Docker Desktop or Docker extension in VSC). Doing a docker compose down in a terminal in the main OED directory will also accomplish this. Otherwise, you are likely to get the following error when you restart OED: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting &quot;/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2&quot; to rootfs at &quot;/var/lib/postgresql/data/pgdata&quot;: mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2:/var/lib/postgresql/data/pgdata (via /proc/self/fd/14), flags: 0x5000: no such file or directory: unknown Do an install of OED by reopening it in the VSC container or doing it outside of VSC. Remember if package changes were made then it will reinstall the node_modules. Note the install will take longer do to the extra initializations. Sometimes the first attempt at installation will fail when you do this. Try it one or two times more to see if it will work. (We are trying to determine why this happens.) If not, replace the postgres-data/ directory with the one removed and this should get you running but will not give you a new version of the database. If you have this issue then contact us for help (see link at bottom of page). OED runs in the containerized Docker environment. This means the software and files created are within this container and disappear when you stop running OED (shut the container down). The one exception to this rule is the information stored in the PostgreSQL database. Because this information needs to exist between OED runs to keep the database initialization and OED data, the information is kept within your OED installation in the postgres-data/ directory on your machine&#39;s file system. This is why removing the postgres-data/ directory resets the database within the Docker container. OED environment variables If you want to know about the environment variables that control OED then see the environment page. OED Scripts OED has a number of scripts that are run via commands in the package.json file. A complete listing with descriptions is on the NPM script page. Migrating OED The script src/scripts/updateOED.sh should update all dependencies and migrate the OED database if changes are needed. This may not work (see ideas above) if migrations are not yet available or this has been done before for the same version of OED. Having multiple versions of OED Most developers keep one clone of the OED software. They switch between branches as needed. However, if you are working on multiple versions of OED, esp. where the node modules are changing or the database configuration changes, then you can avoid having to do a full install (see above) by cloning separate copies of OED. When you install it will do the clone you are currently located in (the current directory in your terminal). The database information and all code is kept separate for each installation as part of the Docker containerization. Note you cannot run multiple version of OED simultaneously unless you change the ports it uses (this is not common). Rebuild after Docker dependency changes If a &quot;From&quot; in a Dockerfile is changed, then the version of that software needs to be updated. Docker normally uses its cached version so the update will not happen. To force the update, do: Inside VSC run the command rebuild container. Outside VSC in a terminal do docker compose up --build where you can add other arguments (such as keeping the node modules). This is unusual in that it is done in a terminal on your own machine in the main OED directory and not in an OED Docker container (because you are resetting the Docker containers). This should make Docker use what is specified in the Dockerfile. If there are no changes then it will not download a new version of the needed software but it will be a little slower for the checks and potentially creating the container. OED tries to announce to the Docker channel for developers whenever a change is make to a Dockerfile that would require this action. This is not commonly done. Running without the database container On rare occasions, you may get a database failure during the startup of the database container during the install/startup of OED. (This is not the transient issues noted during the install where the script reports it is continuing). Generally OED will tell you an issue happened in the console output and Docker indicates the database container is not running. In general, the underlying issue should be addressed so you have a correct OED installation. (This happened, for example, during Windows WSL installs until an file permission issue was resolved.) In rare circumstances, you still want to run the OED web container knowing that any operations that touch the database will fail. There is a parameter to the install script that allows this and can be done with: install_args=&quot;--continue_on_db_error&quot; docker compose up or the full install script (not using docker compose up) of docker compose run --service-ports --rm web npm run src/scripts/installOED.sh --continue_on_db_error OED will still try to install the DB, fail and then continue to try to install the web container. You should see the regular messages in the console indicating the web container is running as expected. If you are working inside VSC, you will need to edit the src/scripts/installOED.sh script to add the --continue_on_db_error parameter. TypeScript Wisdom TypeScript is great, but sometimes it requires some rather strange incantations, especially when working with external libraries. We cannot provide information on everything you need to know but here is one of interest: Regarding InjectedIntlProps from react-intl When using react-intl&#39;s higher order component functionality, some incantations are required. When defining a component, it&#39;s necessary to express that the component&#39;s props are actually (your props) ∪ (internationalization injector). This can be done via the &amp;amp; operator, as follows: interfaceSomeProps { prop1: number; } interfaceSomeState { state1: number; } class SomeComponent extends React.Component&amp;lt;SomeProps &amp;amp; InjectedIntlProps, SomeState&amp;gt; { constructor(props: SomeProps: &amp;amp; InjectedIntlProps) { super(props); // ... } // ... } export default injectIntl&amp;lt;SomeProps&amp;gt;(SomeComponent); If the union type is used often, it might be cleaner to create a type alias: type SomePropsWithIntl = SomeProps &amp;amp; InjectedIntlProps; Database timeout on testing Sometimes when you run the OED tests for the first time in a while, you get an error about the database timing out. The message is normally something similar to &quot;Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure &quot;done()&quot; is called; if returning a Promise, ensure it resolves.&quot; If this happens, rerun the test command. It normally works the next time (or within a total or three tries). We are working to change our testing and installation so Postgres is ready before operations continue so this problem will go away. The current fix is to allow a test to take up toe 15,000 ms or 15 seconds to complete so Postgres has time to start up and that is why you see &quot;15000ms&quot; in the error message. We have also set the timeout to be longer in a few tests where the issue was happening. If the problem persists, you can go into package.json and change the 15000 to be a larger value (such as 30000). This means mocha will not terminate a test until 30 seconds have passed. The only known negative of doing this is that a test that will not complete due to an error will take longer for mocha to terminate. However, this is uncommon in OED tests so the change should be fine. check permission error (historical) A few developers have reported that when they run docker compose run --rm web npm run check they get an error similar to &quot;Error: EACCES: permission denied, scandir &#39;/root/.npm/_logs&quot;. We do not believe this will happen any longer now that developers are asked to work within the Docker container. For the historical record the only know fix was to run outside of docker by doing npm run check. It is believed that this issue is due to doing installs as root and then not being root when inside docker but this is not certain. However, at least one developer found that changing the file permissions did not fix the issue. If anyone has this issue or finds a solution then please let us know. Faster OED installation (historical) The installation process was updated in late February 2022 so the node modules are not updated unless needed. This means the node modules will only be updated if the package.json and/or package-lock.json file is update whether by directed edit or from pulling updating versions. As a result, the old method of install_args=&quot;--keep_node_modules&quot; docker compose up should not be needed if you are running current versions of OED software. The keep_node_modules parameter was left for backward compatibility and in the unlikely case where a developer wishes to use it. As expected, the steps and output is different when there is no node module installation as seen in skipping NPM install output."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/devDetails/"><meta property="og:title" content="Developer Details"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. There are many details and good ideas to use as an OED developer. This page tries to give you some of them. The topics covered are: Stopping OED Seeing what is happening with OED Getting a running OED to recognize code changes Accessing the database Rapid testing of a one or a few test(s) Resetting the Postgres database OED environment variables OED Scripts Migrating OED Having multiple versions of OED Rebuild after Docker dependency changes Running without the database container TypeScript Wisdom Database timeout on testing check permission error (historical) Faster OED installation (historical) Stopping OED If you are running in a VSC container, then you can simply click the green icon for the Remote Container and select &quot;Close Remote Container&quot;. You can also shut the container down manually (by right clicking and choosing &quot;stop&quot;) but that is normally only done if something went wrong in shutting down the container in the usual way. If you are running OED outside of Visual Studio Code then go to the terminal where OED is running, you can type ^-c (control and letter c) together to stop OED. Note it is best to only do this once since a second time causes a force stop. An alternative is to use docker compose down in a second terminal that is in the same directory as where the install is happening. This can also be useful if you are having an issue with your docker container(s) since it cleans them all up. Normally, doing ^-z will put the process into the background. This does not work with a running OED. Seeing what is happening with OED Sometimes OED will not act as you expect and you want to know what is going on. There are two normal ways to do this: The &quot;nohup.out&quot; file in the main OED directory shows all the logged messages. (If running OED outside Visual Studio Code then it is in the terminal where you started OED.) It is a good idea to be able to see this while you are running a version you are developing so you can tell when something significant happens. The messages can be informational where these are normal and not an indication of a problem. Any server side console.log output will be here. Any console.log output on the client side will show up in the web browser console. OED has the log file &quot;log.txt&quot; in the main OED directory. All logged messages and errors should be placed in this file. The newest messages are at the end. This file can get large over time so you probably want to focus on lines in the time frame you are interested (they should be timestamped). Using the Redux debugging tools in the web browser is also very valuable. It can also help to look at the traces. To do this you must enable it in the code. Go to src/client/app/index.tsx and do what the comments say to enable traces (comment out one line and uncomment two lines below). Please make sure you do not commit this change/include in a pull request. As the comments indicate, it would be nice to automate this process and maybe a developer will do this work and submit a PR. Getting a running OED to recognize code changes As a developer, you are often changing the code to see what impact it has on a running version of OED. In general, the system should recognize these changes and update the running version. If you change code under the client/ directory, the output will include a rebuild of the code. When that happens, the output will show this line if it worked. This will be in the terminal where OED is running or in nohup.out if you are working inside VSC. oed-web-1 | webpack 5.62.0 compiled successfully in 24100 ms If it fails then you will see one or more failure lines (with failure in red) rather than success. It will also show that it is done rebuilding when you see the line: oed-web-1 | \ [webpack.Progress] 100% It is not safe to reload the new version in the web browser until the rebuild finishes. You must reload to see the new code. If you change code on the server side, you will not see a rebuild but after a few lines of output you will see: oed-web-1 | [INFO@2022-04-24T16:31:17.449Z] Listening on port 3000 and then you can see the changes. Since all these changes are on the server, you do not need to reload the web browser. Normally the output is seen quickly but it can take a little while for webpack to detect the changes. If it ever fails to do this you could shut down OED and restart it but it is generally much easier/faster to go into some file, add a space, remove the space and save the file. This change (that really does nothing) should cause webpack to start the rebuild. In several cases, developers on Windows have reported not having the code rebuild on save. It turned out that the code was not on the WSL/Linux partition (generally under /home). As described in the developer first steps page, it is important to do this properly. Accessing the database There are two ways to access the Postgres database that OED uses. Through the docker container or through pgAdmin To access the database from the docker database container (see info on accessing containers), execute the following command: psql -U oed. You will now be in the Postgres command line for the OED database. It is assumed that you know some SQL and Postgres command line controls if you use this method. One important one is \q which will get you back to the terminal by leaving the Postgres command system. You can also use the pgAdmin utility to access the database. For this method, you need to install pgAdmin on your device. The link to get the latest version is here. Once you have downloaded and installed the correct version for your operating system, you need to enable the port for the connection to pgAdmin. This can be done by going to the docker-compose.yml file in the main OED directory and uncommenting the lines ports: and -&quot;5432&quot;:&quot;5432&quot;. Note you must shut down and restart OED for this to take effect. You should now be able to open pgAdmin and access the database on localhost port 5432 by adding a New Server with these properties: General tab: Name: oed (or whatever desired) Connection tab: Host name/address: localhost Post: 5432 (should be default) Username: oed password: opened (unless changed in docker-compoe.yml) Save password?: enable if desired to log in again without password A screenshot of the setup: When Save, it will verify connection and then open up connection if all is correct. Note that no matter how you access the OED database it is the live system so you can make changes that the running application will see (and damage the information too!). There may be times you want to backup/restore the Postgres data for OED. You can do it by Take a database dump (in the database Docker container terminal) with pg_dump -U oed &amp;gt; dump_$(date +%Y-%m-%d&quot;_&quot;%H_%M_%S.sql) Restore a database dump by first copying the dump into the container with docker cp /path/to/dump.sql container_name:/dump.sql and then restoring it into the database with psql -U oed -f /dump.sql. The /path/to/dump.sql is the file with date &amp; time created in the dump step. TODO Note someone should test/see if you really need to put it into the container first and this has not been tested since we went to working in the database container. Rapid testing of a one or a few test(s) When you make changes to OED or develop new tests, it may be the case that only one or a few tests fail when you run testing (or you want to focus on one test at a time that fails). Running all the tests is much slower than running a single test file. Thus, to run a single test, in the web/vsc docker container (see info on accessing container) do: npm run testsome &amp;lt;first test&amp;gt; [&amp;lt;second test&amp;gt;] where you replace &amp;lt; xxxx test&amp;gt; with the path to the test file you want to run and [ ] indicates this is optional and you can repeat as many times as you want for more tests. For example, to run the web groups test, you would use: npm run testsome src/server/test/web/groups.js and to run the web groups test and the db baselineTests use: npm run testsome src/server/test/web/groups.js src/server/test/db/baselineTests.js If you are using VSC you can easily get the path to any open test file. Right click on the file name in the tab for that editor window and choose &quot;Copy Relative Path&quot;. This can then be pasted into the needed command. Resetting the Postgres database During the initial install of OED, Postgres detects that you have not run before for this install and initializes the database system. It keeps the information in the postgres-data/ directory in the main OED directory. If you or a pull changes the database configuration, it will not automatically be changed on the next OED install. When we change versions of OED we use a migration system to upgrade the database but this may not be available during the development cycle. Given this, it is often easiest to force Postgres to reinitialize the database. Note that doing this will wipe out any data (meter, readings, preferences, etc.) that you have for this instance of OED. If you wish to force Postgres to reinitialize then do the following: Remove the postgres-data/ directory from the main OED directory. While you can move it to keep a copy, some OSes will still use the moved directory as if it exists in the main OED directory (at least until a reboot). Thus, it is probably best to delete the directory. Also note that OED should not be running when you do this as it will cause all kinds of problems when it does not find this directory. OED will automatically recreate the next time you bring it up. To delete this on Linux, you can do rm -rf postgres-data in the main OED directory. Note you may need to be root to remove this directory. If this is the case, use sudo rm -rf postgres-data where you will be prompted for the root password. It is sometimes tricky to know/login as root on a Windows WSL system. In this case, open the PowerShell, and enter the command wsl -u root that will put you in your WSL/Linus terminal as root. You can then directly delete the postgres-data/ directory. You should be very careful using this terminal as you can do damage as the root user. After you delete the postgres-data/ directory on Windows WSL, you will need to delete both OED containers (can do via the Docker Desktop or Docker extension in VSC). Doing a docker compose down in a terminal in the main OED directory will also accomplish this. Otherwise, you are likely to get the following error when you restart OED: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting &quot;/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2&quot; to rootfs at &quot;/var/lib/postgresql/data/pgdata&quot;: mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2:/var/lib/postgresql/data/pgdata (via /proc/self/fd/14), flags: 0x5000: no such file or directory: unknown Do an install of OED by reopening it in the VSC container or doing it outside of VSC. Remember if package changes were made then it will reinstall the node_modules. Note the install will take longer do to the extra initializations. Sometimes the first attempt at installation will fail when you do this. Try it one or two times more to see if it will work. (We are trying to determine why this happens.) If not, replace the postgres-data/ directory with the one removed and this should get you running but will not give you a new version of the database. If you have this issue then contact us for help (see link at bottom of page). OED runs in the containerized Docker environment. This means the software and files created are within this container and disappear when you stop running OED (shut the container down). The one exception to this rule is the information stored in the PostgreSQL database. Because this information needs to exist between OED runs to keep the database initialization and OED data, the information is kept within your OED installation in the postgres-data/ directory on your machine&#39;s file system. This is why removing the postgres-data/ directory resets the database within the Docker container. OED environment variables If you want to know about the environment variables that control OED then see the environment page. OED Scripts OED has a number of scripts that are run via commands in the package.json file. A complete listing with descriptions is on the NPM script page. Migrating OED The script src/scripts/updateOED.sh should update all dependencies and migrate the OED database if changes are needed. This may not work (see ideas above) if migrations are not yet available or this has been done before for the same version of OED. Having multiple versions of OED Most developers keep one clone of the OED software. They switch between branches as needed. However, if you are working on multiple versions of OED, esp. where the node modules are changing or the database configuration changes, then you can avoid having to do a full install (see above) by cloning separate copies of OED. When you install it will do the clone you are currently located in (the current directory in your terminal). The database information and all code is kept separate for each installation as part of the Docker containerization. Note you cannot run multiple version of OED simultaneously unless you change the ports it uses (this is not common). Rebuild after Docker dependency changes If a &quot;From&quot; in a Dockerfile is changed, then the version of that software needs to be updated. Docker normally uses its cached version so the update will not happen. To force the update, do: Inside VSC run the command rebuild container. Outside VSC in a terminal do docker compose up --build where you can add other arguments (such as keeping the node modules). This is unusual in that it is done in a terminal on your own machine in the main OED directory and not in an OED Docker container (because you are resetting the Docker containers). This should make Docker use what is specified in the Dockerfile. If there are no changes then it will not download a new version of the needed software but it will be a little slower for the checks and potentially creating the container. OED tries to announce to the Docker channel for developers whenever a change is make to a Dockerfile that would require this action. This is not commonly done. Running without the database container On rare occasions, you may get a database failure during the startup of the database container during the install/startup of OED. (This is not the transient issues noted during the install where the script reports it is continuing). Generally OED will tell you an issue happened in the console output and Docker indicates the database container is not running. In general, the underlying issue should be addressed so you have a correct OED installation. (This happened, for example, during Windows WSL installs until an file permission issue was resolved.) In rare circumstances, you still want to run the OED web container knowing that any operations that touch the database will fail. There is a parameter to the install script that allows this and can be done with: install_args=&quot;--continue_on_db_error&quot; docker compose up or the full install script (not using docker compose up) of docker compose run --service-ports --rm web npm run src/scripts/installOED.sh --continue_on_db_error OED will still try to install the DB, fail and then continue to try to install the web container. You should see the regular messages in the console indicating the web container is running as expected. If you are working inside VSC, you will need to edit the src/scripts/installOED.sh script to add the --continue_on_db_error parameter. TypeScript Wisdom TypeScript is great, but sometimes it requires some rather strange incantations, especially when working with external libraries. We cannot provide information on everything you need to know but here is one of interest: Regarding InjectedIntlProps from react-intl When using react-intl&#39;s higher order component functionality, some incantations are required. When defining a component, it&#39;s necessary to express that the component&#39;s props are actually (your props) ∪ (internationalization injector). This can be done via the &amp;amp; operator, as follows: interfaceSomeProps { prop1: number; } interfaceSomeState { state1: number; } class SomeComponent extends React.Component&amp;lt;SomeProps &amp;amp; InjectedIntlProps, SomeState&amp;gt; { constructor(props: SomeProps: &amp;amp; InjectedIntlProps) { super(props); // ... } // ... } export default injectIntl&amp;lt;SomeProps&amp;gt;(SomeComponent); If the union type is used often, it might be cleaner to create a type alias: type SomePropsWithIntl = SomeProps &amp;amp; InjectedIntlProps; Database timeout on testing Sometimes when you run the OED tests for the first time in a while, you get an error about the database timing out. The message is normally something similar to &quot;Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure &quot;done()&quot; is called; if returning a Promise, ensure it resolves.&quot; If this happens, rerun the test command. It normally works the next time (or within a total or three tries). We are working to change our testing and installation so Postgres is ready before operations continue so this problem will go away. The current fix is to allow a test to take up toe 15,000 ms or 15 seconds to complete so Postgres has time to start up and that is why you see &quot;15000ms&quot; in the error message. We have also set the timeout to be longer in a few tests where the issue was happening. If the problem persists, you can go into package.json and change the 15000 to be a larger value (such as 30000). This means mocha will not terminate a test until 30 seconds have passed. The only known negative of doing this is that a test that will not complete due to an error will take longer for mocha to terminate. However, this is uncommon in OED tests so the change should be fine. check permission error (historical) A few developers have reported that when they run docker compose run --rm web npm run check they get an error similar to &quot;Error: EACCES: permission denied, scandir &#39;/root/.npm/_logs&quot;. We do not believe this will happen any longer now that developers are asked to work within the Docker container. For the historical record the only know fix was to run outside of docker by doing npm run check. It is believed that this issue is due to doing installs as root and then not being root when inside docker but this is not certain. However, at least one developer found that changing the file permissions did not fix the issue. If anyone has this issue or finds a solution then please let us know. Faster OED installation (historical) The installation process was updated in late February 2022 so the node modules are not updated unless needed. This means the node modules will only be updated if the package.json and/or package-lock.json file is update whether by directed edit or from pulling updating versions. As a result, the old method of install_args=&quot;--keep_node_modules&quot; docker compose up should not be needed if you are running current versions of OED software. The keep_node_modules parameter was left for backward compatibility and in the unlikely case where a developer wishes to use it. As expected, the steps and output is different when there is no node module installation as seen in skipping NPM install output."><meta property="og:url" content="https://openenergydashboard.org/developer/devDetails/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Developer Details</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Developer Details</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>There are many details and good ideas to use as an OED developer. This page tries to give you some of them. The topics covered are:<ol><li><a href="#stopping">Stopping OED</a><li><a href="#goingOn">Seeing what is happening with OED</a><li><a href="#codeChange">Getting a running OED to recognize code changes</a><li><a href="#dbAccess">Accessing the database</a><li><a href="#singleTest">Rapid testing of a one or a few test(s)</a><li><a href="#resetDB">Resetting the Postgres database</a><li><a href="#environment">OED environment variables</a><li><a href="#scripts">OED Scripts</a><li><a href="#migrate">Migrating OED</a><li><a href="#versions">Having multiple versions of OED</a><li><a href="#rebuild">Rebuild after Docker dependency changes</a><li><a href="#noDb">Running without the database container</a><li><a href="#typescript">TypeScript Wisdom</a><li><a href="#testingTimeout">Database timeout on testing</a><li><a href="#npmPermission">check permission error (historical)</a><li><a href="#fastInstall">Faster OED installation (historical)</a></ol><h2 id="stopping">Stopping OED</h2><p>If you are running in a VSC container, then you can simply click the green icon for the Remote Container and select "Close Remote Container". You can also shut the container down manually (by right clicking and choosing "stop") but that is normally only done if something went wrong in shutting down the container in the usual way.<p>If you are running OED outside of Visual Studio Code then go to the terminal where OED is running, you can type ^-c (control and letter c) together to stop OED. Note it is best to only do this once since a second time causes a force stop. An alternative is to use <code>docker compose down</code> in a second terminal that is in the same directory as where the install is happening. This can also be useful if you are having an issue with your docker container(s) since it cleans them all up. Normally, doing ^-z will put the process into the background. This does not work with a running OED.<h2 id="goingOn">Seeing what is happening with OED</h2><p>Sometimes OED will not act as you expect and you want to know what is going on. There are two normal ways to do this:<ul><li>The "nohup.out" file in the main OED directory shows all the logged messages. (If running OED outside Visual Studio Code then it is in the terminal where you started OED.) It is a good idea to be able to see this while you are running a version you are developing so you can tell when something significant happens. The messages can be informational where these are normal and not an indication of a problem. Any server side console.log output will be here.<li>Any console.log output on the client side will show up in the web browser console.<li>OED has the log file "log.txt" in the main OED directory. All logged messages and errors should be placed in this file. The newest messages are at the end. This file can get large over time so you probably want to focus on lines in the time frame you are interested (they should be timestamped).<li>Using the Redux debugging tools in the web browser is also very valuable. It can also help to look at the traces. To do this you must enable it in the code. Go to src/client/app/index.tsx and do what the comments say to enable traces (comment out one line and uncomment two lines below). Please make sure you do not commit this change/include in a pull request. As the comments indicate, it would be nice to automate this process and maybe a developer will do this work and submit a PR.</ul><h2 id="codeChange">Getting a running OED to recognize code changes</h2><p>As a developer, you are often changing the code to see what impact it has on a running version of OED. In general, the system should recognize these changes and update the running version. If you change code under the client/ directory, the output will include a rebuild of the code. When that happens, the output will show this line if it worked. This will be in the terminal where OED is running or in nohup.out if you are working inside VSC.<br> <code>oed-web-1 | webpack 5.62.0 compiled successfully in 24100 ms</code><br> If it fails then you will see one or more failure lines (with failure in red) rather than success. It will also show that it is done rebuilding when you see the line:<br> <code>oed-web-1 | \<s\> [webpack.Progress] 100% </code><br> It is not safe to reload the new version in the web browser until the rebuild finishes. You must reload to see the new code. If you change code on the server side, you will not see a rebuild but after a few lines of output you will see:<br> <code>oed-web-1 | [INFO@2022-04-24T16:31:17.449Z] Listening on port 3000</code><br> and then you can see the changes. Since all these changes are on the server, you do not need to reload the web browser.<p>Normally the output is seen quickly but it can take a little while for webpack to detect the changes. If it ever fails to do this you could shut down OED and restart it but it is generally much easier/faster to go into some file, add a space, remove the space and save the file. This change (that really does nothing) should cause webpack to start the rebuild.<p>In several cases, developers on Windows have reported not having the code rebuild on save. It turned out that the code was not on the WSL/Linux partition (generally under /home). As described in the <a href="../gettingStarted/">developer first steps page</a>, it is important to do this properly.<h2 id="dbAccess">Accessing the database</h2><p>There are two ways to access the Postgres database that OED uses. Through the docker container or through pgAdmin<ul><li> To access the database from the docker database container (see <a href="../gettingStarted/#DockerInfo">info on accessing containers)</a>, execute the following command: <code>psql -U oed</code>. You will now be in the Postgres command line for the OED database. It is assumed that you know some SQL and Postgres command line controls if you use this method. One important one is <code>\q</code> which will get you back to the terminal by leaving the Postgres command system.<li> You can also use the pgAdmin utility to access the database. For this method, you need to install pgAdmin on your device. The link to get the latest version is <a href="https://www.pgadmin.org/download/">here</a>. Once you have downloaded and installed the correct version for your operating system, you need to enable the port for the connection to pgAdmin. This can be done by going to the docker-compose.yml file in the main OED directory and uncommenting the lines <code>ports:</code> and <code>-"5432":"5432"</code>. Note you must shut down and restart OED for this to take effect. You should now be able to open pgAdmin and access the database on localhost port 5432 by adding a New Server with these properties:<ul><li>General tab:<ul><li>Name: oed (or whatever desired)</ul><li>Connection tab:<ul><li>Host name/address: localhost<li>Post: 5432 (should be default)<li>Username: oed<li>password: opened (unless changed in docker-compoe.yml)<li>Save password?: enable if desired to log in again without password</ul></ul><p>A screenshot of the setup:<p><img alt="PGAdmin setup" src="../images/pgAdminSetup.png"><p>When Save, it will verify connection and then open up connection if all is correct.</ul><p>Note that no matter how you access the OED database it is the live system so you can make changes that the running application will see (and damage the information too!).<p>There may be times you want to backup/restore the Postgres data for OED. You can do it by<ul><li>Take a database dump (in the database Docker container terminal) with <code>pg_dump -U oed &gt; dump_$(date +%Y-%m-%d"_"%H_%M_%S.sql)</code><li>Restore a database dump by first copying the dump into the container with <code>docker cp /path/to/dump.sql container_name:/dump.sql</code> and then restoring it into the database with <code>psql -U oed -f /dump.sql</code>. The /path/to/dump.sql is the file with date & time created in the dump step. TODO Note someone should test/see if you really need to put it into the container first and this has not been tested since we went to working in the database container.</ul><h2 id="singleTest">Rapid testing of a one or a few test(s)</h2><p>When you make changes to OED or develop new tests, it may be the case that only one or a few tests fail when you run testing (or you want to focus on one test at a time that fails). Running all the tests is much slower than running a single test file. Thus, to run a single test, in the web/vsc docker container (see <a href="../gettingStarted/#DockerInfo">info on accessing container</a>) do:<br> <code>npm run testsome &lt;first test&gt; [&lt;second test&gt;] </code><br> where you replace &lt; xxxx test&gt; with the path to the test file you want to run and [ ] indicates this is optional and you can repeat as many times as you want for more tests.<p>For example, to run the web groups test, you would use:<br> <code>npm run testsome src/server/test/web/groups.js</code><br> and to run the web groups test and the db baselineTests use:<br> <code>npm run testsome src/server/test/web/groups.js src/server/test/db/baselineTests.js</code><p>If you are using VSC you can easily get the path to any open test file. Right click on the file name in the tab for that editor window and choose "Copy Relative Path". This can then be pasted into the needed command.<h2 id="resetDB">Resetting the Postgres database</h2><p>During the initial install of OED, Postgres detects that you have not run before for this install and initializes the database system. It keeps the information in the postgres-data/ directory in the main OED directory. If you or a pull changes the database configuration, it will not automatically be changed on the next OED install. When we change versions of OED we use a migration system to upgrade the database but this may not be available during the development cycle. Given this, it is often easiest to force Postgres to reinitialize the database. Note that doing this will wipe out any data (meter, readings, preferences, etc.) that you have for this instance of OED. If you wish to force Postgres to reinitialize then do the following:<ol><li>Remove the postgres-data/ directory from the main OED directory. While you can move it to keep a copy, some OSes will still use the moved directory as if it exists in the main OED directory (at least until a reboot). Thus, it is probably best to delete the directory. Also note that OED should not be running when you do this as it will cause all kinds of problems when it does not find this directory. OED will automatically recreate the next time you bring it up.<ul><li>To delete this on Linux, you can do <code>rm -rf postgres-data</code> in the main OED directory. Note you may need to be root to remove this directory. If this is the case, use <code>sudo rm -rf postgres-data</code> where you will be prompted for the root password.<li>It is sometimes tricky to know/login as root on a Windows WSL system. In this case, open the PowerShell, and enter the command <code>wsl -u root</code> that will put you in your WSL/Linus terminal as root. You can then directly delete the postgres-data/ directory. You should be very careful using this terminal as you can do damage as the root user.<li>After you delete the postgres-data/ directory on Windows WSL, you will need to delete both OED containers (can do via the Docker Desktop or Docker extension in VSC). Doing a <code>docker compose down</code> in a terminal in the main OED directory will also accomplish this. Otherwise, you are likely to get the following error when you restart OED:<p> Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2" to rootfs at "/var/lib/postgresql/data/pgdata": mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/c5c261024a2161c37bee3afcd0931bd36812e943519b816556c0bfbd60899ef2:/var/lib/postgresql/data/pgdata (via /proc/self/fd/14), flags: 0x5000: no such file or directory: unknown</ul><li>Do an install of OED by reopening it in the VSC container or doing it outside of VSC. Remember if package changes were made then it will reinstall the node_modules. Note the install will take longer do to the extra initializations.<li>Sometimes the first attempt at installation will fail when you do this. Try it one or two times more to see if it will work. (We are trying to determine why this happens.) If not, replace the postgres-data/ directory with the one removed and this should get you running but will not give you a new version of the database. If you have this issue then contact us for help (see link at bottom of page).</ol><p>OED runs in the containerized Docker environment. This means the software and files created are within this container and disappear when you stop running OED (shut the container down). The one exception to this rule is the information stored in the PostgreSQL database. Because this information needs to exist between OED runs to keep the database initialization and OED data, the information is kept within your OED installation in the postgres-data/ directory on your machine's file system. This is why removing the postgres-data/ directory resets the database within the Docker container.<h2 id="environment">OED environment variables</h2><p>If you want to know about the environment variables that control OED then see the <a href="../environment/">environment page</a>.<h2 id="scripts">OED Scripts</h2><p>OED has a number of scripts that are run via commands in the package.json file. A complete listing with descriptions is on the <a href="../npm/">NPM script</a> page.<h2 id="migrate">Migrating OED</h2><p>The script <code>src/scripts/updateOED.sh</code> should update all dependencies and migrate the OED database if changes are needed. This may not work (see ideas above) if migrations are not yet available or this has been done before for the same version of OED.<h2 id="versions">Having multiple versions of OED</h2><p>Most developers keep one clone of the OED software. They switch between branches as needed. However, if you are working on multiple versions of OED, esp. where the node modules are changing or the database configuration changes, then you can avoid having to do a full install (see above) by cloning separate copies of OED. When you install it will do the clone you are currently located in (the current directory in your terminal). The database information and all code is kept separate for each installation as part of the Docker containerization. Note you cannot run multiple version of OED simultaneously unless you change the ports it uses (this is not common).<h2 id="rebuild">Rebuild after Docker dependency changes</h2><p>If a "From" in a Dockerfile is changed, then the version of that software needs to be updated. Docker normally uses its cached version so the update will not happen. To force the update, do:<ul><li>Inside VSC run the command <code>rebuild container</code>.<li>Outside VSC in a terminal do <code>docker compose up --build</code> where you can add other arguments (such as keeping the node modules). This is unusual in that it is done in a terminal on your own machine in the main OED directory and not in an OED Docker container (because you are resetting the Docker containers).</ul><p>This should make Docker use what is specified in the Dockerfile. If there are no changes then it will not download a new version of the needed software but it will be a little slower for the checks and potentially creating the container. OED tries to announce to the Docker channel for developers whenever a change is make to a Dockerfile that would require this action. This is not commonly done.<h2 id="noDb">Running without the database container</h2><p>On rare occasions, you may get a database failure during the startup of the database container during the install/startup of OED. (This is not the transient issues noted during the install where the script reports it is continuing). Generally OED will tell you an issue happened in the console output and Docker indicates the database container is not running. In general, the underlying issue should be addressed so you have a correct OED installation. (This happened, for example, during Windows WSL installs until an file permission issue was resolved.) In rare circumstances, you still want to run the OED web container knowing that any operations that touch the database will fail. There is a parameter to the install script that allows this and can be done with: <br><code>install_args="--continue_on_db_error" docker compose up</code><br> or the full install script (not using docker compose up) of <br><code>docker compose run --service-ports --rm web npm run src/scripts/installOED.sh --continue_on_db_error</code><br> OED will still try to install the DB, fail and then continue to try to install the web container. You should see the regular messages in the console indicating the web container is running as expected. If you are working inside VSC, you will need to edit the src/scripts/installOED.sh script to add the --continue_on_db_error parameter.<h2 id="typescript">TypeScript Wisdom</h2><p>TypeScript is great, but sometimes it requires some rather strange incantations, especially when working with external libraries. We cannot provide information on everything you need to know but here is one of interest:<h3>Regarding <code>InjectedIntlProps</code> from <code>react-intl</code></h3><p>When using <code>react-intl</code>'s higher order component functionality, some incantations are required. When defining a component, it's necessary to express that the component's props are actually (your props) ∪ (internationalization injector). This can be done via the <code>&amp;</code> operator, as follows:<pre>
 interfaceSomeProps {
     prop1: number;
 }
diff --git a/developer/developer/index.html b/developer/developer/index.html
index 7696ef76..5bc4911e 100644
--- a/developer/developer/index.html
+++ b/developer/developer/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Developer Overview Doc</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Developer documentation Information Overview: Lists developer documentation pages. Starting Developer First Steps: How to begin coding development with OED. Steps for WSL: Describes steps generally needed on Windows OS for WSL. Contributor License Agreement: Describes the CLA that all contributors must sign. Creating Pull Requests: Describes how to request your work be integrated into the OED project. Test Data: Describes how to load sample data into your OED system. Work Selection: Describes some thoughts on choosing work within the OED project. Codebase Info Learn OED Technology: Describes resources to learn about the technologies used in OED. npm scripts: Information on npm commands that are available for a wide array of actions. Technology Overview: Overview of technology usage that currently describes how front-end code becomes our web-based app. Further Details Code Organization: Describes the directory structure and meaning of files in the OED code base. Developer Details: More detailed information that developers may find useful. Documentation Expectations: Describes our desires in documenting code and doing imports. Environment Variables: Information on environment variables used in OED. Full Install Output: Shows the terminal output of building OED for the first time. No npm/DB Install Output: Shows the terminal output of building OED where there the npm install is skipped. Test Code: Information on how to use and include test code in OED. Version Release Releasing OED: Discusses how to create an OED release."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/developer/"><meta property="og:title" content="Developer Overview Doc"><meta property="og:description" content="This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Developer documentation Information Overview: Lists developer documentation pages. Starting Developer First Steps: How to begin coding development with OED. Steps for WSL: Describes steps generally needed on Windows OS for WSL. Contributor License Agreement: Describes the CLA that all contributors must sign. Creating Pull Requests: Describes how to request your work be integrated into the OED project. Test Data: Describes how to load sample data into your OED system. Work Selection: Describes some thoughts on choosing work within the OED project. Codebase Info Learn OED Technology: Describes resources to learn about the technologies used in OED. npm scripts: Information on npm commands that are available for a wide array of actions. Technology Overview: Overview of technology usage that currently describes how front-end code becomes our web-based app. Further Details Code Organization: Describes the directory structure and meaning of files in the OED code base. Developer Details: More detailed information that developers may find useful. Documentation Expectations: Describes our desires in documenting code and doing imports. Environment Variables: Information on environment variables used in OED. Full Install Output: Shows the terminal output of building OED for the first time. No npm/DB Install Output: Shows the terminal output of building OED where there the npm install is skipped. Test Code: Information on how to use and include test code in OED. Version Release Releasing OED: Discusses how to create an OED release."><meta property="og:url" content="https://openenergydashboard.org/developer/developer/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li class="active"><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Overview</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Overview</h1></header><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a>: Lists developer documentation pages.</br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a>: How to begin coding development with OED.</br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a>: Describes steps generally needed on Windows OS for WSL.</br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a>: Describes the CLA that all contributors must sign.</br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a>: Describes how to request your work be integrated into the OED project.</br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a>: Describes how to load sample data into your OED system.</br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a>: Describes some thoughts on choosing work within the OED project.</br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a>: Describes resources to learn about the technologies used in OED.</br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a>: Information on npm commands that are available for a wide array of actions.</br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a>: Overview of technology usage that currently describes how front-end code becomes our web-based app.</br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a>: Describes the directory structure and meaning of files in the OED code base.</br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a>: More detailed information that developers may find useful.</br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a>: Describes our desires in documenting code and doing imports.</br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a>: Information on environment variables used in OED.</br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a>: Shows the terminal output of building OED for the first time.</br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a>: Shows the terminal output of building OED where there the npm install is skipped.</br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a>: Information on how to use and include test code in OED.</br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a>: Discusses how to create an OED release.</br></div></div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Developer Overview Doc</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Developer documentation Information Overview: Lists developer documentation pages. Starting Developer First Steps: How to begin coding development with OED. Contributor License Agreement: Describes the CLA that all contributors must sign. Creating Pull Requests: Describes how to request your work be integrated into the OED project. Test Data: Describes how to load sample data into your OED system. Work Selection: Describes some thoughts on choosing work within the OED project. Codebase Info Learn OED Technology: Describes resources to learn about the technologies used in OED. npm scripts: Information on npm commands that are available for a wide array of actions. Technology Overview: Overview of technology usage that currently describes how front-end code becomes our web-based app. Further Details Code Organization: Describes the directory structure and meaning of files in the OED code base. Developer Details: More detailed information that developers may find useful. Documentation Expectations: Describes our desires in documenting code and doing imports. Environment Variables: Information on environment variables used in OED. Full Install Output: Shows the terminal output of building OED for the first time. No npm/DB Install Output: Shows the terminal output of building OED where there the npm install is skipped. Test Code: Information on how to use and include test code in OED. Version Release Releasing OED: Discusses how to create an OED release."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/developer/"><meta property="og:title" content="Developer Overview Doc"><meta property="og:description" content="This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Developer documentation Information Overview: Lists developer documentation pages. Starting Developer First Steps: How to begin coding development with OED. Contributor License Agreement: Describes the CLA that all contributors must sign. Creating Pull Requests: Describes how to request your work be integrated into the OED project. Test Data: Describes how to load sample data into your OED system. Work Selection: Describes some thoughts on choosing work within the OED project. Codebase Info Learn OED Technology: Describes resources to learn about the technologies used in OED. npm scripts: Information on npm commands that are available for a wide array of actions. Technology Overview: Overview of technology usage that currently describes how front-end code becomes our web-based app. Further Details Code Organization: Describes the directory structure and meaning of files in the OED code base. Developer Details: More detailed information that developers may find useful. Documentation Expectations: Describes our desires in documenting code and doing imports. Environment Variables: Information on environment variables used in OED. Full Install Output: Shows the terminal output of building OED for the first time. No npm/DB Install Output: Shows the terminal output of building OED where there the npm install is skipped. Test Code: Information on how to use and include test code in OED. Version Release Releasing OED: Discusses how to create an OED release."><meta property="og:url" content="https://openenergydashboard.org/developer/developer/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li class="active"><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Overview</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Overview</h1></header><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a>: Lists developer documentation pages.</br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a>: How to begin coding development with OED.</br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a>: Describes the CLA that all contributors must sign.</br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a>: Describes how to request your work be integrated into the OED project.</br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a>: Describes how to load sample data into your OED system.</br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a>: Describes some thoughts on choosing work within the OED project.</br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a>: Describes resources to learn about the technologies used in OED.</br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a>: Information on npm commands that are available for a wide array of actions.</br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a>: Overview of technology usage that currently describes how front-end code becomes our web-based app.</br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a>: Describes the directory structure and meaning of files in the OED code base.</br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a>: More detailed information that developers may find useful.</br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a>: Describes our desires in documenting code and doing imports.</br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a>: Information on environment variables used in OED.</br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a>: Shows the terminal output of building OED for the first time.</br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a>: Shows the terminal output of building OED where there the npm install is skipped.</br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a>: Information on how to use and include test code in OED.</br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a>: Discusses how to create an OED release.</br></div></div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/environment/index.html b/developer/environment/index.html
index 5de0bcc5..aacc6fc6 100644
--- a/developer/environment/index.html
+++ b/developer/environment/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Environment Variables</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The OED server is configured via environment variables. These are normally set in the docker-compose.yml file located in the main OED directory. Developers generally do not need to change these values. Production installations generally do need to change some values as described in the installation directions. The environment variables are: OED_PRODUCTION: &#39;yes&#39; if running &quot;for realsies&quot; on a server (live site), &#39;no&#39; otherwise (normally development). OED_SERVER_PORT: The port that the server should run on. 3000 is a good default choice. OED_DB_USER: The user that should be used to connect to postgres. OED_DB_DATABASE: The database you just created, so likely oed. OED_DB_TEST_DATABASE: The test database you just created, so likely oed_testing. OED_DB_PASSWORD: The password for your postgres user. OED_DB_HOST: The host for your postgres db, likely database where docker will set the needed value since database is the name of the service for the database. OED_DB_PORT: The port for your postgres db, likely 5432. OED_TOKEN_SECRET: Token for authentication. Generate something secure and random where you should never need to use this value. OED_LOG_FILE: Path to the log file, defaults to ./log.txt. OED_MAIL_METHOD: Method of sending mail. Supports &quot;secure-smtp&quot; and &quot;none&quot;. Case insensitive. OED_MAIL_IDENT: Username for gmail, domain for mailgun. Ex: user@example.com OED_MAIL_CREDENTIAL: Password for gmail, or API key for mailgun. OED_MAIL_FROM: From address for email. If using GMail, make sure this is set. OED_MAIL_TO: Who gets error, warning (log) e-mail. Ex: admin@example.com OED_MAIL_ORG: Organization name, used in e-mail subject line TZ: Used to set the time zone on the OED server. This impacts the messages with timestamps from the server. By default this will be UTC."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/environment/"><meta property="og:title" content="Environment Variables"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The OED server is configured via environment variables. These are normally set in the docker-compose.yml file located in the main OED directory. Developers generally do not need to change these values. Production installations generally do need to change some values as described in the installation directions. The environment variables are: OED_PRODUCTION: &#39;yes&#39; if running &quot;for realsies&quot; on a server (live site), &#39;no&#39; otherwise (normally development). OED_SERVER_PORT: The port that the server should run on. 3000 is a good default choice. OED_DB_USER: The user that should be used to connect to postgres. OED_DB_DATABASE: The database you just created, so likely oed. OED_DB_TEST_DATABASE: The test database you just created, so likely oed_testing. OED_DB_PASSWORD: The password for your postgres user. OED_DB_HOST: The host for your postgres db, likely database where docker will set the needed value since database is the name of the service for the database. OED_DB_PORT: The port for your postgres db, likely 5432. OED_TOKEN_SECRET: Token for authentication. Generate something secure and random where you should never need to use this value. OED_LOG_FILE: Path to the log file, defaults to ./log.txt. OED_MAIL_METHOD: Method of sending mail. Supports &quot;secure-smtp&quot; and &quot;none&quot;. Case insensitive. OED_MAIL_IDENT: Username for gmail, domain for mailgun. Ex: user@example.com OED_MAIL_CREDENTIAL: Password for gmail, or API key for mailgun. OED_MAIL_FROM: From address for email. If using GMail, make sure this is set. OED_MAIL_TO: Who gets error, warning (log) e-mail. Ex: admin@example.com OED_MAIL_ORG: Organization name, used in e-mail subject line TZ: Used to set the time zone on the OED server. This impacts the messages with timestamps from the server. By default this will be UTC."><meta property="og:url" content="https://openenergydashboard.org/developer/environment/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Environment Variables</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Environment Variables</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>The OED server is configured via environment variables. These are normally set in the <code>docker-compose.yml</code> file located in the main OED directory. Developers generally do not need to change these values. Production installations generally do need to change some values as described in the <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">installation directions</a>.<p>The environment variables are:<ul><li>OED_PRODUCTION: 'yes' if running "for realsies" on a server (live site), 'no' otherwise (normally development).<li>OED_SERVER_PORT: The port that the server should run on. 3000 is a good default choice.<li>OED_DB_USER: The user that should be used to connect to postgres.<li>OED_DB_DATABASE: The database you just created, so likely oed.<li>OED_DB_TEST_DATABASE: The test database you just created, so likely oed_testing.<li>OED_DB_PASSWORD: The password for your postgres user.<li>OED_DB_HOST: The host for your postgres db, likely database where docker will set the needed value since database is the name of the service for the database.<li>OED_DB_PORT: The port for your postgres db, likely 5432.<li>OED_TOKEN_SECRET: Token for authentication. Generate something secure and random where you should never need to use this value.<li>OED_LOG_FILE: Path to the log file, defaults to ./log.txt.<li>OED_MAIL_METHOD: Method of sending mail. Supports "secure-smtp" and "none". Case insensitive.<li>OED_MAIL_IDENT: Username for gmail, domain for mailgun. Ex: user@example.com<li>OED_MAIL_CREDENTIAL: Password for gmail, or API key for mailgun.<li>OED_MAIL_FROM: From address for email. If using GMail, make sure this is set.<li>OED_MAIL_TO: Who gets error, warning (log) e-mail. Ex: admin@example.com<li>OED_MAIL_ORG: Organization name, used in e-mail subject line<li>TZ: Used to set the time zone on the OED server. This impacts the messages with timestamps from the server. By default this will be UTC.</ul></div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Environment Variables</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The OED server is configured via environment variables. These are normally set in the docker-compose.yml file located in the main OED directory. Developers generally do not need to change these values. Production installations generally do need to change some values as described in the installation directions. The environment variables are: OED_PRODUCTION: &#39;yes&#39; if running &quot;for realsies&quot; on a server (live site), &#39;no&#39; otherwise (normally development). OED_SERVER_PORT: The port that the server should run on. 3000 is a good default choice. OED_DB_USER: The user that should be used to connect to postgres. OED_DB_DATABASE: The database you just created, so likely oed. OED_DB_TEST_DATABASE: The test database you just created, so likely oed_testing. OED_DB_PASSWORD: The password for your postgres user. OED_DB_HOST: The host for your postgres db, likely database where docker will set the needed value since database is the name of the service for the database. OED_DB_PORT: The port for your postgres db, likely 5432. OED_TOKEN_SECRET: Token for authentication. Generate something secure and random where you should never need to use this value. OED_LOG_FILE: Path to the log file, defaults to ./log.txt. OED_MAIL_METHOD: Method of sending mail. Supports &quot;secure-smtp&quot; and &quot;none&quot;. Case insensitive. OED_MAIL_IDENT: Username for gmail, domain for mailgun. Ex: user@example.com OED_MAIL_CREDENTIAL: Password for gmail, or API key for mailgun. OED_MAIL_FROM: From address for email. If using GMail, make sure this is set. OED_MAIL_TO: Who gets error, warning (log) e-mail. Ex: admin@example.com OED_MAIL_ORG: Organization name, used in e-mail subject line TZ: Used to set the time zone on the OED server. This impacts the messages with timestamps from the server. By default this will be UTC."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/environment/"><meta property="og:title" content="Environment Variables"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The OED server is configured via environment variables. These are normally set in the docker-compose.yml file located in the main OED directory. Developers generally do not need to change these values. Production installations generally do need to change some values as described in the installation directions. The environment variables are: OED_PRODUCTION: &#39;yes&#39; if running &quot;for realsies&quot; on a server (live site), &#39;no&#39; otherwise (normally development). OED_SERVER_PORT: The port that the server should run on. 3000 is a good default choice. OED_DB_USER: The user that should be used to connect to postgres. OED_DB_DATABASE: The database you just created, so likely oed. OED_DB_TEST_DATABASE: The test database you just created, so likely oed_testing. OED_DB_PASSWORD: The password for your postgres user. OED_DB_HOST: The host for your postgres db, likely database where docker will set the needed value since database is the name of the service for the database. OED_DB_PORT: The port for your postgres db, likely 5432. OED_TOKEN_SECRET: Token for authentication. Generate something secure and random where you should never need to use this value. OED_LOG_FILE: Path to the log file, defaults to ./log.txt. OED_MAIL_METHOD: Method of sending mail. Supports &quot;secure-smtp&quot; and &quot;none&quot;. Case insensitive. OED_MAIL_IDENT: Username for gmail, domain for mailgun. Ex: user@example.com OED_MAIL_CREDENTIAL: Password for gmail, or API key for mailgun. OED_MAIL_FROM: From address for email. If using GMail, make sure this is set. OED_MAIL_TO: Who gets error, warning (log) e-mail. Ex: admin@example.com OED_MAIL_ORG: Organization name, used in e-mail subject line TZ: Used to set the time zone on the OED server. This impacts the messages with timestamps from the server. By default this will be UTC."><meta property="og:url" content="https://openenergydashboard.org/developer/environment/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Environment Variables</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Environment Variables</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>The OED server is configured via environment variables. These are normally set in the <code>docker-compose.yml</code> file located in the main OED directory. Developers generally do not need to change these values. Production installations generally do need to change some values as described in the <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">installation directions</a>.<p>The environment variables are:<ul><li>OED_PRODUCTION: 'yes' if running "for realsies" on a server (live site), 'no' otherwise (normally development).<li>OED_SERVER_PORT: The port that the server should run on. 3000 is a good default choice.<li>OED_DB_USER: The user that should be used to connect to postgres.<li>OED_DB_DATABASE: The database you just created, so likely oed.<li>OED_DB_TEST_DATABASE: The test database you just created, so likely oed_testing.<li>OED_DB_PASSWORD: The password for your postgres user.<li>OED_DB_HOST: The host for your postgres db, likely database where docker will set the needed value since database is the name of the service for the database.<li>OED_DB_PORT: The port for your postgres db, likely 5432.<li>OED_TOKEN_SECRET: Token for authentication. Generate something secure and random where you should never need to use this value.<li>OED_LOG_FILE: Path to the log file, defaults to ./log.txt.<li>OED_MAIL_METHOD: Method of sending mail. Supports "secure-smtp" and "none". Case insensitive.<li>OED_MAIL_IDENT: Username for gmail, domain for mailgun. Ex: user@example.com<li>OED_MAIL_CREDENTIAL: Password for gmail, or API key for mailgun.<li>OED_MAIL_FROM: From address for email. If using GMail, make sure this is set.<li>OED_MAIL_TO: Who gets error, warning (log) e-mail. Ex: admin@example.com<li>OED_MAIL_ORG: Organization name, used in e-mail subject line<li>TZ: Used to set the time zone on the OED server. This impacts the messages with timestamps from the server. By default this will be UTC.</ul></div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/fullInstallOutput/index.html b/developer/fullInstallOutput/index.html
index 6e7eaab9..3352a4be 100644
--- a/developer/fullInstallOutput/index.html
+++ b/developer/fullInstallOutput/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Full Install Output</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. When you install OED without already having a database or node modules, it does all the steps. Below is typical output for this process. This output is shown in the nohup.out file for a VSC install or in the terminal when doing docker compose up. Please note: The exact output will vary with machine type and changes to OED. This output was created on Windows 11 using WSL 2 in October 2023 outside VSC. The string &quot;oed&quot; reflects that it is in a directory with that name and one&#39;s output would change accordingly. The lines starting with &quot;oed-database |&quot; would be elsewhere when using the VSC OED container. One can see the output from the database install by right clicking on the database Docker container in the VSC Docker extension and choosing &quot;Show Logs&quot;. The output and information in install output without redoing database or npm install is similar to what will happen here. For unknown reasons, the OED install fails to run at times in VSC. See the no npm install output to see the known solution. nohup.out output [+] Building 3.2s (14/14) FINISHED docker:default =&gt; [database internal] load .dockerignore 0.0s =&gt; =&gt; transferring context: 2B 0.0s =&gt; [database internal] load build definition from Dockerfile 0.0s =&gt; =&gt; transferring dockerfile: 462B 0.0s =&gt; [database internal] load metadata for docker.io/library/postgres:15.3 2.1s =&gt; [database internal] load build context 0.0s =&gt; =&gt; transferring context: 858B 0.0s =&gt; [database 1/2] FROM docker.io/library/postgres:15.3@sha256:8775adb39f0db45cf4cdb3601380312ee5e9c4f53af0f89b7dc5cd4c9a78e4e8 0.0s =&gt; CACHED [database 2/2] COPY *.sql /docker-entrypoint-initdb.d/ 0.0s =&gt; [database] exporting to image 0.0s =&gt; =&gt; exporting layers 0.0s =&gt; =&gt; writing image sha256:b42a00751662cbff86856a54572e167e3eaaa7b9166ccd0433797af9f1005698 0.0s =&gt; =&gt; naming to docker.io/library/oed-database 0.0s =&gt; [web internal] load .dockerignore 0.0s =&gt; =&gt; transferring context: 300B 0.0s =&gt; [web internal] load build definition from Dockerfile 0.0s =&gt; =&gt; transferring dockerfile: 614B 0.0s =&gt; [web internal] load metadata for docker.io/library/node:18.17.1 0.6s =&gt; [web 1/3] FROM docker.io/library/node:18.17.1@sha256:933bcfad91e9052a02bc29eb5aa29033e542afac4174f9524b79066d97b23c24 0.0s =&gt; CACHED [web 2/3] RUN mkdir -p &quot;/usr/src/app&quot; 0.0s =&gt; CACHED [web 3/3] WORKDIR /usr/src/app 0.0s =&gt; [web] exporting to image 0.0s =&gt; =&gt; exporting layers 0.0s =&gt; =&gt; writing image sha256:43ec575d519a23888db44ba3fd4af8847b557a23d927ed22549c81c776244499 0.0s =&gt; =&gt; naming to docker.io/library/oed-web 0.0s [+] Running 3/3 ✔ Network oed_default Created 0.1s ✔ Container oed-database Created 0.2s ✔ Container oed-web Created 0.1s Attaching to oed-database, oed-web oed-database | The files belonging to this database system will be owned by user &quot;postgres&quot;. oed-database | This user must also own the server process. oed-database | oed-database | The database cluster will be initialized with locale &quot;en_US.utf8&quot;. oed-database | The default database encoding has accordingly been set to &quot;UTF8&quot;. oed-database | The default text search configuration will be set to &quot;english&quot;. oed-database | oed-database | Data page checksums are disabled. oed-database | oed-database | fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok oed-database | creating subdirectories ... ok oed-database | selecting dynamic shared memory implementation ... posix oed-database | selecting default max_connections ... 100 oed-database | selecting default shared_buffers ... 128MB oed-database | selecting default time zone ... Etc/UTC oed-database | creating configuration files ... ok oed-database | running bootstrap script ... ok oed-web | oed-web | oed-web | ***** Starting install of OED at Sun Oct 15 21:36:55 UTC 2023 ***** oed-web | oed-web | oed-web | NPM install... oed-web | oed-database | performing post-bootstrap initialization ... ok oed-database | initdb: warning: enabling &quot;trust&quot; authentication for local connections oed-database | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. oed-database | syncing data to disk ... ok oed-database | oed-database | oed-database | Success. You can now start the database server using: oed-database | oed-database | pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start oed-database | oed-database | waiting for server to start....2023-10-15 21:36:56.244 UTC [49] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database | 2023-10-15 21:36:56.249 UTC [49] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database | 2023-10-15 21:36:56.258 UTC [52] LOG: database system was shut down at 2023-10-15 21:36:55 UTC oed-database | 2023-10-15 21:36:56.264 UTC [49] LOG: database system is ready to accept connections oed-database | done oed-database | server started oed-database | oed-database | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init.sql oed-database | CREATE ROLE oed-database | DROP DATABASE oed-database | psql:/docker-entrypoint-initdb.d/init.sql:6: NOTICE: database &quot;oed&quot; does not exist, skipping oed-database | CREATE DATABASE oed-database | DROP DATABASE oed-database | psql:/docker-entrypoint-initdb.d/init.sql:8: NOTICE: database &quot;oed_testing&quot; does not exist, skipping oed-database | CREATE DATABASE oed-database | ALTER ROLE oed-database | oed-database | oed-database | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/nuke.sql oed-database | 2023-10-15 21:36:56.516 UTC [50] LOG: checkpoint starting: immediate force wait oed-database | 2023-10-15 21:36:56.640 UTC [50] LOG: checkpoint complete: wrote 927 buffers (5.7%); 1 WAL file(s) added, 0 removed, 0 recycled; write=0.016 s, sync=0.077 s, total=0.125 s; sync files=257, longest=0.012 s, average=0.001 s; distance=8450 kB, estimate=8450 kB oed-database | DROP DATABASE oed-database | 2023-10-15 21:36:56.647 UTC [50] LOG: checkpoint starting: immediate force wait oed-database | 2023-10-15 21:36:56.665 UTC [50] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.004 s, total=0.018 s; sync files=3, longest=0.003 s, average=0.002 s; distance=1 kB, estimate=7605 kB oed-database | DROP DATABASE oed-database | CREATE DATABASE oed-database | CREATE DATABASE oed-database | oed-database | oed-database | waiting for server to shut down...2023-10-15 21:36:56.749 UTC [49] LOG: received fast shutdown request oed-database | .2023-10-15 21:36:56.752 UTC [49] LOG: aborting any active transactions oed-database | 2023-10-15 21:36:56.754 UTC [49] LOG: background worker &quot;logical replication launcher&quot; (PID 55) exited with exit code 1 oed-database | 2023-10-15 21:36:56.754 UTC [50] LOG: shutting down oed-database | 2023-10-15 21:36:56.757 UTC [50] LOG: checkpoint starting: shutdown immediate oed-database | 2023-10-15 21:36:56.940 UTC [50] LOG: checkpoint complete: wrote 1832 buffers (11.2%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.034 s, sync=0.140 s, total=0.186 s; sync files=498, longest=0.007 s, average=0.001 s; distance=8447 kB, estimate=8447 kB oed-database | 2023-10-15 21:36:56.946 UTC [49] LOG: database system is shut down oed-database | done oed-database | server stopped oed-database | oed-database | PostgreSQL init process complete; ready for start up. oed-database | oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: listening on IPv4 address &quot;0.0.0.0&quot;, port 5432 oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: listening on IPv6 address &quot;::&quot;, port 5432 oed-database | 2023-10-15 21:36:56.979 UTC [1] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database | 2023-10-15 21:36:56.985 UTC [67] LOG: database system was shut down at 2023-10-15 21:36:56 UTC oed-database | 2023-10-15 21:36:56.992 UTC [1] LOG: database system is ready to accept connections oed-web | npm WARN deprecated multer@1.3.1: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. oed-web | npm WARN deprecated mumath@3.3.4: Redundant dependency in your project. oed-web | npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau oed-web | npm WARN deprecated superagent@3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at &amp;lt;https://github.com/visionmedia/superagent/releases&amp;gt;. oed-web | npm WARN deprecated core-js@2.6.12: core-js@&amp;lt;3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. oed-web | oed-web | added 1166 packages, and audited 1167 packages in 31s oed-web | oed-web | 111 packages are looking for funding oed-web | run `npm fund` for details oed-web | oed-web | 7 vulnerabilities (4 moderate, 3 high) oed-web | oed-web | To address issues that do not require attention, run: oed-web | npm audit fix oed-web | oed-web | To address all issues possible (including breaking changes), run: oed-web | npm audit fix --force oed-web | oed-web | Some issues need review, and may require choosing oed-web | a different dependency. oed-web | oed-web | Run `npm audit` for details. oed-web | npm notice oed-web | npm notice New major version of npm available! 9.6.7 -&gt; 10.2.0 oed-web | npm notice Changelog: &amp;lt;https://github.com/npm/cli/releases/tag/v10.2.0&amp;gt; oed-web | npm notice Run `npm install -g npm@10.2.0` to update! oed-web | npm notice oed-web | oed-web | NPM install finished. oed-web | oed-web | Attempting to create database... oed-web | oed-web | -----start of npm run createdb output----- oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 createdb oed-web | &gt; node ./src/server/services/createDB.js oed-web | oed-web | [WARN@2023-10-15T21:37:34.894+00:00] Automatically set identifier of the unit &quot;kWh&quot; to &quot;kWh&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.936+00:00] Automatically set identifier of the unit &quot;metric ton&quot; to &quot;metric ton&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.941+00:00] Automatically set identifier of the unit &quot;gallon&quot; to &quot;gallon&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.942+00:00] Automatically set identifier of the unit &quot;kg&quot; to &quot;kg&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.944+00:00] Automatically set identifier of the unit &quot;Fahrenheit&quot; to &quot;Fahrenheit&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.945+00:00] Automatically set identifier of the unit &quot;m³ gas&quot; to &quot;m³ gas&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.946+00:00] Automatically set identifier of the unit &quot;BTU&quot; to &quot;BTU&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.947+00:00] Automatically set identifier of the unit &quot;Electric_Utility&quot; to &quot;Electric_Utility&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.947+00:00] Automatically set identifier of the unit &quot;Celsius&quot; to &quot;Celsius&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.952+00:00] Automatically set identifier of the unit &quot;liter&quot; to &quot;liter&quot; oed-web | oed-web | -----end of npm run createdb output----- oed-web | oed-web | database creation had no errors so assume schema creation worked. oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 createUser oed-web | &gt; node ./src/server/services/user/createUser.js test@example.com password oed-web | oed-web | [INFO@2023-10-15T21:37:46.142+00:00] User test@example.com created oed-web | oed-web | User creation had no errors so default user &#39;test@example.com&#39; with password &#39;password&#39; should exist oed-web | Creating developer DB function oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 developerdb oed-web | &gt; node -e &#39;require(&quot;./src/server/util/developer.js&quot;).createShiftReadingsFunction()&#39; oed-web | oed-web | OED install finished oed-web | Starting OED in development mode oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 webpack:dev oed-web | &gt; webpack watch --color --progress --mode development oed-web | oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 start:dev oed-web | &gt; nodemon --legacy-watch --inspect=0.0.0.0 ./src/bin/www oed-web | oed-web | [nodemon] 2.0.22 oed-web | [nodemon] to restart at any time, enter `rs` oed-web | [nodemon] watching path(s): src/server/**/* src/bin/**/* src/common/**/* oed-web | [nodemon] watching extensions: js,mjs,json oed-web | [nodemon] starting `node --inspect=0.0.0.0 ./src/bin/www` oed-web | Debugger listening on ws://0.0.0.0:9229/8f986c6b-88ca-4b76-9b3f-eb6e77a84041 oed-web | For help, see: https://nodejs.org/en/docs/inspector oed-web | [INFO@2023-10-15T21:37:58.120+00:00] Listening on port 3000 oed-web | oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run webpack-cli oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory LodashModuleReplacementPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile ProgressPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile ExternalsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation WorkerPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation SplitChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ResolverCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProgressPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProvidePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ModuleInfoHeaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JsonModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AssetModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EntryPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RuntimePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DataUriPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FileUriPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CompatibilityPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation HarmonyModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AMDPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireJsStuffPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CommonJsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NodeStuffPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation APIPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ConstPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation UseStrictPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireIncludePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireEnsurePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SystemPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportMetaPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation URLPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedModuleIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedChunkIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefinePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation TemplatedPathPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/ts-loader/index.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/1 dependencies 0/1 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/2 dependencies 0/1 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/style-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/css-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 10/33 dependencies 0/9 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/source-map-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 48/52 dependencies 0/38 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 48/100 dependencies 0/38 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 78/138 dependencies 2/62 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 194/234 dependencies 34/101 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 231/261 dependencies 43/108 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 399/500 dependencies 49/160 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 442/790 dependencies 54/200 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 858/900 dependencies 64/355 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 11% building 0/1 entries 1200/1273 dependencies 151/466 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1400/1450 dependencies 235/492 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1418/1500 dependencies 238/494 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1800/1898 dependencies 260/533 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 2011/2100 dependencies 263/549 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 15% building 0/1 entries 2475/2500 dependencies 476/668 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 15% building 0/1 entries 2700/2773 dependencies 542/763 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 16% building 0/1 entries 2843/2890 dependencies 600/779 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 17% building 0/1 entries 3032/3100 dependencies 685/858 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 65% building 1/1 entries 3747/3747 dependencies 1071/1071 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 65% building oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph ResolverCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph InferAsyncModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph FlagDependencyExportsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins WarnCaseSensitiveModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization SideEffectsFlagPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization EnsureChunkConditionsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization MergeDuplicateChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization SplitChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids NamedModuleIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids NamedChunkIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing ts-loader oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js generate SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js generated SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js attach SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js attached SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit SizeLimitsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% oed-web | oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web | oed-web | asset bundle.js 15.4 MiB [emitted] [big] (name: application) 1 related asset oed-web | orphan modules 236 KiB [orphan] 128 modules oed-web | runtime modules 1.7 KiB 8 modules oed-web | modules by path ./node_modules/ 13.2 MiB 756 modules oed-web | modules by path ./src/ 1.2 MiB 171 modules oed-web | asset modules 4.4 KiB oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 181 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 165 bytes [built] [code generated] oed-web | + 10 modules oed-web | webpack 5.76.3 compiled successfully in 29752 ms"><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/fullInstallOutput/"><meta property="og:title" content="Full Install Output"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. When you install OED without already having a database or node modules, it does all the steps. Below is typical output for this process. This output is shown in the nohup.out file for a VSC install or in the terminal when doing docker compose up. Please note: The exact output will vary with machine type and changes to OED. This output was created on Windows 11 using WSL 2 in October 2023 outside VSC. The string &quot;oed&quot; reflects that it is in a directory with that name and one&#39;s output would change accordingly. The lines starting with &quot;oed-database |&quot; would be elsewhere when using the VSC OED container. One can see the output from the database install by right clicking on the database Docker container in the VSC Docker extension and choosing &quot;Show Logs&quot;. The output and information in install output without redoing database or npm install is similar to what will happen here. For unknown reasons, the OED install fails to run at times in VSC. See the no npm install output to see the known solution. nohup.out output [+] Building 3.2s (14/14) FINISHED docker:default =&gt; [database internal] load .dockerignore 0.0s =&gt; =&gt; transferring context: 2B 0.0s =&gt; [database internal] load build definition from Dockerfile 0.0s =&gt; =&gt; transferring dockerfile: 462B 0.0s =&gt; [database internal] load metadata for docker.io/library/postgres:15.3 2.1s =&gt; [database internal] load build context 0.0s =&gt; =&gt; transferring context: 858B 0.0s =&gt; [database 1/2] FROM docker.io/library/postgres:15.3@sha256:8775adb39f0db45cf4cdb3601380312ee5e9c4f53af0f89b7dc5cd4c9a78e4e8 0.0s =&gt; CACHED [database 2/2] COPY *.sql /docker-entrypoint-initdb.d/ 0.0s =&gt; [database] exporting to image 0.0s =&gt; =&gt; exporting layers 0.0s =&gt; =&gt; writing image sha256:b42a00751662cbff86856a54572e167e3eaaa7b9166ccd0433797af9f1005698 0.0s =&gt; =&gt; naming to docker.io/library/oed-database 0.0s =&gt; [web internal] load .dockerignore 0.0s =&gt; =&gt; transferring context: 300B 0.0s =&gt; [web internal] load build definition from Dockerfile 0.0s =&gt; =&gt; transferring dockerfile: 614B 0.0s =&gt; [web internal] load metadata for docker.io/library/node:18.17.1 0.6s =&gt; [web 1/3] FROM docker.io/library/node:18.17.1@sha256:933bcfad91e9052a02bc29eb5aa29033e542afac4174f9524b79066d97b23c24 0.0s =&gt; CACHED [web 2/3] RUN mkdir -p &quot;/usr/src/app&quot; 0.0s =&gt; CACHED [web 3/3] WORKDIR /usr/src/app 0.0s =&gt; [web] exporting to image 0.0s =&gt; =&gt; exporting layers 0.0s =&gt; =&gt; writing image sha256:43ec575d519a23888db44ba3fd4af8847b557a23d927ed22549c81c776244499 0.0s =&gt; =&gt; naming to docker.io/library/oed-web 0.0s [+] Running 3/3 ✔ Network oed_default Created 0.1s ✔ Container oed-database Created 0.2s ✔ Container oed-web Created 0.1s Attaching to oed-database, oed-web oed-database | The files belonging to this database system will be owned by user &quot;postgres&quot;. oed-database | This user must also own the server process. oed-database | oed-database | The database cluster will be initialized with locale &quot;en_US.utf8&quot;. oed-database | The default database encoding has accordingly been set to &quot;UTF8&quot;. oed-database | The default text search configuration will be set to &quot;english&quot;. oed-database | oed-database | Data page checksums are disabled. oed-database | oed-database | fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok oed-database | creating subdirectories ... ok oed-database | selecting dynamic shared memory implementation ... posix oed-database | selecting default max_connections ... 100 oed-database | selecting default shared_buffers ... 128MB oed-database | selecting default time zone ... Etc/UTC oed-database | creating configuration files ... ok oed-database | running bootstrap script ... ok oed-web | oed-web | oed-web | ***** Starting install of OED at Sun Oct 15 21:36:55 UTC 2023 ***** oed-web | oed-web | oed-web | NPM install... oed-web | oed-database | performing post-bootstrap initialization ... ok oed-database | initdb: warning: enabling &quot;trust&quot; authentication for local connections oed-database | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. oed-database | syncing data to disk ... ok oed-database | oed-database | oed-database | Success. You can now start the database server using: oed-database | oed-database | pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start oed-database | oed-database | waiting for server to start....2023-10-15 21:36:56.244 UTC [49] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database | 2023-10-15 21:36:56.249 UTC [49] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database | 2023-10-15 21:36:56.258 UTC [52] LOG: database system was shut down at 2023-10-15 21:36:55 UTC oed-database | 2023-10-15 21:36:56.264 UTC [49] LOG: database system is ready to accept connections oed-database | done oed-database | server started oed-database | oed-database | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init.sql oed-database | CREATE ROLE oed-database | DROP DATABASE oed-database | psql:/docker-entrypoint-initdb.d/init.sql:6: NOTICE: database &quot;oed&quot; does not exist, skipping oed-database | CREATE DATABASE oed-database | DROP DATABASE oed-database | psql:/docker-entrypoint-initdb.d/init.sql:8: NOTICE: database &quot;oed_testing&quot; does not exist, skipping oed-database | CREATE DATABASE oed-database | ALTER ROLE oed-database | oed-database | oed-database | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/nuke.sql oed-database | 2023-10-15 21:36:56.516 UTC [50] LOG: checkpoint starting: immediate force wait oed-database | 2023-10-15 21:36:56.640 UTC [50] LOG: checkpoint complete: wrote 927 buffers (5.7%); 1 WAL file(s) added, 0 removed, 0 recycled; write=0.016 s, sync=0.077 s, total=0.125 s; sync files=257, longest=0.012 s, average=0.001 s; distance=8450 kB, estimate=8450 kB oed-database | DROP DATABASE oed-database | 2023-10-15 21:36:56.647 UTC [50] LOG: checkpoint starting: immediate force wait oed-database | 2023-10-15 21:36:56.665 UTC [50] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.004 s, total=0.018 s; sync files=3, longest=0.003 s, average=0.002 s; distance=1 kB, estimate=7605 kB oed-database | DROP DATABASE oed-database | CREATE DATABASE oed-database | CREATE DATABASE oed-database | oed-database | oed-database | waiting for server to shut down...2023-10-15 21:36:56.749 UTC [49] LOG: received fast shutdown request oed-database | .2023-10-15 21:36:56.752 UTC [49] LOG: aborting any active transactions oed-database | 2023-10-15 21:36:56.754 UTC [49] LOG: background worker &quot;logical replication launcher&quot; (PID 55) exited with exit code 1 oed-database | 2023-10-15 21:36:56.754 UTC [50] LOG: shutting down oed-database | 2023-10-15 21:36:56.757 UTC [50] LOG: checkpoint starting: shutdown immediate oed-database | 2023-10-15 21:36:56.940 UTC [50] LOG: checkpoint complete: wrote 1832 buffers (11.2%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.034 s, sync=0.140 s, total=0.186 s; sync files=498, longest=0.007 s, average=0.001 s; distance=8447 kB, estimate=8447 kB oed-database | 2023-10-15 21:36:56.946 UTC [49] LOG: database system is shut down oed-database | done oed-database | server stopped oed-database | oed-database | PostgreSQL init process complete; ready for start up. oed-database | oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: listening on IPv4 address &quot;0.0.0.0&quot;, port 5432 oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: listening on IPv6 address &quot;::&quot;, port 5432 oed-database | 2023-10-15 21:36:56.979 UTC [1] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database | 2023-10-15 21:36:56.985 UTC [67] LOG: database system was shut down at 2023-10-15 21:36:56 UTC oed-database | 2023-10-15 21:36:56.992 UTC [1] LOG: database system is ready to accept connections oed-web | npm WARN deprecated multer@1.3.1: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. oed-web | npm WARN deprecated mumath@3.3.4: Redundant dependency in your project. oed-web | npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau oed-web | npm WARN deprecated superagent@3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at &amp;lt;https://github.com/visionmedia/superagent/releases&amp;gt;. oed-web | npm WARN deprecated core-js@2.6.12: core-js@&amp;lt;3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. oed-web | oed-web | added 1166 packages, and audited 1167 packages in 31s oed-web | oed-web | 111 packages are looking for funding oed-web | run `npm fund` for details oed-web | oed-web | 7 vulnerabilities (4 moderate, 3 high) oed-web | oed-web | To address issues that do not require attention, run: oed-web | npm audit fix oed-web | oed-web | To address all issues possible (including breaking changes), run: oed-web | npm audit fix --force oed-web | oed-web | Some issues need review, and may require choosing oed-web | a different dependency. oed-web | oed-web | Run `npm audit` for details. oed-web | npm notice oed-web | npm notice New major version of npm available! 9.6.7 -&gt; 10.2.0 oed-web | npm notice Changelog: &amp;lt;https://github.com/npm/cli/releases/tag/v10.2.0&amp;gt; oed-web | npm notice Run `npm install -g npm@10.2.0` to update! oed-web | npm notice oed-web | oed-web | NPM install finished. oed-web | oed-web | Attempting to create database... oed-web | oed-web | -----start of npm run createdb output----- oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 createdb oed-web | &gt; node ./src/server/services/createDB.js oed-web | oed-web | [WARN@2023-10-15T21:37:34.894+00:00] Automatically set identifier of the unit &quot;kWh&quot; to &quot;kWh&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.936+00:00] Automatically set identifier of the unit &quot;metric ton&quot; to &quot;metric ton&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.941+00:00] Automatically set identifier of the unit &quot;gallon&quot; to &quot;gallon&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.942+00:00] Automatically set identifier of the unit &quot;kg&quot; to &quot;kg&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.944+00:00] Automatically set identifier of the unit &quot;Fahrenheit&quot; to &quot;Fahrenheit&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.945+00:00] Automatically set identifier of the unit &quot;m³ gas&quot; to &quot;m³ gas&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.946+00:00] Automatically set identifier of the unit &quot;BTU&quot; to &quot;BTU&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.947+00:00] Automatically set identifier of the unit &quot;Electric_Utility&quot; to &quot;Electric_Utility&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.947+00:00] Automatically set identifier of the unit &quot;Celsius&quot; to &quot;Celsius&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.952+00:00] Automatically set identifier of the unit &quot;liter&quot; to &quot;liter&quot; oed-web | oed-web | -----end of npm run createdb output----- oed-web | oed-web | database creation had no errors so assume schema creation worked. oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 createUser oed-web | &gt; node ./src/server/services/user/createUser.js test@example.com password oed-web | oed-web | [INFO@2023-10-15T21:37:46.142+00:00] User test@example.com created oed-web | oed-web | User creation had no errors so default user &#39;test@example.com&#39; with password &#39;password&#39; should exist oed-web | Creating developer DB function oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 developerdb oed-web | &gt; node -e &#39;require(&quot;./src/server/util/developer.js&quot;).createShiftReadingsFunction()&#39; oed-web | oed-web | OED install finished oed-web | Starting OED in development mode oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 webpack:dev oed-web | &gt; webpack watch --color --progress --mode development oed-web | oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 start:dev oed-web | &gt; nodemon --legacy-watch --inspect=0.0.0.0 ./src/bin/www oed-web | oed-web | [nodemon] 2.0.22 oed-web | [nodemon] to restart at any time, enter `rs` oed-web | [nodemon] watching path(s): src/server/**/* src/bin/**/* src/common/**/* oed-web | [nodemon] watching extensions: js,mjs,json oed-web | [nodemon] starting `node --inspect=0.0.0.0 ./src/bin/www` oed-web | Debugger listening on ws://0.0.0.0:9229/8f986c6b-88ca-4b76-9b3f-eb6e77a84041 oed-web | For help, see: https://nodejs.org/en/docs/inspector oed-web | [INFO@2023-10-15T21:37:58.120+00:00] Listening on port 3000 oed-web | oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run webpack-cli oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory LodashModuleReplacementPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile ProgressPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile ExternalsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation WorkerPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation SplitChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ResolverCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProgressPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProvidePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ModuleInfoHeaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JsonModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AssetModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EntryPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RuntimePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DataUriPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FileUriPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CompatibilityPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation HarmonyModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AMDPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireJsStuffPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CommonJsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NodeStuffPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation APIPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ConstPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation UseStrictPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireIncludePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireEnsurePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SystemPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportMetaPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation URLPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedModuleIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedChunkIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefinePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation TemplatedPathPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/ts-loader/index.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/1 dependencies 0/1 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/2 dependencies 0/1 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/style-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/css-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 10/33 dependencies 0/9 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/source-map-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 48/52 dependencies 0/38 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 48/100 dependencies 0/38 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 78/138 dependencies 2/62 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 194/234 dependencies 34/101 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 231/261 dependencies 43/108 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 399/500 dependencies 49/160 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 442/790 dependencies 54/200 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 858/900 dependencies 64/355 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 11% building 0/1 entries 1200/1273 dependencies 151/466 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1400/1450 dependencies 235/492 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1418/1500 dependencies 238/494 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1800/1898 dependencies 260/533 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 2011/2100 dependencies 263/549 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 15% building 0/1 entries 2475/2500 dependencies 476/668 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 15% building 0/1 entries 2700/2773 dependencies 542/763 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 16% building 0/1 entries 2843/2890 dependencies 600/779 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 17% building 0/1 entries 3032/3100 dependencies 685/858 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 65% building 1/1 entries 3747/3747 dependencies 1071/1071 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 65% building oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph ResolverCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph InferAsyncModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph FlagDependencyExportsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins WarnCaseSensitiveModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization SideEffectsFlagPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization EnsureChunkConditionsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization MergeDuplicateChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization SplitChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids NamedModuleIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids NamedChunkIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing ts-loader oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js generate SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js generated SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js attach SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js attached SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit SizeLimitsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% oed-web | oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web | oed-web | asset bundle.js 15.4 MiB [emitted] [big] (name: application) 1 related asset oed-web | orphan modules 236 KiB [orphan] 128 modules oed-web | runtime modules 1.7 KiB 8 modules oed-web | modules by path ./node_modules/ 13.2 MiB 756 modules oed-web | modules by path ./src/ 1.2 MiB 171 modules oed-web | asset modules 4.4 KiB oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 181 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 165 bytes [built] [code generated] oed-web | + 10 modules oed-web | webpack 5.76.3 compiled successfully in 29752 ms"><meta property="og:url" content="https://openenergydashboard.org/developer/fullInstallOutput/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Full Install Output</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Full Install Output</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>When you install OED without already having a database or node modules, it does all the steps. Below is typical output for this process. This output is shown in the nohup.out file for a VSC install or in the terminal when doing <code>docker compose up</code>. Please note:<ul><li>The exact output will vary with machine type and changes to OED. This output was created on Windows 11 using WSL 2 in October 2023 outside VSC. The string "oed" reflects that it is in a directory with that name and one's output would change accordingly.<li>The lines starting with "oed-database |" would be elsewhere when using the VSC OED container. One can see the output from the database install by right clicking on the database Docker container in the VSC Docker extension and choosing "Show Logs".<li>The output and information in <a href="../noNPMInstallOutput/">install output without redoing database or npm install</a> is similar to what will happen here.<li>For unknown reasons, the OED install fails to run at times in VSC. See the <a href="../noNPMInstallOutput/">no npm install output</a> to see the known solution.</ul><h3>nohup.out output</h3><pre>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Full Install Output</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. When you install OED without already having a database or node modules, it does all the steps. Below is typical output for this process. This output is shown in the nohup.out file for a VSC install or in the terminal when doing docker compose up. Please note: The exact output will vary with machine type and changes to OED. This output was created on Windows 11 using WSL 2 in October 2023 outside VSC. The string &quot;oed&quot; reflects that it is in a directory with that name and one&#39;s output would change accordingly. The lines starting with &quot;oed-database |&quot; would be elsewhere when using the VSC OED container. One can see the output from the database install by right clicking on the database Docker container in the VSC Docker extension and choosing &quot;Show Logs&quot;. The output and information in install output without redoing database or npm install is similar to what will happen here. For unknown reasons, the OED install fails to run at times in VSC. See the no npm install output to see the known solution. nohup.out output [+] Building 3.2s (14/14) FINISHED docker:default =&gt; [database internal] load .dockerignore 0.0s =&gt; =&gt; transferring context: 2B 0.0s =&gt; [database internal] load build definition from Dockerfile 0.0s =&gt; =&gt; transferring dockerfile: 462B 0.0s =&gt; [database internal] load metadata for docker.io/library/postgres:15.3 2.1s =&gt; [database internal] load build context 0.0s =&gt; =&gt; transferring context: 858B 0.0s =&gt; [database 1/2] FROM docker.io/library/postgres:15.3@sha256:8775adb39f0db45cf4cdb3601380312ee5e9c4f53af0f89b7dc5cd4c9a78e4e8 0.0s =&gt; CACHED [database 2/2] COPY *.sql /docker-entrypoint-initdb.d/ 0.0s =&gt; [database] exporting to image 0.0s =&gt; =&gt; exporting layers 0.0s =&gt; =&gt; writing image sha256:b42a00751662cbff86856a54572e167e3eaaa7b9166ccd0433797af9f1005698 0.0s =&gt; =&gt; naming to docker.io/library/oed-database 0.0s =&gt; [web internal] load .dockerignore 0.0s =&gt; =&gt; transferring context: 300B 0.0s =&gt; [web internal] load build definition from Dockerfile 0.0s =&gt; =&gt; transferring dockerfile: 614B 0.0s =&gt; [web internal] load metadata for docker.io/library/node:18.17.1 0.6s =&gt; [web 1/3] FROM docker.io/library/node:18.17.1@sha256:933bcfad91e9052a02bc29eb5aa29033e542afac4174f9524b79066d97b23c24 0.0s =&gt; CACHED [web 2/3] RUN mkdir -p &quot;/usr/src/app&quot; 0.0s =&gt; CACHED [web 3/3] WORKDIR /usr/src/app 0.0s =&gt; [web] exporting to image 0.0s =&gt; =&gt; exporting layers 0.0s =&gt; =&gt; writing image sha256:43ec575d519a23888db44ba3fd4af8847b557a23d927ed22549c81c776244499 0.0s =&gt; =&gt; naming to docker.io/library/oed-web 0.0s [+] Running 3/3 ✔ Network oed_default Created 0.1s ✔ Container oed-database Created 0.2s ✔ Container oed-web Created 0.1s Attaching to oed-database, oed-web oed-database | The files belonging to this database system will be owned by user &quot;postgres&quot;. oed-database | This user must also own the server process. oed-database | oed-database | The database cluster will be initialized with locale &quot;en_US.utf8&quot;. oed-database | The default database encoding has accordingly been set to &quot;UTF8&quot;. oed-database | The default text search configuration will be set to &quot;english&quot;. oed-database | oed-database | Data page checksums are disabled. oed-database | oed-database | fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok oed-database | creating subdirectories ... ok oed-database | selecting dynamic shared memory implementation ... posix oed-database | selecting default max_connections ... 100 oed-database | selecting default shared_buffers ... 128MB oed-database | selecting default time zone ... Etc/UTC oed-database | creating configuration files ... ok oed-database | running bootstrap script ... ok oed-web | oed-web | oed-web | ***** Starting install of OED at Sun Oct 15 21:36:55 UTC 2023 ***** oed-web | oed-web | oed-web | NPM install... oed-web | oed-database | performing post-bootstrap initialization ... ok oed-database | initdb: warning: enabling &quot;trust&quot; authentication for local connections oed-database | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. oed-database | syncing data to disk ... ok oed-database | oed-database | oed-database | Success. You can now start the database server using: oed-database | oed-database | pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start oed-database | oed-database | waiting for server to start....2023-10-15 21:36:56.244 UTC [49] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database | 2023-10-15 21:36:56.249 UTC [49] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database | 2023-10-15 21:36:56.258 UTC [52] LOG: database system was shut down at 2023-10-15 21:36:55 UTC oed-database | 2023-10-15 21:36:56.264 UTC [49] LOG: database system is ready to accept connections oed-database | done oed-database | server started oed-database | oed-database | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init.sql oed-database | CREATE ROLE oed-database | DROP DATABASE oed-database | psql:/docker-entrypoint-initdb.d/init.sql:6: NOTICE: database &quot;oed&quot; does not exist, skipping oed-database | CREATE DATABASE oed-database | DROP DATABASE oed-database | psql:/docker-entrypoint-initdb.d/init.sql:8: NOTICE: database &quot;oed_testing&quot; does not exist, skipping oed-database | CREATE DATABASE oed-database | ALTER ROLE oed-database | oed-database | oed-database | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/nuke.sql oed-database | 2023-10-15 21:36:56.516 UTC [50] LOG: checkpoint starting: immediate force wait oed-database | 2023-10-15 21:36:56.640 UTC [50] LOG: checkpoint complete: wrote 927 buffers (5.7%); 1 WAL file(s) added, 0 removed, 0 recycled; write=0.016 s, sync=0.077 s, total=0.125 s; sync files=257, longest=0.012 s, average=0.001 s; distance=8450 kB, estimate=8450 kB oed-database | DROP DATABASE oed-database | 2023-10-15 21:36:56.647 UTC [50] LOG: checkpoint starting: immediate force wait oed-database | 2023-10-15 21:36:56.665 UTC [50] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.004 s, total=0.018 s; sync files=3, longest=0.003 s, average=0.002 s; distance=1 kB, estimate=7605 kB oed-database | DROP DATABASE oed-database | CREATE DATABASE oed-database | CREATE DATABASE oed-database | oed-database | oed-database | waiting for server to shut down...2023-10-15 21:36:56.749 UTC [49] LOG: received fast shutdown request oed-database | .2023-10-15 21:36:56.752 UTC [49] LOG: aborting any active transactions oed-database | 2023-10-15 21:36:56.754 UTC [49] LOG: background worker &quot;logical replication launcher&quot; (PID 55) exited with exit code 1 oed-database | 2023-10-15 21:36:56.754 UTC [50] LOG: shutting down oed-database | 2023-10-15 21:36:56.757 UTC [50] LOG: checkpoint starting: shutdown immediate oed-database | 2023-10-15 21:36:56.940 UTC [50] LOG: checkpoint complete: wrote 1832 buffers (11.2%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.034 s, sync=0.140 s, total=0.186 s; sync files=498, longest=0.007 s, average=0.001 s; distance=8447 kB, estimate=8447 kB oed-database | 2023-10-15 21:36:56.946 UTC [49] LOG: database system is shut down oed-database | done oed-database | server stopped oed-database | oed-database | PostgreSQL init process complete; ready for start up. oed-database | oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: listening on IPv4 address &quot;0.0.0.0&quot;, port 5432 oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: listening on IPv6 address &quot;::&quot;, port 5432 oed-database | 2023-10-15 21:36:56.979 UTC [1] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database | 2023-10-15 21:36:56.985 UTC [67] LOG: database system was shut down at 2023-10-15 21:36:56 UTC oed-database | 2023-10-15 21:36:56.992 UTC [1] LOG: database system is ready to accept connections oed-web | npm WARN deprecated multer@1.3.1: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. oed-web | npm WARN deprecated mumath@3.3.4: Redundant dependency in your project. oed-web | npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau oed-web | npm WARN deprecated superagent@3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at &amp;lt;https://github.com/visionmedia/superagent/releases&amp;gt;. oed-web | npm WARN deprecated core-js@2.6.12: core-js@&amp;lt;3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. oed-web | oed-web | added 1166 packages, and audited 1167 packages in 31s oed-web | oed-web | 111 packages are looking for funding oed-web | run `npm fund` for details oed-web | oed-web | 7 vulnerabilities (4 moderate, 3 high) oed-web | oed-web | To address issues that do not require attention, run: oed-web | npm audit fix oed-web | oed-web | To address all issues possible (including breaking changes), run: oed-web | npm audit fix --force oed-web | oed-web | Some issues need review, and may require choosing oed-web | a different dependency. oed-web | oed-web | Run `npm audit` for details. oed-web | npm notice oed-web | npm notice New major version of npm available! 9.6.7 -&gt; 10.2.0 oed-web | npm notice Changelog: &amp;lt;https://github.com/npm/cli/releases/tag/v10.2.0&amp;gt; oed-web | npm notice Run `npm install -g npm@10.2.0` to update! oed-web | npm notice oed-web | oed-web | NPM install finished. oed-web | oed-web | Attempting to create database... oed-web | oed-web | -----start of npm run createdb output----- oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 createdb oed-web | &gt; node ./src/server/services/createDB.js oed-web | oed-web | [WARN@2023-10-15T21:37:34.894+00:00] Automatically set identifier of the unit &quot;kWh&quot; to &quot;kWh&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.936+00:00] Automatically set identifier of the unit &quot;metric ton&quot; to &quot;metric ton&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.941+00:00] Automatically set identifier of the unit &quot;gallon&quot; to &quot;gallon&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.942+00:00] Automatically set identifier of the unit &quot;kg&quot; to &quot;kg&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.944+00:00] Automatically set identifier of the unit &quot;Fahrenheit&quot; to &quot;Fahrenheit&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.945+00:00] Automatically set identifier of the unit &quot;m³ gas&quot; to &quot;m³ gas&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.946+00:00] Automatically set identifier of the unit &quot;BTU&quot; to &quot;BTU&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.947+00:00] Automatically set identifier of the unit &quot;Electric_Utility&quot; to &quot;Electric_Utility&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.947+00:00] Automatically set identifier of the unit &quot;Celsius&quot; to &quot;Celsius&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.952+00:00] Automatically set identifier of the unit &quot;liter&quot; to &quot;liter&quot; oed-web | oed-web | -----end of npm run createdb output----- oed-web | oed-web | database creation had no errors so assume schema creation worked. oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 createUser oed-web | &gt; node ./src/server/services/user/createUser.js test@example.com password oed-web | oed-web | [INFO@2023-10-15T21:37:46.142+00:00] User test@example.com created oed-web | oed-web | User creation had no errors so default user &#39;test@example.com&#39; with password &#39;password&#39; should exist oed-web | Creating developer DB function oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 developerdb oed-web | &gt; node -e &#39;require(&quot;./src/server/util/developer.js&quot;).createShiftReadingsFunction()&#39; oed-web | oed-web | OED install finished oed-web | Starting OED in development mode oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 webpack:dev oed-web | &gt; webpack watch --color --progress --mode development oed-web | oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 start:dev oed-web | &gt; nodemon --legacy-watch --inspect=0.0.0.0 ./src/bin/www oed-web | oed-web | [nodemon] 2.0.22 oed-web | [nodemon] to restart at any time, enter `rs` oed-web | [nodemon] watching path(s): src/server/**/* src/bin/**/* src/common/**/* oed-web | [nodemon] watching extensions: js,mjs,json oed-web | [nodemon] starting `node --inspect=0.0.0.0 ./src/bin/www` oed-web | Debugger listening on ws://0.0.0.0:9229/8f986c6b-88ca-4b76-9b3f-eb6e77a84041 oed-web | For help, see: https://nodejs.org/en/docs/inspector oed-web | [INFO@2023-10-15T21:37:58.120+00:00] Listening on port 3000 oed-web | oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run webpack-cli oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory LodashModuleReplacementPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile ProgressPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile ExternalsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation WorkerPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation SplitChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ResolverCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProgressPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProvidePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ModuleInfoHeaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JsonModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AssetModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EntryPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RuntimePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DataUriPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FileUriPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CompatibilityPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation HarmonyModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AMDPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireJsStuffPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CommonJsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NodeStuffPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation APIPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ConstPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation UseStrictPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireIncludePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireEnsurePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SystemPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportMetaPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation URLPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedModuleIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedChunkIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefinePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation TemplatedPathPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/ts-loader/index.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/1 dependencies 0/1 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/2 dependencies 0/1 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/style-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/css-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 10/33 dependencies 0/9 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/source-map-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 48/52 dependencies 0/38 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 48/100 dependencies 0/38 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 78/138 dependencies 2/62 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 194/234 dependencies 34/101 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 231/261 dependencies 43/108 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 399/500 dependencies 49/160 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 442/790 dependencies 54/200 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 858/900 dependencies 64/355 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 11% building 0/1 entries 1200/1273 dependencies 151/466 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1400/1450 dependencies 235/492 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1418/1500 dependencies 238/494 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1800/1898 dependencies 260/533 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 2011/2100 dependencies 263/549 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 15% building 0/1 entries 2475/2500 dependencies 476/668 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 15% building 0/1 entries 2700/2773 dependencies 542/763 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 16% building 0/1 entries 2843/2890 dependencies 600/779 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 17% building 0/1 entries 3032/3100 dependencies 685/858 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 65% building 1/1 entries 3747/3747 dependencies 1071/1071 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 65% building oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph ResolverCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph InferAsyncModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph FlagDependencyExportsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins WarnCaseSensitiveModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization SideEffectsFlagPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization EnsureChunkConditionsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization MergeDuplicateChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization SplitChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids NamedModuleIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids NamedChunkIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing ts-loader oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js generate SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js generated SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js attach SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js attached SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit SizeLimitsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% oed-web | oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web | oed-web | asset bundle.js 15.4 MiB [emitted] [big] (name: application) 1 related asset oed-web | orphan modules 236 KiB [orphan] 128 modules oed-web | runtime modules 1.7 KiB 8 modules oed-web | modules by path ./node_modules/ 13.2 MiB 756 modules oed-web | modules by path ./src/ 1.2 MiB 171 modules oed-web | asset modules 4.4 KiB oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 181 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 165 bytes [built] [code generated] oed-web | + 10 modules oed-web | webpack 5.76.3 compiled successfully in 29752 ms"><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/fullInstallOutput/"><meta property="og:title" content="Full Install Output"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. When you install OED without already having a database or node modules, it does all the steps. Below is typical output for this process. This output is shown in the nohup.out file for a VSC install or in the terminal when doing docker compose up. Please note: The exact output will vary with machine type and changes to OED. This output was created on Windows 11 using WSL 2 in October 2023 outside VSC. The string &quot;oed&quot; reflects that it is in a directory with that name and one&#39;s output would change accordingly. The lines starting with &quot;oed-database |&quot; would be elsewhere when using the VSC OED container. One can see the output from the database install by right clicking on the database Docker container in the VSC Docker extension and choosing &quot;Show Logs&quot;. The output and information in install output without redoing database or npm install is similar to what will happen here. For unknown reasons, the OED install fails to run at times in VSC. See the no npm install output to see the known solution. nohup.out output [+] Building 3.2s (14/14) FINISHED docker:default =&gt; [database internal] load .dockerignore 0.0s =&gt; =&gt; transferring context: 2B 0.0s =&gt; [database internal] load build definition from Dockerfile 0.0s =&gt; =&gt; transferring dockerfile: 462B 0.0s =&gt; [database internal] load metadata for docker.io/library/postgres:15.3 2.1s =&gt; [database internal] load build context 0.0s =&gt; =&gt; transferring context: 858B 0.0s =&gt; [database 1/2] FROM docker.io/library/postgres:15.3@sha256:8775adb39f0db45cf4cdb3601380312ee5e9c4f53af0f89b7dc5cd4c9a78e4e8 0.0s =&gt; CACHED [database 2/2] COPY *.sql /docker-entrypoint-initdb.d/ 0.0s =&gt; [database] exporting to image 0.0s =&gt; =&gt; exporting layers 0.0s =&gt; =&gt; writing image sha256:b42a00751662cbff86856a54572e167e3eaaa7b9166ccd0433797af9f1005698 0.0s =&gt; =&gt; naming to docker.io/library/oed-database 0.0s =&gt; [web internal] load .dockerignore 0.0s =&gt; =&gt; transferring context: 300B 0.0s =&gt; [web internal] load build definition from Dockerfile 0.0s =&gt; =&gt; transferring dockerfile: 614B 0.0s =&gt; [web internal] load metadata for docker.io/library/node:18.17.1 0.6s =&gt; [web 1/3] FROM docker.io/library/node:18.17.1@sha256:933bcfad91e9052a02bc29eb5aa29033e542afac4174f9524b79066d97b23c24 0.0s =&gt; CACHED [web 2/3] RUN mkdir -p &quot;/usr/src/app&quot; 0.0s =&gt; CACHED [web 3/3] WORKDIR /usr/src/app 0.0s =&gt; [web] exporting to image 0.0s =&gt; =&gt; exporting layers 0.0s =&gt; =&gt; writing image sha256:43ec575d519a23888db44ba3fd4af8847b557a23d927ed22549c81c776244499 0.0s =&gt; =&gt; naming to docker.io/library/oed-web 0.0s [+] Running 3/3 ✔ Network oed_default Created 0.1s ✔ Container oed-database Created 0.2s ✔ Container oed-web Created 0.1s Attaching to oed-database, oed-web oed-database | The files belonging to this database system will be owned by user &quot;postgres&quot;. oed-database | This user must also own the server process. oed-database | oed-database | The database cluster will be initialized with locale &quot;en_US.utf8&quot;. oed-database | The default database encoding has accordingly been set to &quot;UTF8&quot;. oed-database | The default text search configuration will be set to &quot;english&quot;. oed-database | oed-database | Data page checksums are disabled. oed-database | oed-database | fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok oed-database | creating subdirectories ... ok oed-database | selecting dynamic shared memory implementation ... posix oed-database | selecting default max_connections ... 100 oed-database | selecting default shared_buffers ... 128MB oed-database | selecting default time zone ... Etc/UTC oed-database | creating configuration files ... ok oed-database | running bootstrap script ... ok oed-web | oed-web | oed-web | ***** Starting install of OED at Sun Oct 15 21:36:55 UTC 2023 ***** oed-web | oed-web | oed-web | NPM install... oed-web | oed-database | performing post-bootstrap initialization ... ok oed-database | initdb: warning: enabling &quot;trust&quot; authentication for local connections oed-database | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. oed-database | syncing data to disk ... ok oed-database | oed-database | oed-database | Success. You can now start the database server using: oed-database | oed-database | pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start oed-database | oed-database | waiting for server to start....2023-10-15 21:36:56.244 UTC [49] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database | 2023-10-15 21:36:56.249 UTC [49] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database | 2023-10-15 21:36:56.258 UTC [52] LOG: database system was shut down at 2023-10-15 21:36:55 UTC oed-database | 2023-10-15 21:36:56.264 UTC [49] LOG: database system is ready to accept connections oed-database | done oed-database | server started oed-database | oed-database | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init.sql oed-database | CREATE ROLE oed-database | DROP DATABASE oed-database | psql:/docker-entrypoint-initdb.d/init.sql:6: NOTICE: database &quot;oed&quot; does not exist, skipping oed-database | CREATE DATABASE oed-database | DROP DATABASE oed-database | psql:/docker-entrypoint-initdb.d/init.sql:8: NOTICE: database &quot;oed_testing&quot; does not exist, skipping oed-database | CREATE DATABASE oed-database | ALTER ROLE oed-database | oed-database | oed-database | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/nuke.sql oed-database | 2023-10-15 21:36:56.516 UTC [50] LOG: checkpoint starting: immediate force wait oed-database | 2023-10-15 21:36:56.640 UTC [50] LOG: checkpoint complete: wrote 927 buffers (5.7%); 1 WAL file(s) added, 0 removed, 0 recycled; write=0.016 s, sync=0.077 s, total=0.125 s; sync files=257, longest=0.012 s, average=0.001 s; distance=8450 kB, estimate=8450 kB oed-database | DROP DATABASE oed-database | 2023-10-15 21:36:56.647 UTC [50] LOG: checkpoint starting: immediate force wait oed-database | 2023-10-15 21:36:56.665 UTC [50] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.004 s, total=0.018 s; sync files=3, longest=0.003 s, average=0.002 s; distance=1 kB, estimate=7605 kB oed-database | DROP DATABASE oed-database | CREATE DATABASE oed-database | CREATE DATABASE oed-database | oed-database | oed-database | waiting for server to shut down...2023-10-15 21:36:56.749 UTC [49] LOG: received fast shutdown request oed-database | .2023-10-15 21:36:56.752 UTC [49] LOG: aborting any active transactions oed-database | 2023-10-15 21:36:56.754 UTC [49] LOG: background worker &quot;logical replication launcher&quot; (PID 55) exited with exit code 1 oed-database | 2023-10-15 21:36:56.754 UTC [50] LOG: shutting down oed-database | 2023-10-15 21:36:56.757 UTC [50] LOG: checkpoint starting: shutdown immediate oed-database | 2023-10-15 21:36:56.940 UTC [50] LOG: checkpoint complete: wrote 1832 buffers (11.2%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.034 s, sync=0.140 s, total=0.186 s; sync files=498, longest=0.007 s, average=0.001 s; distance=8447 kB, estimate=8447 kB oed-database | 2023-10-15 21:36:56.946 UTC [49] LOG: database system is shut down oed-database | done oed-database | server stopped oed-database | oed-database | PostgreSQL init process complete; ready for start up. oed-database | oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: listening on IPv4 address &quot;0.0.0.0&quot;, port 5432 oed-database | 2023-10-15 21:36:56.970 UTC [1] LOG: listening on IPv6 address &quot;::&quot;, port 5432 oed-database | 2023-10-15 21:36:56.979 UTC [1] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database | 2023-10-15 21:36:56.985 UTC [67] LOG: database system was shut down at 2023-10-15 21:36:56 UTC oed-database | 2023-10-15 21:36:56.992 UTC [1] LOG: database system is ready to accept connections oed-web | npm WARN deprecated multer@1.3.1: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. oed-web | npm WARN deprecated mumath@3.3.4: Redundant dependency in your project. oed-web | npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau oed-web | npm WARN deprecated superagent@3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at &amp;lt;https://github.com/visionmedia/superagent/releases&amp;gt;. oed-web | npm WARN deprecated core-js@2.6.12: core-js@&amp;lt;3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. oed-web | oed-web | added 1166 packages, and audited 1167 packages in 31s oed-web | oed-web | 111 packages are looking for funding oed-web | run `npm fund` for details oed-web | oed-web | 7 vulnerabilities (4 moderate, 3 high) oed-web | oed-web | To address issues that do not require attention, run: oed-web | npm audit fix oed-web | oed-web | To address all issues possible (including breaking changes), run: oed-web | npm audit fix --force oed-web | oed-web | Some issues need review, and may require choosing oed-web | a different dependency. oed-web | oed-web | Run `npm audit` for details. oed-web | npm notice oed-web | npm notice New major version of npm available! 9.6.7 -&gt; 10.2.0 oed-web | npm notice Changelog: &amp;lt;https://github.com/npm/cli/releases/tag/v10.2.0&amp;gt; oed-web | npm notice Run `npm install -g npm@10.2.0` to update! oed-web | npm notice oed-web | oed-web | NPM install finished. oed-web | oed-web | Attempting to create database... oed-web | oed-web | -----start of npm run createdb output----- oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 createdb oed-web | &gt; node ./src/server/services/createDB.js oed-web | oed-web | [WARN@2023-10-15T21:37:34.894+00:00] Automatically set identifier of the unit &quot;kWh&quot; to &quot;kWh&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.936+00:00] Automatically set identifier of the unit &quot;metric ton&quot; to &quot;metric ton&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.941+00:00] Automatically set identifier of the unit &quot;gallon&quot; to &quot;gallon&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.942+00:00] Automatically set identifier of the unit &quot;kg&quot; to &quot;kg&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.944+00:00] Automatically set identifier of the unit &quot;Fahrenheit&quot; to &quot;Fahrenheit&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.945+00:00] Automatically set identifier of the unit &quot;m³ gas&quot; to &quot;m³ gas&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.946+00:00] Automatically set identifier of the unit &quot;BTU&quot; to &quot;BTU&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.947+00:00] Automatically set identifier of the unit &quot;Electric_Utility&quot; to &quot;Electric_Utility&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.947+00:00] Automatically set identifier of the unit &quot;Celsius&quot; to &quot;Celsius&quot; oed-web | oed-web | [WARN@2023-10-15T21:37:34.952+00:00] Automatically set identifier of the unit &quot;liter&quot; to &quot;liter&quot; oed-web | oed-web | -----end of npm run createdb output----- oed-web | oed-web | database creation had no errors so assume schema creation worked. oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 createUser oed-web | &gt; node ./src/server/services/user/createUser.js test@example.com password oed-web | oed-web | [INFO@2023-10-15T21:37:46.142+00:00] User test@example.com created oed-web | oed-web | User creation had no errors so default user &#39;test@example.com&#39; with password &#39;password&#39; should exist oed-web | Creating developer DB function oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 developerdb oed-web | &gt; node -e &#39;require(&quot;./src/server/util/developer.js&quot;).createShiftReadingsFunction()&#39; oed-web | oed-web | OED install finished oed-web | Starting OED in development mode oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 webpack:dev oed-web | &gt; webpack watch --color --progress --mode development oed-web | oed-web | oed-web | &gt; open-energy-dashboard@1.0.0 start:dev oed-web | &gt; nodemon --legacy-watch --inspect=0.0.0.0 ./src/bin/www oed-web | oed-web | [nodemon] 2.0.22 oed-web | [nodemon] to restart at any time, enter `rs` oed-web | [nodemon] watching path(s): src/server/**/* src/bin/**/* src/common/**/* oed-web | [nodemon] watching extensions: js,mjs,json oed-web | [nodemon] starting `node --inspect=0.0.0.0 ./src/bin/www` oed-web | Debugger listening on ws://0.0.0.0:9229/8f986c6b-88ca-4b76-9b3f-eb6e77a84041 oed-web | For help, see: https://nodejs.org/en/docs/inspector oed-web | [INFO@2023-10-15T21:37:58.120+00:00] Listening on port 3000 oed-web | oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run webpack-cli oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory LodashModuleReplacementPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile ProgressPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile ExternalsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation WorkerPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation SplitChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ResolverCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProgressPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProvidePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ModuleInfoHeaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JsonModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AssetModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EntryPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RuntimePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DataUriPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FileUriPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CompatibilityPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation HarmonyModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AMDPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireJsStuffPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CommonJsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NodeStuffPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation APIPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ConstPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation UseStrictPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireIncludePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireEnsurePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SystemPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportMetaPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation URLPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedModuleIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedChunkIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefinePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation TemplatedPathPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/ts-loader/index.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/1 dependencies 0/1 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/2 dependencies 0/1 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/style-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/css-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 10/33 dependencies 0/9 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building import loader ./node_modules/source-map-loader/dist/cjs.js oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 48/52 dependencies 0/38 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 48/100 dependencies 0/38 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 78/138 dependencies 2/62 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 194/234 dependencies 34/101 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 231/261 dependencies 43/108 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 399/500 dependencies 49/160 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 442/790 dependencies 54/200 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 858/900 dependencies 64/355 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 11% building 0/1 entries 1200/1273 dependencies 151/466 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1400/1450 dependencies 235/492 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1418/1500 dependencies 238/494 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 1800/1898 dependencies 260/533 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 12% building 0/1 entries 2011/2100 dependencies 263/549 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 15% building 0/1 entries 2475/2500 dependencies 476/668 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 15% building 0/1 entries 2700/2773 dependencies 542/763 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 16% building 0/1 entries 2843/2890 dependencies 600/779 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 17% building 0/1 entries 3032/3100 dependencies 685/858 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 65% building 1/1 entries 3747/3747 dependencies 1071/1071 modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 65% building oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph ResolverCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph InferAsyncModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph FlagDependencyExportsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins WarnCaseSensitiveModulesPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization SideEffectsFlagPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization EnsureChunkConditionsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization MergeDuplicateChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization SplitChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids NamedModuleIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids NamedChunkIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks RecordIdsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing ts-loader oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js generate SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js generated SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js attach SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js attached SourceMap oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit SizeLimitsPlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% oed-web | oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle IdleFileCachePlugin oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web | oed-web | asset bundle.js 15.4 MiB [emitted] [big] (name: application) 1 related asset oed-web | orphan modules 236 KiB [orphan] 128 modules oed-web | runtime modules 1.7 KiB 8 modules oed-web | modules by path ./node_modules/ 13.2 MiB 756 modules oed-web | modules by path ./src/ 1.2 MiB 171 modules oed-web | asset modules 4.4 KiB oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 181 bytes [built] [code generated] oed-web | data:image/svg+xml,%3csvg xmlns=%27.. 165 bytes [built] [code generated] oed-web | + 10 modules oed-web | webpack 5.76.3 compiled successfully in 29752 ms"><meta property="og:url" content="https://openenergydashboard.org/developer/fullInstallOutput/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Full Install Output</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Full Install Output</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>When you install OED without already having a database or node modules, it does all the steps. Below is typical output for this process. This output is shown in the nohup.out file for a VSC install or in the terminal when doing <code>docker compose up</code>. Please note:<ul><li>The exact output will vary with machine type and changes to OED. This output was created on Windows 11 using WSL 2 in October 2023 outside VSC. The string "oed" reflects that it is in a directory with that name and one's output would change accordingly.<li>The lines starting with "oed-database |" would be elsewhere when using the VSC OED container. One can see the output from the database install by right clicking on the database Docker container in the VSC Docker extension and choosing "Show Logs".<li>The output and information in <a href="../noNPMInstallOutput/">install output without redoing database or npm install</a> is similar to what will happen here.<li>For unknown reasons, the OED install fails to run at times in VSC. See the <a href="../noNPMInstallOutput/">no npm install output</a> to see the known solution.</ul><h3>nohup.out output</h3><pre>
 [+] Building 3.2s (14/14) FINISHED                                                                                                                                                              docker:default
 => [database internal] load .dockerignore                                                                                                                                                                0.0s
 => => transferring context: 2B                                                                                                                                                                           0.0s
diff --git a/developer/gettingStarted/index.html b/developer/gettingStarted/index.html
index e858ab71..e243ccb2 100644
--- a/developer/gettingStarted/index.html
+++ b/developer/gettingStarted/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>OED Developer Documentation</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The following steps should get you ready to contribute to OED in a fairly short period of time. Please know that we are here to help you so use the link at the bottom of the page to email/message us with any issues. Prerequisites First, we strongly encourage you to contact the OED project as a potential developer. You can join our Discord channel with this Discord invite link or contact us. That way we know about you and can help you select tasks that will be interesting to you and also benefit the project. Before you can submit work to OED, you need to sign the Contributor&#39;s License Agreement. The OED project resides on GitHub so you need a login to contribute to the project. If you are using Windows 10+ then you will probably want to use the Windows Subsystem for Linux (WSL) that allows Docker to run on Windows. Please see this page for the steps you need to follow these extra steps. Installing WSL before Docker is helpful with the setup. Please be sure to see the information on the WSL page (link earlier in this bullet) about using the Linux filesystem for OED and running Visual Studio Code under WSL if you are using Windows. You need to read this even if you already had WSL and/or Visual Studio Code. OED uses the Docker container system to run the software so you need to download and install Docker. (You need both Docker and docker compose but you generally get those together during the install.) There are paid subscriptions but your non-commercial work on the OSS OED project does not require a paid subscription. This has the advantage that our configuration files for Docker can get any needed software and also means we do not modify your normal system since the setup is in a separate container that does not impact other programs on your computer. Note that Docker should run on all OSes (Linux, Mac OS X, Windows - see above for information on using WSL on Windows) so you should be able to use it. You are welcome to use any IDE for code development. Having said that, most OED developers use Visual Studio Code (VSC). The OED repository contains the .devcontainer folder that allows VSC to automatically launch and set up the needed Docker containers. There are a number of advantages to this system including that it puts in the extensions that OED thinks are valuable, gives a guaranteed environment to work with OED and avoids you having to separately install OED. Thus, you are encouraged to install VSC (if you don&#39;t already have it. The directions for working outside VSC follow the ones for VSC. Once you have VSC installed, you need to add one extension to it so you can work with the OED container. Click on the Extensions manager icon on the far left of the VSC window (), search for &quot;Remote Development&quot; and install it. You will get several Extensions included with this one. OED uses the fork model for development. (There are many descriptions of this process on the web but GitHub ones include a general one and one with more operational details.) This means you need to go to the main OED GitHub page (after login to GitHub), fork the project onto your own GitHub account and then clone the forked copy onto you own development machine to work on the code base. You can place the clone anywhere you want on your machine but please note what is stated on the WSL page linked above about where it should go on WSL. Note the clone will place all the files inside a new directory named OED unless you put a &quot;.&quot; at the end of the git clone command. This model has the advantage that you can commit and push to your account without needing write permission on the main OED project repository. There are separate directions of the steps for creating a pull request to integrate your code into OED. Installing OED in Visual Studio Code Make sure you have Docker running on your system so OED can use it to get running. Assuming you are using VSC, you will do the following (steps to setup outside VSC are below): Open the cloned OED repository that is on your local machine in VSC by doing File -&gt; Open Folder... You need to open the main OED folder that was created when you cloned OED. It has the README.md file, the src/ directory, the package.json file and lots of other files. Typically, VSC will ask if you want to reopen the folder in a container by showing this message: You can click the button &quot;Reopen in Container&quot;. You will often see a popup in VSC that indicate you can click to see the log: The first time OED installs it can take a while where the time depends on the speed of your machine and internet connection (to get the needed npm packages). You can see the output of the install and anything OED outputs to the console by looking at the file nohup.out that will be created in your main OED directory. If you open this in VSC it should update with new lines at the bottom as they are added. See full install output or install without Postgres or npm install output to see a typical install output and for information if something goes wrong. If VSC does not automatically ask to open in a container, you can click the &quot;Remote Container&quot; icon () that is normally in the bottom, left of the VSC window and select &quot;Reopen in Container&quot; for the menu that appears. Once OED is running you should be able to see the web and database Docker containers. See Useful VSC information for more info on doing this. You can shut down the OED VSC container by clicking the green icon for the Remote Container and selecting &quot;Close Remote Container&quot; Using OED Once you have OED installed and running, you will want to open it in a web browser. It should not matter which one you use. Enter the address:localhost:3000 and load the page. &quot;localhost&quot; indicates the page is being served up from your machine and &quot;3000&quot; is the default port that OED uses to accept web connections. If all went well, you will see the main OED web page that looks something like: If you see that then the basic OED install worked and your system is properly serving up the OED web system. Though not common, it is possible for the OED web system to run without starting the underlying database system. To verify that the database is running properly, you should log into OED as the admin. The username and password were shown during the install process. By default they are: email: test@example.com password: password Yes, the password really is password but remember it is running on your local machine in a container so it should not be accessible to others. If it fails you should see a message appear briefly in the top, right corner of the page. If this happens, please follow the steps below to email us the output in your terminal. If all went well, you now have a fully running development version of OED that can be used to begin coding. Congratulations! OED test data When you install OED, it does not have any data. An actual site would connect up meters to gather data. For a developer, we have standard test data you can use. The OED test data page has information and directions for doing this. We suggest you load up the data now so you can try any features you want in OED. Note that an advantage of this test data is that it is the same for all developers so people should be able to reproduce what you mention if you have a question or issue. Technologies OED uses OED uses a number of technologies. You may want further information on these and some are provided on the OED technologies page. We welcome your input on other areas you would like to know about or other resources you find valuable. Note that you can work on parts of OED without knowing many of the technologies in any depth. For example, you can work on database queries without knowing about the front-end. Thus, many developers begin in areas they know or want to learn first and focus on that needed information. Having said that, almost the entire code base is in JavaScript/TypeScript so a basic understanding of that is usually needed to get started. OED GitHub Information areas There are two areas on our GitHub repo that are worth noting. First, the discussion board has several areas including one for developers. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group. Second, the projects have an overview of the status of work and major initiatives. Choosing OED work to do The What to Work on in OED page can help you figure out what to do. Multi-author work It is common for a team to work on OED together. If you are doing this and want to give another person acknowledgement on a commit, then see GitHub info on multiple authors. Issues If you have any issues please copy all the output from your nohup.out (or the terminal outside Visual Studio Code) and send it and a message by contacting us. We will look it over and get back to you. We try to do that quickly. It is also fine to send a message to the developer Discord channel to seek answers. Useful VSC information The VSC container you are working in has the Docker extension included. You can access it by clicking the whale with squares over it icon () on the far left side of the VSC window (default location). It should show information on all the Docker images/containers you have. The containers that are currently running have a green triangle next to them. You can get the following choices by right clicking on a container: View Logs: The web container (prefixed with “vsc-”) will not show much since the OED output is in nohup.out. The database one will show messages from PostgreSQL. These open a new terminal that you can remove with the trash can icon. Attach Shell: This puts you in a shell within the container that is using the OED environment. It is important to recognize this is not the same as opening a shell on your machine that runs in your local environment. You are strongly encouraged to run all your OED terminal commands in the container so you get the OED environment. For example, it will use the version of node or npm that OED expects. In the shell inside the database you can do: “psql -U oed” to open the Postgres command line. This will allow you to look at the live OED database. You can also see the OED startup files for the database with: ls docker-entrypoint-initdb.d. In the shell inside the web container, you can look at the environment variables or do other Linux operation. You can run any script in package.json, e.g., npm run check. You can see all the running processes with “ps -aux”. Inspect: Opens a JSON file that gives detailed information on the container that can be useful for debugging issues. Open in Browser: For the web container, this will go to localhost:3000. Stop, Remove: Stop or remove the container where stop is useful if something does not shut down properly. The VSC container also include several extensions OED thinks are valuable: GitLens: This shows detailed information on Git commits, who made changes, file history and more. It makes working with Git inside VSC much nicer. Code Spell Checker: It will help you avoid spelling mistakes. GitHub Pull Request: It lets you work with GitHub within VSC including creating, commenting on and working with pull requests all with VSC features. Docker was discussed above. Install OED outside of Visual Studio Code While there is further information on more advanced options for doing this, the initial install can be done by following these steps: Open a terminal on your computer (it is the &quot;command prompt&quot; on some Windows systems). It is fine to use a terminal within VSC. In the terminal do the following: cd &quot;directory with cloned OED&quot;. You need to replace &quot;directory with cloned OED&quot; with the location of the cloned copy of OED. This is where the &quot;README.md&quot; and other main OED files are located. Some people find it easiest to locate that directory using the file manager on their OS and then use that information to get to the needed directory. As an example, you might do cd /home/username/projects/OED if you cloned OED in the /home/username/projects/ directory. docker compose upThis will run the entire OED install process. Note that on some systems (mostly some Linux systems), depending on how you installed Docker, you may get a permission error so you will need to do:sudo docker compose upwhich runs the process with root privileges. If this is the case then you need to do sudo before all docker commands on your system. Depending on the speed of your machine and internet connection, this can take a few to ten minutes. It should go faster after the first install. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while) and starting up the web system. When you see the line: + 2073 hidden modules where the actual number will likely be different then OED should be running normally unless there was an error in the output. The developer web pages assume you assess a terminal inside of the Docker container. Normally you can do this by going to the Docker icon for your running Docker and selecting the &quot;Dashboard&quot;. Then look for your running OED container in the list. There should be an icon to the right that gives a &quot;CLI&quot;. Clicking it should get you a command line interface for either the web or database container that OED uses. You can do other operations to control container through the same interface. You can also do this within VSC with the Docker extension even though you started OED outside VSC. The developer pages often refer to output from OED. This goes to the nohup.out file with Visual Studio Code. When installed outside of VSC it will come to the terminal where you started OED, even in a terminal opened in VSC to install OED. Getting help If you want help or have questions about running OED, then see the website or the documentation pages and contact information in the links on this page."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/gettingStarted/"><meta property="og:title" content="OED Developer Documentation"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. The following steps should get you ready to contribute to OED in a fairly short period of time. Please know that we are here to help you so use the link at the bottom of the page to email/message us with any issues. Prerequisites First, we strongly encourage you to contact the OED project as a potential developer. You can join our Discord channel with this Discord invite link or contact us. That way we know about you and can help you select tasks that will be interesting to you and also benefit the project. Before you can submit work to OED, you need to sign the Contributor&#39;s License Agreement. The OED project resides on GitHub so you need a login to contribute to the project. If you are using Windows 10+ then you will probably want to use the Windows Subsystem for Linux (WSL) that allows Docker to run on Windows. Please see this page for the steps you need to follow these extra steps. Installing WSL before Docker is helpful with the setup. Please be sure to see the information on the WSL page (link earlier in this bullet) about using the Linux filesystem for OED and running Visual Studio Code under WSL if you are using Windows. You need to read this even if you already had WSL and/or Visual Studio Code. OED uses the Docker container system to run the software so you need to download and install Docker. (You need both Docker and docker compose but you generally get those together during the install.) There are paid subscriptions but your non-commercial work on the OSS OED project does not require a paid subscription. This has the advantage that our configuration files for Docker can get any needed software and also means we do not modify your normal system since the setup is in a separate container that does not impact other programs on your computer. Note that Docker should run on all OSes (Linux, Mac OS X, Windows - see above for information on using WSL on Windows) so you should be able to use it. You are welcome to use any IDE for code development. Having said that, most OED developers use Visual Studio Code (VSC). The OED repository contains the .devcontainer folder that allows VSC to automatically launch and set up the needed Docker containers. There are a number of advantages to this system including that it puts in the extensions that OED thinks are valuable, gives a guaranteed environment to work with OED and avoids you having to separately install OED. Thus, you are encouraged to install VSC (if you don&#39;t already have it. The directions for working outside VSC follow the ones for VSC. Once you have VSC installed, you need to add one extension to it so you can work with the OED container. Click on the Extensions manager icon on the far left of the VSC window (), search for &quot;Remote Development&quot; and install it. You will get several Extensions included with this one. OED uses the fork model for development. (There are many descriptions of this process on the web but GitHub ones include a general one and one with more operational details.) This means you need to go to the main OED GitHub page (after login to GitHub), fork the project onto your own GitHub account and then clone the forked copy onto you own development machine to work on the code base. You can place the clone anywhere you want on your machine but please note what is stated on the WSL page linked above about where it should go on WSL. Note the clone will place all the files inside a new directory named OED unless you put a &quot;.&quot; at the end of the git clone command. This model has the advantage that you can commit and push to your account without needing write permission on the main OED project repository. There are separate directions of the steps for creating a pull request to integrate your code into OED. Installing OED in Visual Studio Code Make sure you have Docker running on your system so OED can use it to get running. Assuming you are using VSC, you will do the following (steps to setup outside VSC are below): Open the cloned OED repository that is on your local machine in VSC by doing File -&gt; Open Folder... You need to open the main OED folder that was created when you cloned OED. It has the README.md file, the src/ directory, the package.json file and lots of other files. Typically, VSC will ask if you want to reopen the folder in a container by showing this message: You can click the button &quot;Reopen in Container&quot;. You will often see a popup in VSC that indicate you can click to see the log: The first time OED installs it can take a while where the time depends on the speed of your machine and internet connection (to get the needed npm packages). You can see the output of the install and anything OED outputs to the console by looking at the file nohup.out that will be created in your main OED directory. If you open this in VSC it should update with new lines at the bottom as they are added. See full install output or install without Postgres or npm install output to see a typical install output and for information if something goes wrong. If VSC does not automatically ask to open in a container, you can click the &quot;Remote Container&quot; icon () that is normally in the bottom, left of the VSC window and select &quot;Reopen in Container&quot; for the menu that appears. Once OED is running you should be able to see the web and database Docker containers. See Useful VSC information for more info on doing this. You can shut down the OED VSC container by clicking the green icon for the Remote Container and selecting &quot;Close Remote Container&quot; Using OED Once you have OED installed and running, you will want to open it in a web browser. It should not matter which one you use. Enter the address:localhost:3000 and load the page. &quot;localhost&quot; indicates the page is being served up from your machine and &quot;3000&quot; is the default port that OED uses to accept web connections. If all went well, you will see the main OED web page that looks something like: If you see that then the basic OED install worked and your system is properly serving up the OED web system. Though not common, it is possible for the OED web system to run without starting the underlying database system. To verify that the database is running properly, you should log into OED as the admin. The username and password were shown during the install process. By default they are: email: test@example.com password: password Yes, the password really is password but remember it is running on your local machine in a container so it should not be accessible to others. If it fails you should see a message appear briefly in the top, right corner of the page. If this happens, please follow the steps below to email us the output in your terminal. If all went well, you now have a fully running development version of OED that can be used to begin coding. Congratulations! OED test data When you install OED, it does not have any data. An actual site would connect up meters to gather data. For a developer, we have standard test data you can use. The OED test data page has information and directions for doing this. We suggest you load up the data now so you can try any features you want in OED. Note that an advantage of this test data is that it is the same for all developers so people should be able to reproduce what you mention if you have a question or issue. Technologies OED uses OED uses a number of technologies. You may want further information on these and some are provided on the OED technologies page. We welcome your input on other areas you would like to know about or other resources you find valuable. Note that you can work on parts of OED without knowing many of the technologies in any depth. For example, you can work on database queries without knowing about the front-end. Thus, many developers begin in areas they know or want to learn first and focus on that needed information. Having said that, almost the entire code base is in JavaScript/TypeScript so a basic understanding of that is usually needed to get started. OED GitHub Information areas There are two areas on our GitHub repo that are worth noting. First, the discussion board has several areas including one for developers. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group. Second, the projects have an overview of the status of work and major initiatives. Choosing OED work to do The What to Work on in OED page can help you figure out what to do. Multi-author work It is common for a team to work on OED together. If you are doing this and want to give another person acknowledgement on a commit, then see GitHub info on multiple authors. Issues If you have any issues please copy all the output from your nohup.out (or the terminal outside Visual Studio Code) and send it and a message by contacting us. We will look it over and get back to you. We try to do that quickly. It is also fine to send a message to the developer Discord channel to seek answers. Useful VSC information The VSC container you are working in has the Docker extension included. You can access it by clicking the whale with squares over it icon () on the far left side of the VSC window (default location). It should show information on all the Docker images/containers you have. The containers that are currently running have a green triangle next to them. You can get the following choices by right clicking on a container: View Logs: The web container (prefixed with “vsc-”) will not show much since the OED output is in nohup.out. The database one will show messages from PostgreSQL. These open a new terminal that you can remove with the trash can icon. Attach Shell: This puts you in a shell within the container that is using the OED environment. It is important to recognize this is not the same as opening a shell on your machine that runs in your local environment. You are strongly encouraged to run all your OED terminal commands in the container so you get the OED environment. For example, it will use the version of node or npm that OED expects. In the shell inside the database you can do: “psql -U oed” to open the Postgres command line. This will allow you to look at the live OED database. You can also see the OED startup files for the database with: ls docker-entrypoint-initdb.d. In the shell inside the web container, you can look at the environment variables or do other Linux operation. You can run any script in package.json, e.g., npm run check. You can see all the running processes with “ps -aux”. Inspect: Opens a JSON file that gives detailed information on the container that can be useful for debugging issues. Open in Browser: For the web container, this will go to localhost:3000. Stop, Remove: Stop or remove the container where stop is useful if something does not shut down properly. The VSC container also include several extensions OED thinks are valuable: GitLens: This shows detailed information on Git commits, who made changes, file history and more. It makes working with Git inside VSC much nicer. Code Spell Checker: It will help you avoid spelling mistakes. GitHub Pull Request: It lets you work with GitHub within VSC including creating, commenting on and working with pull requests all with VSC features. Docker was discussed above. Install OED outside of Visual Studio Code While there is further information on more advanced options for doing this, the initial install can be done by following these steps: Open a terminal on your computer (it is the &quot;command prompt&quot; on some Windows systems). It is fine to use a terminal within VSC. In the terminal do the following: cd &quot;directory with cloned OED&quot;. You need to replace &quot;directory with cloned OED&quot; with the location of the cloned copy of OED. This is where the &quot;README.md&quot; and other main OED files are located. Some people find it easiest to locate that directory using the file manager on their OS and then use that information to get to the needed directory. As an example, you might do cd /home/username/projects/OED if you cloned OED in the /home/username/projects/ directory. docker compose upThis will run the entire OED install process. Note that on some systems (mostly some Linux systems), depending on how you installed Docker, you may get a permission error so you will need to do:sudo docker compose upwhich runs the process with root privileges. If this is the case then you need to do sudo before all docker commands on your system. Depending on the speed of your machine and internet connection, this can take a few to ten minutes. It should go faster after the first install. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while) and starting up the web system. When you see the line: + 2073 hidden modules where the actual number will likely be different then OED should be running normally unless there was an error in the output. The developer web pages assume you assess a terminal inside of the Docker container. Normally you can do this by going to the Docker icon for your running Docker and selecting the &quot;Dashboard&quot;. Then look for your running OED container in the list. There should be an icon to the right that gives a &quot;CLI&quot;. Clicking it should get you a command line interface for either the web or database container that OED uses. You can do other operations to control container through the same interface. You can also do this within VSC with the Docker extension even though you started OED outside VSC. The developer pages often refer to output from OED. This goes to the nohup.out file with Visual Studio Code. When installed outside of VSC it will come to the terminal where you started OED, even in a terminal opened in VSC to install OED. Getting help If you want help or have questions about running OED, then see the website or the documentation pages and contact information in the links on this page."><meta property="og:url" content="https://openenergydashboard.org/developer/gettingStarted/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Developer First Steps</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">Developer Startup<h1>Developer First Steps</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>The following steps should get you ready to contribute to OED in a fairly short period of time. Please know that we are here to help you so use the link at the bottom of the page to email/message us with any issues.<h3>Prerequisites</h3><ol><li>First, we strongly encourage you to contact the OED project as a potential developer. You can join our Discord channel with this <a href="https://discord.com/invite/zP6nHVspet">Discord invite link</a> or <a href="https://openenergydashboard.org/contact/">contact us</a>. That way we know about you and can help you select tasks that will be interesting to you and also benefit the project.<li>Before you can submit work to OED, you need to sign the <a href="../cla/">Contributor's License Agreement</a>.<li>The OED project resides on <a href="https://github.com/" rel="noopener noreferrer">GitHub</a> so you need a login to contribute to the project.<li>If you are using Windows 10+ then you will probably want to use the Windows Subsystem for Linux (WSL) that allows Docker to run on Windows. Please see this page for the steps you need to follow <a href="../wslSteps/">these extra steps</a>. Installing WSL before Docker is helpful with the setup. <strong>Please be sure to see the information on the WSL page (link earlier in this bullet) about using the Linux filesystem for OED and running Visual Studio Code under WSL if you are using Windows. You need to read this even if you already had WSL and/or Visual Studio Code.</strong><li>OED uses the Docker container system to run the software so you need to <a href="https://www.docker.com/products/docker-desktop/" rel="noopener noreferrer">download</a> and install Docker. (You need both Docker and docker compose but you generally get those together during the install.) There are paid subscriptions but your non-commercial work on the OSS OED project does not require a paid subscription. This has the advantage that our configuration files for Docker can get any needed software and also means we do not modify your normal system since the setup is in a separate container that does not impact other programs on your computer. Note that Docker should run on all OSes (Linux, Mac OS X, Windows - see above for information on using WSL on Windows) so you should be able to use it.<li>You are welcome to use any IDE for code development. Having said that, most OED developers use <a href="https://code.visualstudio.com/" rel="noopener noreferrer">Visual Studio Code</a> (VSC). The OED repository contains the .devcontainer folder that allows VSC to automatically launch and set up the needed Docker containers. There are a number of advantages to this system including that it puts in the extensions that OED thinks are valuable, gives a guaranteed environment to work with OED and avoids you having to separately install OED. Thus, you are encouraged to <a href="https://code.visualstudio.com/Download">install VSC</a> (if you don't already have it. The directions for working outside VSC follow the ones for VSC.<ul><li>Once you have VSC installed, you need to add one extension to it so you can work with the OED container. Click on the Extensions manager icon on the far left of the VSC window (<img alt="VSC Extension icon" src="../images/VSCExtensions.png">), search for "Remote Development" and install it. You will get several Extensions included with this one.</ul><li>OED uses the fork model for development. (There are many descriptions of this process on the web but GitHub ones include a <a href="https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project" rel="noopener noreferrer">general one</a> and one with <a href="https://docs.github.com/get-started/quickstart/fork-a-repo" rel="noopener noreferrer">more operational details</a>.) This means you need to go to the main OED GitHub page (after login to GitHub), fork the project onto your own GitHub account and then clone the forked copy onto you own development machine to work on the code base. You can place the clone anywhere you want on your machine but please note what is stated on the WSL page linked above about where it should go on WSL. Note the clone will place all the files inside a new directory named OED unless you put a "." at the end of the <code>git clone</code> command. This model has the advantage that you can commit and push to your account without needing write permission on the main OED project repository. There are <a href="../pr/">separate directions</a> of the steps for creating a pull request to integrate your code into OED.</ol><h3>Installing OED in Visual Studio Code</h3><ol><li>Make sure you have Docker running on your system so OED can use it to get running.<li>Assuming you are using VSC, you will do the following (steps to setup outside VSC are below):<ol><li>Open the cloned OED repository that is on your local machine in VSC by doing File -> Open Folder... You need to open the main OED folder that was created when you cloned OED. It has the README.md file, the src/ directory, the package.json file and lots of other files.<li>Typically, VSC will ask if you want to reopen the folder in a container by showing this message:<br> <img alt="VSC container msg" src="../images/VSCContainerMsg.png" style="width: 25vw; min-width: 200px;"><p>You can click the button "Reopen in Container". You will often see a popup in VSC that indicate you can click to see the log: <img alt="VSC container msg" src="../images/VSCDevLog.png" style="width: 25vw; min-width: 200px;"><p>The first time OED installs it can take a while where the time depends on the speed of your machine and internet connection (to get the needed npm packages). You can see the output of the install and anything OED outputs to the console by looking at the file nohup.out that will be created in your main OED directory. If you open this in VSC it should update with new lines at the bottom as they are added. See <a href="../fullInstallOutput/">full install output</a> or <a href="../noNPMInstallOutput/">install without Postgres or npm install output</a> to see a typical install output and for information if something goes wrong.<p>If VSC does not automatically ask to open in a container, you can click the "Remote Container" icon (<img alt="VSC Remote Container icon" src="../images/VSCRemoteIcon.png" width="32" height="26" style="min-width:32px; display: inline">) that is normally in the bottom, left of the VSC window and select "Reopen in Container" for the menu that appears.<p>Once OED is running you should be able to see the web and database Docker containers. See <a href="#VSCInfo">Useful VSC information</a> for more info on doing this.<p>You can shut down the OED VSC container by clicking the green icon for the Remote Container and selecting "Close Remote Container"</ol></ol><h3>Using OED</h3><ol><li>Once you have OED installed and running, you will want to open it in a web browser. It should not matter which one you use. Enter the address:<code>localhost:3000</code> and load the page. "localhost" indicates the page is being served up from your machine and "3000" is the default port that OED uses to accept web connections. If all went well, you will see the main OED web page that looks something like:<p><img alt="OED Main Page" src="../images/startupMainPage.png" /><p>If you see that then the basic OED install worked and your system is properly serving up the OED web system.<li>Though not common, it is possible for the OED web system to run without starting the underlying database system. To verify that the database is running properly, you should <a href="https://openenergydashboard.org/helpV1_0_0/optionsMenu/">log into OED</a> as the admin. The username and password were shown during the install process. By default they are:<br> email: test@example.com<br> password: password<br> Yes, the password really is password but remember it is running on your local machine in a container so it should not be accessible to others. If it fails you should see a message appear briefly in the top, right corner of the page. If this happens, please follow the <a href="#sendConsole">steps below</a> to email us the output in your terminal.<li>If all went well, you now have a fully running development version of OED that can be used to begin coding. Congratulations!</ol><h3>OED test data</h3><p>When you install OED, it does not have any data. An actual site would connect up meters to gather data. For a developer, we have standard test data you can use. The <a href="../testData/">OED test data</a> page has information and directions for doing this. We suggest you load up the data now so you can try any features you want in OED. Note that an advantage of this test data is that it is the same for all developers so people should be able to reproduce what you mention if you have a question or issue.<h3>Technologies OED uses</h3><p>OED uses a number of technologies. You may want further information on these and some are provided on the <a href="../learningTechnologies/">OED technologies page</a>. We welcome your input on other areas you would like to know about or other resources you find valuable. Note that you can work on parts of OED without knowing many of the technologies in any depth. For example, you can work on database queries without knowing about the front-end. Thus, many developers begin in areas they know or want to learn first and focus on that needed information. Having said that, almost the entire code base is in JavaScript/TypeScript so a basic understanding of that is usually needed to get started.<h3>OED GitHub Information areas</h3><p>There are two areas on our GitHub repo that are worth noting. First, the <a href="https://github.com/OpenEnergyDashboard/OED/discussions" rel="noopener noreferrer">discussion board</a> has several areas including one for developers. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group. Second, the <a href="https://github.com/OpenEnergyDashboard/OED/projects?type=beta" rel="noopener noreferrer">projects</a> have an overview of the status of work and major initiatives.<h3>Choosing OED work to do</h3><p>The <a href="../work/">What to Work on in OED</a> page can help you figure out what to do.<h3>Multi-author work</h3><p>It is common for a team to work on OED together. If you are doing this and want to give another person acknowledgement on a commit, then see <a href="https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors" rel="noopener noreferrer">GitHub info on multiple authors</a>.<h3>Issues</h3><p id="sendConsole">If you have any issues please copy all the output from your nohup.out (or the terminal outside Visual Studio Code) and send it and a message by <a href="https://openenergydashboard.org/contact/">contacting us</a>. We will look it over and get back to you. We try to do that quickly. It is also fine to send a message to the developer Discord channel to seek answers.<h3 id="VSCInfo">Useful VSC information</h3><ul><li>The VSC container you are working in has the Docker extension included. You can access it by clicking the whale with squares over it icon (<img alt="VSC container msg" src="../images/dockerIcon.png">) on the far left side of the VSC window (default location). It should show information on all the Docker images/containers you have. The containers that are currently running have a green triangle next to them. You can get the following choices by right clicking on a container:<ul><li>View Logs: The web container (prefixed with “vsc-”) will not show much since the OED output is in nohup.out. The database one will show messages from PostgreSQL. These open a new terminal that you can remove with the trash can icon.<li>Attach Shell: This puts you in a shell within the container that is using the OED environment. It is important to recognize this is not the same as opening a shell on your machine that runs in your local environment. You are strongly encouraged to run all your OED terminal commands in the container so you get the OED environment. For example, it will use the version of node or npm that OED expects.<ul><li>In the shell inside the database you can do: “psql -U oed” to open the Postgres command line. This will allow you to look at the live OED database. You can also see the OED startup files for the database with: ls docker-entrypoint-initdb.d.</ul><li>In the shell inside the web container, you can look at the environment variables or do other Linux operation. You can run any script in package.json, e.g., npm run check. You can see all the running processes with “ps -aux”.<li>Inspect: Opens a JSON file that gives detailed information on the container that can be useful for debugging issues.<li>Open in Browser: For the web container, this will go to localhost:3000.<li>Stop, Remove: Stop or remove the container where stop is useful if something does not shut down properly.</ul><li>The VSC container also include several extensions OED thinks are valuable:<ul><li>GitLens: This shows detailed information on Git commits, who made changes, file history and more. It makes working with Git inside VSC much nicer.<li>Code Spell Checker: It will help you avoid spelling mistakes.<li>GitHub Pull Request: It lets you work with GitHub within VSC including creating, commenting on and working with pull requests all with VSC features.<li>Docker was discussed above.</ul></ul><h3>Install OED outside of Visual Studio Code</h3><p>While there is <a href="../devDetails/">further information</a> on more advanced options for doing this, the initial install can be done by following these steps:<ol><li>Open a terminal on your computer (it is the "command prompt" on some Windows systems). It is fine to use a terminal within VSC. In the terminal do the following:<ol><li><code>cd "directory with cloned OED"</code>. You need to replace "directory with cloned OED" with the location of the cloned copy of OED. This is where the "README.md" and other main OED files are located. Some people find it easiest to locate that directory using the file manager on their OS and then use that information to get to the needed directory. As an example, you might do <code>cd /home/username/projects/OED</code> if you cloned OED in the /home/username/projects/ directory.<li><code>docker compose up</code><br>This will run the entire OED install process. Note that on some systems (mostly some Linux systems), depending on how you installed Docker, you may get a permission error so you will need to do:<br><code>sudo docker compose up</code><br>which runs the process with root privileges. If this is the case then you need to do sudo before all docker commands on your system.<br> Depending on the speed of your machine and internet connection, this can take a few to ten minutes. It should go faster after the first install. You will see a lot of output about installing the database (Postgres), getting needed packages (<strong>this can take a while so you may not see output for a while</strong>) and starting up the web system. When you see the line:<br> + 2073 hidden modules<br> where the actual number will likely be different then OED should be running normally unless there was an error in the output.</ol><li>The developer web pages assume you assess a terminal inside of the Docker container. Normally you can do this by going to the Docker icon for your running Docker and selecting the "Dashboard". Then look for your running OED container in the list. There should be an icon to the right that gives a "CLI". Clicking it should get you a command line interface for either the web or database container that OED uses. You can do other operations to control container through the same interface. You can also do this within VSC with the Docker extension even though you started OED outside VSC.<li>The developer pages often refer to output from OED. This goes to the nohup.out file with Visual Studio Code. When installed outside of VSC it will come to the terminal where you started OED, even in a terminal opened in VSC to install OED.</ol><h3>Getting help</h3><p>If you want help or have questions about running OED, then see the <a href="https://openenergydashboard.org/">website</a> or the documentation pages and contact information in the links on this page.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>OED Developer Documentation</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED appreciates that there is a lot of information and details on this page. They were developed from the experience of many developers. It is normally the case that developers that carefully follow the directions have no issues and can quickly and readily get OED working. If one does this and still have issues then please contact us. This page has the following main sections: Prerequisites: Steps/information needed before starting installation including the Contributors License Agreement and Windows OS considerations. GitHub: Using GitHub to get the OED repository (and a link for how to create pull requests). Docker: Getting Docker used for OED installation. IDE: The development IDE, esp. VSC. Install and run OED in a terminal: This is the current recommended way to run OED. Using OED: Using OED in a web browser and verifying it works correctly. OED Recommended VSC extensions Using an OED Docker terminal: How to run OED commands and access the Docker containers. Getting OED Docker information OED test data: Loading standard developer data into OED. Technologies OED uses Multi-author work: Suggestions on how teams can properly acknowledge group work. Issues: What to do if one has issues. Install and run OED in a VSC container: Another way to run OED (not the currently recommended one). Getting help These directions refer to a terminal. This is sometimes called a shell. These directions refer to changing to the main OED directory. This is the directory with the CODE_OF_CONDUCT.md and other files. To do this in a Unix/Linux terminal use cd &amp;lt;directory with cloned OED&amp;gt;. One needs to replace &amp;lt;directory with cloned OED&amp;gt; with the location of the cloned copy of OED. Some people find it easiest to locate that directory using the file manager on their OS and then use that information to get to the needed directory. As an example, one might do cd /home/username/projects/OED if one cloned OED in the /home/username/projects/ directory and used git clone without a . (period) at the end. The following steps should get one ready to contribute to OED in a fairly short period of time. Please know that OED is here to help so see the help section at the bottom of the page if one need it. Prerequisites Stay in contact with the OED project We strongly encourage anyone to contact the OED project as a potential developer. Visit our contact us page to join our Discord channel or reach our contact form. Doing this lets us know about you and OED can help you select tasks that will be interesting to you and also benefit the project. Contributor License Agreement Before one can submit work to OED, one needs to sign the Contributor&#39;s License Agreement. Windows OS If one is using Windows OS (version 10+) then one will want to use the Windows Subsystem for Linux (WSL) that allows Docker to run on Windows. Information for Windows OS developers will be displayed as shown here. It is important and generally necessary for success to follow the steps/information given in these items. Make sure ones WSL is fully installed correctly, following these steps. One should not use WSL-1. Installing WSL before Docker is helpful with the setup. These directions refer to Ubuntu since it is the most common Linux used with WSL and OED. However, any version of Linux should work similarly. If one does not care about the version of Ubuntu used, OED suggests the latest LTS (Long Term Support) version as that is very stable and supported. Other version should work fine. GitHub The OED project resides on GitHub so one needs a login to contribute to the project. OED uses the fork model for development. (There are many descriptions on the web of this process if one is not familiar with it. The GitHub ones include a general one and one with more operational details.) The basic steps are: If not already logged into ones GitHub account then do that. Go to the main OED GitHub page where the OED code resides. Fork the OED project onto ones own GitHub account by clicking the . After this completes, one should have a copy of the OED repository on ones own GitHub account. Clone the OED repository onto ones own development machine. The URL for cloning can be found by going to ones GitHub page, going to ones OED repository (the one forked), and clicking on the green &quot;Code&quot; drop down (). Note the clone will place all the files inside a new directory named OED unless one put a . (period) at the end of the git clone command, i.e., git clone &amp;lt;web location of ones OED GitHub fork&amp;gt; . where one replaces &amp;lt;web location of ones OED GitHub fork&amp;gt; with the actual location of one&#39;s OED fork. If one clones from the OED GitHub page rather than the clone from ones account of the forked version then one will not be able to easily push ones changes since one cannot write to the OED repository. This should be avoided. When using WSL, it is critical that one places the clone of OED on the Ubuntu file partition. Due to differences in how files are stored between Windows OS and Ubuntu, esp. the line ending character(s), failure to do this will lead to issues where code changes will not automatically be updated in the OED code bundle. This is consistent with the best practices given in the Docker WSL information (at least when this was written). The following steps will properly do this: 1. Open an Ubuntu terminal. One can search for “Ubuntu” from the Windows “Start” menu.This should open a terminal within the Ubuntu WSL system. 2. As desired, create a directory for the OED clone and cd to it. Note one can skip this and adding the . (period) at the end of the git clone if one is okay with it in the OED directory under the home directory of ones Ubuntu account. 3. Clone OED as described at the start of this step. This model has the advantage that one can commit and push to their account without needing write permission on the main OED project repository. There are separate directions of the steps for creating a pull request to integrate ones code into OED. Docker OED uses the Docker container system to run the software so one needs to download and install Docker. (One needs both Docker and docker compose but one generally gets those together during the install.) There are paid subscriptions but ones non-commercial work on the Open Source Software OED project does not require a paid subscription. This has the advantage that our configuration files for Docker can get any needed software and also means OED does not modify ones normal system since the setup is in a separate container that does not impact other programs on ones computer. Note that Docker should run on all OSes so one should be able to use it. One must have Docker running to be able to start OED. If it is not running then one will get error messages. One example is bash: /usr/bin/docker: No such file or directory but others happen. Note that if one runs within the VSC container then it may automatically try to start Docker. Make sure Docker is correctly configured to work with WSL following these steps. IDE (often VSC) One is are welcome to use any IDE for code development. Having said that, most OED developers use Visual Studio Code (VSC). tabs vs spaces OED expects all coding files to use tabs and not spaces for indenting. The rationale is each developer can choose how many spaces to use for each tab. If one uses the ESLint VSC extension then it should note any violations. The following may be useful to VSC users: One can tell if VSC is using spaces or tabs by looking at the information at the bottom of the VSC window. This highlights that VSC is usings spaces: . Onme can switch between spaces and tabs by clicking the spaces information shown above and select &quot;Indent Using Tabs&quot; as highlighted here: To convert the existing spaces to tabs, click the spaces information shown above and select &quot;Convert Indentation to Tabs&quot; as highlighted here: These VSC setting may help with controlling indentation: It is important one opens the OED directory in VSC within WSL. While it is fine to use the VSC command WSL: Open Folder in WSL..., it can be difficult to get to the Ubuntu partition the first time. It is often easier to do the following: 1. Open an Ubuntu terminal. One can search for “Ubuntu” from the Windows “Start” menu.This should open a terminal within the Ubuntu WSL system. 2. Go to the directory with the main OED file. 3. Enter code . and hit enter/return. This should start VSC on ones Windows OS system in the main OED directory as a normal window using the WSL system. Note the first time Linux may need to install VSC for use with Ubuntu; this normally happens automatically on Ubuntu. Note one should probably install VSC on Windows before doing this. If this worked correctly, one will see “[WSL: Ubuntu]” in the VSC “File Explorer” as seen here: . After opening the first time, one should be able to start VSC directly in Windows using the normal icon and have this directory in the recently used ones. One can repeat these steps for a new clone or if the directory is not shown in the recently opened ones. If one ever has a folder open outside WSL but it is actually on WSL then one can use the command to reopen in WSL (sometimes VSC will suggest one do that). It is very important that VSC show it is using WSL as in the figure above. Install and run OED in a terminal The OED repository contains the files necessary to automatically start OED in a VSC Docker container. Note this is a different container from the two Docker containers that OED uses to run. While this has some advantages as given below in the section on running with the OED VSC container, OED developers are currently experiencing failures when doing this. Given this, OED developers are encouraged to install/run OED as described in this section rather than using the VSC Docker container. Note this method generally starts up faster and uses less CPU/memory on ones computer. After opening the OED directory in VSC, VSC will typically ask if one wants to reopen the folder in a container by showing this message: To avoid opening in the VSC Docker container, click to close this alert. If one does not want to see this again, click the “Don’t Show Again…” button. While there is further information on more advanced options for doing this, the initial install can be done by following these steps: It is best that the terminal be in WSL/Ubuntu. If one followed the directions above to get VSC in WSL then the terminal opened in VSC will be in WSL/Ubuntu. One should not close this terminal until OED is shut down because it will receive all OED server message that can be valuable. Open a terminal on ones computer. It is fine to use a terminal within VSC. In the terminal do the following: If one opened the terminal within VSC while in the main OED directory then it will normally already be in the main OED directory and not need the next step. If not, one will need to switch to that directory. cd &quot;main OED directory&quot; In the past, some developers have used npm or other commands to start OED. OED recommends against doing this as it can cause issues with running and developing OED. docker compose up Note that on some systems (mostly some Linux systems), depending on how one installed Docker, one may get a permission error so one will need to do: sudo docker compose up which runs the process with root privileges. If this is the case then one needs to do sudo before all docker commands on thieir system or address this more globally. This will run the entire OED install process. Depending on the speed of ones machine and internet connection, this may take a few minutes. It should go faster after the first install. One will see a lot of output in the terminal where one started OED about installing the database (Postgres), getting needed packages (this can take a while so one may not see output for a while) and starting up the web system. Toward the end of the output one should see two items: web-1 | webpack 5.76.3 compiled successfully in 975 ms where the exact information may vary. What is important is it says successfully. If it has a failure message then something went wrong. web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100%. One will see a number of other lines with less than 100%. This final line indicates the build is done and the OED web server is ready to accept requests from a web browser. If one makes a web request before this line appears then one may get a connection denied, the old version (if making code changes) or an improper web page. Note the OED Docker containers will be started/running before OED can accept web connections. To stop OED, go to the terminal where OED was started and enter a single ^c (control and letter c). If a second ^c is entered then it will force stop OED and there is a chance the container will not be properly cleaned up so it is advised not to do this. If one cannot find the terminal where OED was started (may it was accidentally closed), then open another terminal as one did to start OED (in correct directory) and do docker compose down. A final option, if none of these work, is to stop the container within Docker. The developer pages often refer to output from OED. It will shown in the terminal where OED was started. Using OED Once OED is installed and running, one will want to open it in a web browser. It should not matter which one is used. Enter the address:localhost:3000 and load the page. &quot;localhost&quot; indicates the page is being served up from ones machine and &quot;3000&quot; is the default port that OED uses to accept web connections. If all went well, one will see the main OED web page that looks something like: If one see this then the basic OED install worked and their system is properly serving up the OED web system. Though not common, it is possible for the OED web system to run without starting the underlying database system. To verify that the database is running properly, one should log into OED as the admin. The username and password were shown during the install process. By default they are: email: test password: password Yes, the password really is password but remember it is running on ones local machine in a container so it should not be accessible to others. If it fails one should see a message appear briefly in the top, right corner of the page. If this happens, please follow the steps below to contact us and include any output in the terminal. If all went well, one now has a fully running development version of OED that can be used to begin coding. Congratulations! OED Recommended VSC extensions VSC has several extensions OED thinks are valuable. OED recommends that developers consider using them. These are automatically included in the OED VSC container. Docker: Allows one to work with Docker directly in VSC with many features of the Docker Desktop. Once installed it can be accessed by clicking the Docker icon (). GitLens — Git supercharged: This shows detailed information on Git commits, who made changes, file history and more. It makes working with Git inside VSC much nicer. ESLint: This checks that ones code is in a valid structure and format as generally used and required by OED. The automated OED checks on pull request submission will run similar tests so this helps avoid issues. Code Spell Checker: It will help one avoid spelling mistakes that lead to pull request comments as OED expects correct spelling. GitHub Pull Request: It lets one work with GitHub within VSC including creating, commenting on and working with pull requests all with VSC features. These can easily be installed (or see if it already is installed) using the VSC Extensions (). Using an OED Docker terminal Running a terminal in the OED Docker containers differs from running in a standard terminal on ones machine, including opening a terminal from the VSC “terminal” menu. The reason is that the OED Docker terminal has the full OED environment. If one runs outside the OED Docker container terminals then the result may be unpredictable. One can only attach a terminal to the OED Docker container if OED is running The developer web pages assume one assesses a terminal inside of the Docker container. There are two main ways of doing this: If one is using VSC with the Docker extension () then one can use it (see here for info). Right click on the desired OED Docker container and select &quot;Attach Shell&quot; as shown next: One normally gets a prompt similar to root@20124d33c2c7:/usr/src/app#. Using the Docker Desktop, go to containers, and use the drop down menu (three vertical dots) on the OED container to &quot;Open in terminal&quot; as shown next: One normally gets a prompt similar to #. The terminal in the OED Docker container runs as root. This allows the developer to make any desired change but also allows one to change/damage the OED information. Care should be used. Getting OED Docker information The following assumes one has the VSC Docker extension as described above. Similar information is available via the Docker Desktop. It should show information on all the Docker images/containers one has. The containers that are currently running have a green triangle next to them. One can get the following choices by right clicking on a container: View Logs: The web container will not show much since the OED output is in the terminal used to start oed (or in nohup.out if using the OED VSC container). The database one will show messages from PostgreSQL. These open a new terminal that one can remove with the trash can icon. Attach Shell: This puts one in a shell within the container that is using the OED environment (see for more info.). In the shell inside the database container one can do: psql -U oed to open the Postgres command line. This will allow one to look at the live OED database. One can also see the OED startup files for the database with ls docker-entrypoint-initdb.d. In the shell inside the web container, one can look at the environment variables or do other Linux operation. One can run any script in package.json, e.g., npm run check. One can see all the running processes with ps -aux. Inspect: Opens a JSON file that gives detailed information on the container that can be useful for debugging issues. Open in Browser: For the web container, this will go to localhost:3000. Stop, Remove: Stop or remove the container where stop is useful if something does not shut down properly. OED test data When one installs OED, it does not have any data. An actual site would connect up meters to gather data. For a developer, OED has standard test data one can use. The OED test data page has information and directions for doing this. OED suggests one loads up the data now so one can try any features desired in OED. Note that an advantage of this test data is that it is the same for all developers so people should be able to reproduce what one mentions if one has a question or issue. Technologies OED uses OED uses a number of technologies. One may want further information on these and some are provided on the OED technologies page. OED welcomes input on other areas people would like to know about or other resources one finds valuable. Note that one can work on parts of OED without knowing many of the technologies in any depth. For example, one can work on database queries without knowing about the front-end. Thus, many developers begin in areas they know or want to learn first and focus on that needed information. Having said that, almost the entire code base is in JavaScript/TypeScript so a basic understanding of that is usually needed to get started. Multi-author work It is common for a team to work on OED together. If one is doing this and want to give another person acknowledgement on a commit, then see GitHub info on multiple authors. Issues If anyone has any issues please copy the current output from the terminal used to start OED (or nohup.out if using the VSC OED container) and forward it along with any other information to the OED project by contacting us. We will look it over and get back to you. We try to do that quickly. It is also fine to send a message to the developer Discord channel to seek answers. Install and run OED in a VSC container This method has the advantages that one does not have to open a terminal or get all the recommended VSC extensions. However, developers have been having issues/failures with this method of running OED. Furthermore, this method generally starts up slower, uses more CPU/memory on ones computer and is harder to see OED developer messages. Given this, it should only be used when desired/necessary and the method of running in a terminal (described here) is normally recommended. See the section on OED VSC issues for more information. If the last install of OED was from the terminal then it is critical that the two OED containers are remove. The steps are part of the information in the OED VSC issues section. Note the same steps must be followed if going from the OED VSC Docker container to using a terminal install. This only works if one uses VSC as ones IDE. One needs to have the “Remote Development” VSC extension for this to work. Click on the Extensions manager icon on the far left of the VSC window () to see if one has it. If not, search for “Remote Development” and install it. One will get several Extensions included with this one. The OED repository contains the .devcontainer folder that allows VSC to automatically launch and set up the needed Docker containers. Here are the directions: This assumes one has opened the main OED directory in VSC as described above. Typically, VSC will ask to reopen the folder in a container by showing this message: One can click the button &quot;Reopen in Container&quot;. One will often see a popup in VSC that indicate one can click to see the log: The first time OED installs it can take a while where the time depends on the speed of ones machine and internet connection (to get the needed npm packages). One can see the output of the install and anything OED outputs to the console by looking at the file nohup.out that will be created in ones main OED directory. If one opens this in VSC it should update with new lines at the bottom as they are added. See full install output or install without Postgres or npm install output to see a typical install output and for information if something goes wrong. If one waits a while (depends on machine speed but normally not more than 5-10 minute) and doesn’t see the install output in nohup.out then something is likely wrong. Note if there is no nohup.out file then the install did not work. See below on possible issues and solutions. OED starts new output from an install with a line such as web-1 | ***** Starting install of OED at Sat Aug 31 21:18:28 UTC 2024 *****. Searching from the bottom of the file for **** and going upward should find the latest install output. If VSC does not automatically ask to open in a container, one can click the “Remote Container” icon () that is normally in the bottom, left of the VSC window and select “Reopen in Container” for the menu that appears. Once OED is running one should be able to see the web and database Docker containers running via Docker (either the VSC extension or the desktop). See Docker information for more info on doing this. One can shut down the OED VSC container by clicking the green icon for the Remote Container and selecting &quot;Close Remote Container&quot;. All output from the OED server will show in the nohup.out file located in the main OED directory. The latest information is at the bottom. OED VSC issues As mentioned above, developers are experiencing issues using this system. These mostly revolve around the install failing. When this happens, it is often fixed by doing the following: Exiting the OED VSC Docker container by clicking the green icon for the Remote Container and selecting &quot;Close Remote Container&quot;. Normally the OED Docker containers will not be running but stop them using Docker as described above. Remove both OED Docker containers (web and database) but not the images as described above. Try restarting OED by reopening the OED VSC container as described above. If one rebuilds the VSC container too soon after a build failure then it may fail again. Normally the time taken for the steps above avoids this. However, if the rebuild is being done right away then it is best to wait a few seconds before attempting. Getting help If anyone wants help or have questions about running OED, then see the website or the documentation pages and contact information in the links on this page."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/gettingStarted/"><meta property="og:title" content="OED Developer Documentation"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED appreciates that there is a lot of information and details on this page. They were developed from the experience of many developers. It is normally the case that developers that carefully follow the directions have no issues and can quickly and readily get OED working. If one does this and still have issues then please contact us. This page has the following main sections: Prerequisites: Steps/information needed before starting installation including the Contributors License Agreement and Windows OS considerations. GitHub: Using GitHub to get the OED repository (and a link for how to create pull requests). Docker: Getting Docker used for OED installation. IDE: The development IDE, esp. VSC. Install and run OED in a terminal: This is the current recommended way to run OED. Using OED: Using OED in a web browser and verifying it works correctly. OED Recommended VSC extensions Using an OED Docker terminal: How to run OED commands and access the Docker containers. Getting OED Docker information OED test data: Loading standard developer data into OED. Technologies OED uses Multi-author work: Suggestions on how teams can properly acknowledge group work. Issues: What to do if one has issues. Install and run OED in a VSC container: Another way to run OED (not the currently recommended one). Getting help These directions refer to a terminal. This is sometimes called a shell. These directions refer to changing to the main OED directory. This is the directory with the CODE_OF_CONDUCT.md and other files. To do this in a Unix/Linux terminal use cd &amp;lt;directory with cloned OED&amp;gt;. One needs to replace &amp;lt;directory with cloned OED&amp;gt; with the location of the cloned copy of OED. Some people find it easiest to locate that directory using the file manager on their OS and then use that information to get to the needed directory. As an example, one might do cd /home/username/projects/OED if one cloned OED in the /home/username/projects/ directory and used git clone without a . (period) at the end. The following steps should get one ready to contribute to OED in a fairly short period of time. Please know that OED is here to help so see the help section at the bottom of the page if one need it. Prerequisites Stay in contact with the OED project We strongly encourage anyone to contact the OED project as a potential developer. Visit our contact us page to join our Discord channel or reach our contact form. Doing this lets us know about you and OED can help you select tasks that will be interesting to you and also benefit the project. Contributor License Agreement Before one can submit work to OED, one needs to sign the Contributor&#39;s License Agreement. Windows OS If one is using Windows OS (version 10+) then one will want to use the Windows Subsystem for Linux (WSL) that allows Docker to run on Windows. Information for Windows OS developers will be displayed as shown here. It is important and generally necessary for success to follow the steps/information given in these items. Make sure ones WSL is fully installed correctly, following these steps. One should not use WSL-1. Installing WSL before Docker is helpful with the setup. These directions refer to Ubuntu since it is the most common Linux used with WSL and OED. However, any version of Linux should work similarly. If one does not care about the version of Ubuntu used, OED suggests the latest LTS (Long Term Support) version as that is very stable and supported. Other version should work fine. GitHub The OED project resides on GitHub so one needs a login to contribute to the project. OED uses the fork model for development. (There are many descriptions on the web of this process if one is not familiar with it. The GitHub ones include a general one and one with more operational details.) The basic steps are: If not already logged into ones GitHub account then do that. Go to the main OED GitHub page where the OED code resides. Fork the OED project onto ones own GitHub account by clicking the . After this completes, one should have a copy of the OED repository on ones own GitHub account. Clone the OED repository onto ones own development machine. The URL for cloning can be found by going to ones GitHub page, going to ones OED repository (the one forked), and clicking on the green &quot;Code&quot; drop down (). Note the clone will place all the files inside a new directory named OED unless one put a . (period) at the end of the git clone command, i.e., git clone &amp;lt;web location of ones OED GitHub fork&amp;gt; . where one replaces &amp;lt;web location of ones OED GitHub fork&amp;gt; with the actual location of one&#39;s OED fork. If one clones from the OED GitHub page rather than the clone from ones account of the forked version then one will not be able to easily push ones changes since one cannot write to the OED repository. This should be avoided. When using WSL, it is critical that one places the clone of OED on the Ubuntu file partition. Due to differences in how files are stored between Windows OS and Ubuntu, esp. the line ending character(s), failure to do this will lead to issues where code changes will not automatically be updated in the OED code bundle. This is consistent with the best practices given in the Docker WSL information (at least when this was written). The following steps will properly do this: 1. Open an Ubuntu terminal. One can search for “Ubuntu” from the Windows “Start” menu.This should open a terminal within the Ubuntu WSL system. 2. As desired, create a directory for the OED clone and cd to it. Note one can skip this and adding the . (period) at the end of the git clone if one is okay with it in the OED directory under the home directory of ones Ubuntu account. 3. Clone OED as described at the start of this step. This model has the advantage that one can commit and push to their account without needing write permission on the main OED project repository. There are separate directions of the steps for creating a pull request to integrate ones code into OED. Docker OED uses the Docker container system to run the software so one needs to download and install Docker. (One needs both Docker and docker compose but one generally gets those together during the install.) There are paid subscriptions but ones non-commercial work on the Open Source Software OED project does not require a paid subscription. This has the advantage that our configuration files for Docker can get any needed software and also means OED does not modify ones normal system since the setup is in a separate container that does not impact other programs on ones computer. Note that Docker should run on all OSes so one should be able to use it. One must have Docker running to be able to start OED. If it is not running then one will get error messages. One example is bash: /usr/bin/docker: No such file or directory but others happen. Note that if one runs within the VSC container then it may automatically try to start Docker. Make sure Docker is correctly configured to work with WSL following these steps. IDE (often VSC) One is are welcome to use any IDE for code development. Having said that, most OED developers use Visual Studio Code (VSC). tabs vs spaces OED expects all coding files to use tabs and not spaces for indenting. The rationale is each developer can choose how many spaces to use for each tab. If one uses the ESLint VSC extension then it should note any violations. The following may be useful to VSC users: One can tell if VSC is using spaces or tabs by looking at the information at the bottom of the VSC window. This highlights that VSC is usings spaces: . Onme can switch between spaces and tabs by clicking the spaces information shown above and select &quot;Indent Using Tabs&quot; as highlighted here: To convert the existing spaces to tabs, click the spaces information shown above and select &quot;Convert Indentation to Tabs&quot; as highlighted here: These VSC setting may help with controlling indentation: It is important one opens the OED directory in VSC within WSL. While it is fine to use the VSC command WSL: Open Folder in WSL..., it can be difficult to get to the Ubuntu partition the first time. It is often easier to do the following: 1. Open an Ubuntu terminal. One can search for “Ubuntu” from the Windows “Start” menu.This should open a terminal within the Ubuntu WSL system. 2. Go to the directory with the main OED file. 3. Enter code . and hit enter/return. This should start VSC on ones Windows OS system in the main OED directory as a normal window using the WSL system. Note the first time Linux may need to install VSC for use with Ubuntu; this normally happens automatically on Ubuntu. Note one should probably install VSC on Windows before doing this. If this worked correctly, one will see “[WSL: Ubuntu]” in the VSC “File Explorer” as seen here: . After opening the first time, one should be able to start VSC directly in Windows using the normal icon and have this directory in the recently used ones. One can repeat these steps for a new clone or if the directory is not shown in the recently opened ones. If one ever has a folder open outside WSL but it is actually on WSL then one can use the command to reopen in WSL (sometimes VSC will suggest one do that). It is very important that VSC show it is using WSL as in the figure above. Install and run OED in a terminal The OED repository contains the files necessary to automatically start OED in a VSC Docker container. Note this is a different container from the two Docker containers that OED uses to run. While this has some advantages as given below in the section on running with the OED VSC container, OED developers are currently experiencing failures when doing this. Given this, OED developers are encouraged to install/run OED as described in this section rather than using the VSC Docker container. Note this method generally starts up faster and uses less CPU/memory on ones computer. After opening the OED directory in VSC, VSC will typically ask if one wants to reopen the folder in a container by showing this message: To avoid opening in the VSC Docker container, click to close this alert. If one does not want to see this again, click the “Don’t Show Again…” button. While there is further information on more advanced options for doing this, the initial install can be done by following these steps: It is best that the terminal be in WSL/Ubuntu. If one followed the directions above to get VSC in WSL then the terminal opened in VSC will be in WSL/Ubuntu. One should not close this terminal until OED is shut down because it will receive all OED server message that can be valuable. Open a terminal on ones computer. It is fine to use a terminal within VSC. In the terminal do the following: If one opened the terminal within VSC while in the main OED directory then it will normally already be in the main OED directory and not need the next step. If not, one will need to switch to that directory. cd &quot;main OED directory&quot; In the past, some developers have used npm or other commands to start OED. OED recommends against doing this as it can cause issues with running and developing OED. docker compose up Note that on some systems (mostly some Linux systems), depending on how one installed Docker, one may get a permission error so one will need to do: sudo docker compose up which runs the process with root privileges. If this is the case then one needs to do sudo before all docker commands on thieir system or address this more globally. This will run the entire OED install process. Depending on the speed of ones machine and internet connection, this may take a few minutes. It should go faster after the first install. One will see a lot of output in the terminal where one started OED about installing the database (Postgres), getting needed packages (this can take a while so one may not see output for a while) and starting up the web system. Toward the end of the output one should see two items: web-1 | webpack 5.76.3 compiled successfully in 975 ms where the exact information may vary. What is important is it says successfully. If it has a failure message then something went wrong. web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100%. One will see a number of other lines with less than 100%. This final line indicates the build is done and the OED web server is ready to accept requests from a web browser. If one makes a web request before this line appears then one may get a connection denied, the old version (if making code changes) or an improper web page. Note the OED Docker containers will be started/running before OED can accept web connections. To stop OED, go to the terminal where OED was started and enter a single ^c (control and letter c). If a second ^c is entered then it will force stop OED and there is a chance the container will not be properly cleaned up so it is advised not to do this. If one cannot find the terminal where OED was started (may it was accidentally closed), then open another terminal as one did to start OED (in correct directory) and do docker compose down. A final option, if none of these work, is to stop the container within Docker. The developer pages often refer to output from OED. It will shown in the terminal where OED was started. Using OED Once OED is installed and running, one will want to open it in a web browser. It should not matter which one is used. Enter the address:localhost:3000 and load the page. &quot;localhost&quot; indicates the page is being served up from ones machine and &quot;3000&quot; is the default port that OED uses to accept web connections. If all went well, one will see the main OED web page that looks something like: If one see this then the basic OED install worked and their system is properly serving up the OED web system. Though not common, it is possible for the OED web system to run without starting the underlying database system. To verify that the database is running properly, one should log into OED as the admin. The username and password were shown during the install process. By default they are: email: test password: password Yes, the password really is password but remember it is running on ones local machine in a container so it should not be accessible to others. If it fails one should see a message appear briefly in the top, right corner of the page. If this happens, please follow the steps below to contact us and include any output in the terminal. If all went well, one now has a fully running development version of OED that can be used to begin coding. Congratulations! OED Recommended VSC extensions VSC has several extensions OED thinks are valuable. OED recommends that developers consider using them. These are automatically included in the OED VSC container. Docker: Allows one to work with Docker directly in VSC with many features of the Docker Desktop. Once installed it can be accessed by clicking the Docker icon (). GitLens — Git supercharged: This shows detailed information on Git commits, who made changes, file history and more. It makes working with Git inside VSC much nicer. ESLint: This checks that ones code is in a valid structure and format as generally used and required by OED. The automated OED checks on pull request submission will run similar tests so this helps avoid issues. Code Spell Checker: It will help one avoid spelling mistakes that lead to pull request comments as OED expects correct spelling. GitHub Pull Request: It lets one work with GitHub within VSC including creating, commenting on and working with pull requests all with VSC features. These can easily be installed (or see if it already is installed) using the VSC Extensions (). Using an OED Docker terminal Running a terminal in the OED Docker containers differs from running in a standard terminal on ones machine, including opening a terminal from the VSC “terminal” menu. The reason is that the OED Docker terminal has the full OED environment. If one runs outside the OED Docker container terminals then the result may be unpredictable. One can only attach a terminal to the OED Docker container if OED is running The developer web pages assume one assesses a terminal inside of the Docker container. There are two main ways of doing this: If one is using VSC with the Docker extension () then one can use it (see here for info). Right click on the desired OED Docker container and select &quot;Attach Shell&quot; as shown next: One normally gets a prompt similar to root@20124d33c2c7:/usr/src/app#. Using the Docker Desktop, go to containers, and use the drop down menu (three vertical dots) on the OED container to &quot;Open in terminal&quot; as shown next: One normally gets a prompt similar to #. The terminal in the OED Docker container runs as root. This allows the developer to make any desired change but also allows one to change/damage the OED information. Care should be used. Getting OED Docker information The following assumes one has the VSC Docker extension as described above. Similar information is available via the Docker Desktop. It should show information on all the Docker images/containers one has. The containers that are currently running have a green triangle next to them. One can get the following choices by right clicking on a container: View Logs: The web container will not show much since the OED output is in the terminal used to start oed (or in nohup.out if using the OED VSC container). The database one will show messages from PostgreSQL. These open a new terminal that one can remove with the trash can icon. Attach Shell: This puts one in a shell within the container that is using the OED environment (see for more info.). In the shell inside the database container one can do: psql -U oed to open the Postgres command line. This will allow one to look at the live OED database. One can also see the OED startup files for the database with ls docker-entrypoint-initdb.d. In the shell inside the web container, one can look at the environment variables or do other Linux operation. One can run any script in package.json, e.g., npm run check. One can see all the running processes with ps -aux. Inspect: Opens a JSON file that gives detailed information on the container that can be useful for debugging issues. Open in Browser: For the web container, this will go to localhost:3000. Stop, Remove: Stop or remove the container where stop is useful if something does not shut down properly. OED test data When one installs OED, it does not have any data. An actual site would connect up meters to gather data. For a developer, OED has standard test data one can use. The OED test data page has information and directions for doing this. OED suggests one loads up the data now so one can try any features desired in OED. Note that an advantage of this test data is that it is the same for all developers so people should be able to reproduce what one mentions if one has a question or issue. Technologies OED uses OED uses a number of technologies. One may want further information on these and some are provided on the OED technologies page. OED welcomes input on other areas people would like to know about or other resources one finds valuable. Note that one can work on parts of OED without knowing many of the technologies in any depth. For example, one can work on database queries without knowing about the front-end. Thus, many developers begin in areas they know or want to learn first and focus on that needed information. Having said that, almost the entire code base is in JavaScript/TypeScript so a basic understanding of that is usually needed to get started. Multi-author work It is common for a team to work on OED together. If one is doing this and want to give another person acknowledgement on a commit, then see GitHub info on multiple authors. Issues If anyone has any issues please copy the current output from the terminal used to start OED (or nohup.out if using the VSC OED container) and forward it along with any other information to the OED project by contacting us. We will look it over and get back to you. We try to do that quickly. It is also fine to send a message to the developer Discord channel to seek answers. Install and run OED in a VSC container This method has the advantages that one does not have to open a terminal or get all the recommended VSC extensions. However, developers have been having issues/failures with this method of running OED. Furthermore, this method generally starts up slower, uses more CPU/memory on ones computer and is harder to see OED developer messages. Given this, it should only be used when desired/necessary and the method of running in a terminal (described here) is normally recommended. See the section on OED VSC issues for more information. If the last install of OED was from the terminal then it is critical that the two OED containers are remove. The steps are part of the information in the OED VSC issues section. Note the same steps must be followed if going from the OED VSC Docker container to using a terminal install. This only works if one uses VSC as ones IDE. One needs to have the “Remote Development” VSC extension for this to work. Click on the Extensions manager icon on the far left of the VSC window () to see if one has it. If not, search for “Remote Development” and install it. One will get several Extensions included with this one. The OED repository contains the .devcontainer folder that allows VSC to automatically launch and set up the needed Docker containers. Here are the directions: This assumes one has opened the main OED directory in VSC as described above. Typically, VSC will ask to reopen the folder in a container by showing this message: One can click the button &quot;Reopen in Container&quot;. One will often see a popup in VSC that indicate one can click to see the log: The first time OED installs it can take a while where the time depends on the speed of ones machine and internet connection (to get the needed npm packages). One can see the output of the install and anything OED outputs to the console by looking at the file nohup.out that will be created in ones main OED directory. If one opens this in VSC it should update with new lines at the bottom as they are added. See full install output or install without Postgres or npm install output to see a typical install output and for information if something goes wrong. If one waits a while (depends on machine speed but normally not more than 5-10 minute) and doesn’t see the install output in nohup.out then something is likely wrong. Note if there is no nohup.out file then the install did not work. See below on possible issues and solutions. OED starts new output from an install with a line such as web-1 | ***** Starting install of OED at Sat Aug 31 21:18:28 UTC 2024 *****. Searching from the bottom of the file for **** and going upward should find the latest install output. If VSC does not automatically ask to open in a container, one can click the “Remote Container” icon () that is normally in the bottom, left of the VSC window and select “Reopen in Container” for the menu that appears. Once OED is running one should be able to see the web and database Docker containers running via Docker (either the VSC extension or the desktop). See Docker information for more info on doing this. One can shut down the OED VSC container by clicking the green icon for the Remote Container and selecting &quot;Close Remote Container&quot;. All output from the OED server will show in the nohup.out file located in the main OED directory. The latest information is at the bottom. OED VSC issues As mentioned above, developers are experiencing issues using this system. These mostly revolve around the install failing. When this happens, it is often fixed by doing the following: Exiting the OED VSC Docker container by clicking the green icon for the Remote Container and selecting &quot;Close Remote Container&quot;. Normally the OED Docker containers will not be running but stop them using Docker as described above. Remove both OED Docker containers (web and database) but not the images as described above. Try restarting OED by reopening the OED VSC container as described above. If one rebuilds the VSC container too soon after a build failure then it may fail again. Normally the time taken for the steps above avoids this. However, if the rebuild is being done right away then it is best to wait a few seconds before attempting. Getting help If anyone wants help or have questions about running OED, then see the website or the documentation pages and contact information in the links on this page."><meta property="og:url" content="https://openenergydashboard.org/developer/gettingStarted/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Developer First Steps</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">Developer Startup<h1>Developer First Steps</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><div class="alert-box info "><p>OED appreciates that there is a lot of information and details on this page. They were developed from the experience of many developers. It is normally the case that developers that carefully follow the directions have no issues and can quickly and readily get OED working. If one does this and still have issues then please <a href="/contact/">contact us</a>.</div><p>This page has the following main sections:<ol><li><a href="#prerequisites">Prerequisites</a>: Steps/information needed before starting installation including the <a href="#cla">Contributors License Agreement</a> and <a href="#windowsOS">Windows OS considerations</a>.<li><a href="#github">GitHub</a>: Using GitHub to get the OED repository (and a link for how to create pull requests).<li><a href="#docker">Docker</a>: Getting Docker used for OED installation.<li><a href="#ide">IDE</a>: The development IDE, esp. VSC.<li><a href="#terminalInstall">Install and run OED in a terminal</a>: This is the current recommended way to run OED.<li><a href="#usingOED">Using OED</a>: Using OED in a web browser and verifying it works correctly.<li><a href="#VSCExtentions">OED Recommended VSC extensions</a><li><a href="#OEDDockerTerminal">Using an OED Docker terminal</a>: How to run OED commands and access the Docker containers.<li><a href="#DockerInfo">Getting OED Docker information</a><li><a href="#testData">OED test data</a>: Loading standard developer data into OED.<li><a href="#technologies">Technologies OED uses</a><li><a href="#multiauthor">Multi-author work</a>: Suggestions on how teams can properly acknowledge group work.<li><a href="#issues">Issues</a>: What to do if one has issues.<li><a href="#VSCInstall">Install and run OED in a VSC container</a>: Another way to run OED (not the currently recommended one).<li><a href="#help">Getting help</a></ol><div class="alert-box info "><p>These directions refer to a terminal. This is sometimes called a shell.</div><div class="alert-box info "><p>These directions refer to changing to the main OED directory. This is the directory with the <code>CODE_OF_CONDUCT.md</code> and other files. To do this in a Unix/Linux terminal use <code>cd &lt;directory with cloned OED&gt;</code>. One needs to replace <code>&lt;directory with cloned OED&gt;</code> with the location of the cloned copy of OED. Some people find it easiest to locate that directory using the file manager on their OS and then use that information to get to the needed directory. As an example, one might do <code>cd /home/username/projects/OED</code> if one cloned OED in the <code>/home/username/projects/</code> directory and used <code>git clone</code> without a . (period) at the end.</div><p>The following steps should get one ready to contribute to OED in a fairly short period of time. Please know that OED is here to help so see the <a href="#help">help section</a> at the bottom of the page if one need it.<h3 id="prerequisites">Prerequisites</h3><h4>Stay in contact with the OED project</h4><p>We strongly encourage anyone to contact the OED project as a potential developer. Visit our <a href="https://openenergydashboard.org/contact/">contact us</a> page to join our Discord channel or reach our contact form. Doing this lets us know about you and OED can help you select tasks that will be interesting to you and also benefit the project.<h4 id="cla">Contributor License Agreement</h4><p>Before one can submit work to OED, one needs to sign the <a href="../cla/">Contributor's License Agreement</a>.<h4 id="windowsOS">Windows OS</h4><p>If one is using Windows OS (version 10+) then one will want to use the Windows Subsystem for Linux (WSL) that allows Docker to run on Windows.<div class="alert-box windowsOS "><p>Information for Windows OS developers will be displayed as shown here. It is important and generally necessary for success to follow the steps/information given in these items.</div><div class="alert-box windowsOS "><p>Make sure ones WSL is fully installed correctly, following <a href="https://learn.microsoft.com/en-us/windows/wsl/install" rel="noopener noreferrer">these steps</a>. One should <strong>not</strong> use WSL-1. Installing WSL before Docker is helpful with the setup.</div><div class="alert-box windowsOS "><p>These directions refer to Ubuntu since it is the most common Linux used with WSL and OED. However, any version of Linux should work similarly. If one does not care about the version of Ubuntu used, OED suggests the latest LTS (Long Term Support) version as that is very stable and supported. Other version should work fine.</div><h3 id="github">GitHub</h3><p>The OED project resides on <a href="https://github.com/" rel="noopener noreferrer">GitHub</a> so one needs a login to contribute to the project.<p>OED uses the fork model for development. (There are many descriptions on the web of this process if one is not familiar with it. The GitHub ones include a <a href="https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project" rel="noopener noreferrer">general one</a> and one with <a href="https://docs.github.com/get-started/quickstart/fork-a-repo" rel="noopener noreferrer">more operational details</a>.) The basic steps are:<ol><li>If not already logged into ones GitHub account then do that.<li>Go to the <a href="https://github.com/OpenEnergyDashboard/OED">main OED GitHub page</a> where the OED code resides.<li>Fork the OED project onto ones own GitHub account by clicking the <img alt="GitHub Fork button" src="../images/forkButton.png">. After this completes, one should have a copy of the OED repository on ones own GitHub account.<li>Clone the OED repository onto ones own development machine. The URL for cloning can be found by going to ones GitHub page, going to ones OED repository (the one forked), and clicking on the green "Code" drop down (<img alt="GitHub clone URL" src="../images/cloneURL.png">). Note the clone will place all the files inside a new directory named OED unless one put a . (period) at the end of the <code>git clone</code> command, i.e., <code>git clone &lt;web location of ones OED GitHub fork&gt; .</code> where one replaces <code>&lt;web location of ones OED GitHub fork&gt;</code> with the actual location of one's OED fork.</ol><div class="alert-box warning "><p>If one clones from the OED GitHub page rather than the clone from ones account of the forked version then one will not be able to easily push ones changes since one cannot write to the OED repository. This should be avoided.</div><div class="alert-box windowsOS "><p>When using WSL, it is critical that one places the clone of OED on the Ubuntu file partition. Due to differences in how files are stored between Windows OS and Ubuntu, esp. the line ending character(s), failure to do this will lead to issues where code changes will not automatically be updated in the OED code bundle. This is consistent with the best practices given in the <a href="https://docs.docker.com/desktop/wsl/best-practices/" rel="noopener noreferrer">Docker WSL information</a> (at least when this was written). The following steps will properly do this: <br />1. Open an Ubuntu terminal. One can search for “Ubuntu” from the Windows “Start” menu.<br /><img alt="getting to Ubuntu terminal" src="../images/ubuntu.png" /><br />This should open a terminal within the Ubuntu WSL system. <br />2. As desired, create a directory for the OED clone and <code>cd</code> to it. Note one can skip this and adding the . (period) at the end of the <code>git clone</code> if one is okay with it in the OED directory under the home directory of ones Ubuntu account. <br />3. Clone OED as described at the start of this step.</div><p>This model has the advantage that one can commit and push to their account without needing write permission on the main OED project repository.<p>There are <a href="../pr/">separate directions</a> of the steps for creating a pull request to integrate ones code into OED.<h3 id="docker">Docker</h3><p>OED uses the Docker container system to run the software so one needs to <a href="https://www.docker.com/products/docker-desktop/" rel="noopener noreferrer">download</a> and install Docker. (One needs both Docker and docker compose but one generally gets those together during the install.) There are paid subscriptions but ones non-commercial work on the Open Source Software OED project does not require a paid subscription. This has the advantage that our configuration files for Docker can get any needed software and also means OED does not modify ones normal system since the setup is in a separate container that does not impact other programs on ones computer. Note that Docker should run on all OSes so one should be able to use it.<div class="alert-box info "><p>One must have Docker running to be able to start OED. If it is not running then one will get error messages. One example is <code>bash: /usr/bin/docker: No such file or directory</code> but others happen. Note that if one runs within the VSC container then it may automatically try to start Docker.</div><div class="alert-box windowsOS "><p>Make sure Docker is correctly configured to work with WSL following <a href="https://docs.docker.com/desktop/wsl/" rel="noopener noreferrer">these steps</a>.</div><h3 id="ide">IDE (often VSC)</h3><p>One is are welcome to use any IDE for code development. Having said that, most OED developers use <a href="https://code.visualstudio.com/" rel="noopener noreferrer">Visual Studio Code</a> (VSC).<h4>tabs vs spaces</h4><p>OED expects all coding files to use tabs and not spaces for indenting. The rationale is each developer can choose how many spaces to use for each tab. If one uses the <a href="#VSCExtentions">ESLint VSC extension</a> then it should note any violations. The following may be useful to VSC users:<ul><li>One can tell if VSC is using spaces or tabs by looking at the information at the bottom of the VSC window. This highlights that VSC is usings spaces: <img alt="VSC spaces info" src="../images/VSCSpacesTabs.png" />.<li>Onme can switch between spaces and tabs by clicking the spaces information shown above and select "Indent Using Tabs" as highlighted here: <br><img alt="VSC spaces to tabs for indent" src="../images/VSCIndentTabs.png" /><li>To convert the existing spaces to tabs, click the spaces information shown above and select "Convert Indentation to Tabs" as highlighted here: <br><img alt="VSC convert spaces to tabs for indent" src="../images/VSCConvertTabs.png" /><li>These VSC setting may help with controlling indentation: <br><img alt="VSC indent settings" src="../images/VSCIndentSettings.png" /></ul><div class="alert-box windowsOS "><p>It is important one opens the OED directory in VSC within WSL. While it is fine to use the VSC command <code>WSL: Open Folder in WSL...</code>, it can be difficult to get to the Ubuntu partition the first time. It is often easier to do the following: <br />1. Open an Ubuntu terminal. One can search for “Ubuntu” from the Windows “Start” menu.<br /><img alt="getting to Ubuntu terminal" src="../images/ubuntu.png" /><br />This should open a terminal within the Ubuntu WSL system. <br />2. Go to the directory with the main OED file. <br />3. Enter <code>code .</code> and hit enter/return. This should start VSC on ones Windows OS system in the main OED directory as a normal window using the WSL system. Note the first time Linux may need to install VSC for use with Ubuntu; this normally happens automatically on Ubuntu. Note one should probably <a href="#ide">install VSC</a> on Windows before doing this. <br />If this worked correctly, one will see “[WSL: Ubuntu]” in the VSC “File Explorer” as seen here: <br /><img alt="WSL indicated in VSC File Explorer" src="../images/VSCWSL.png" />. <br />After opening the first time, one should be able to start VSC directly in Windows using the normal icon and have this directory in the recently used ones. One can repeat these steps for a new clone or if the directory is not shown in the recently opened ones. If one ever has a folder open outside WSL but it is actually on WSL then one can use the command to reopen in WSL (sometimes VSC will suggest one do that). It is very important that VSC show it is using WSL as in the figure above.</div><h3 id="terminalInstall">Install and run OED in a terminal</h3><div class="alert-box warning "><p>The OED repository contains the files necessary to automatically start OED in a VSC Docker container. Note this is a different container from the two Docker containers that OED uses to run. While this has some advantages as given below in the <a href="#VSCInstall">section on running with the OED VSC container</a>, OED developers are currently experiencing failures when doing this. Given this, OED developers are encouraged to install/run OED as described in this section rather than using the VSC Docker container. Note this method generally starts up faster and uses less CPU/memory on ones computer. <br />After opening the OED directory in VSC, VSC will typically ask if one wants to reopen the folder in a container by showing this message: <br /><img alt="VSC container msg" src="../images/VSCContainerMsg.png" style="width: 25vw; min-width: 200px;" /> <br />To avoid opening in the VSC Docker container, click to close this alert. If one does not want to see this again, click the “Don’t Show Again…” button.</div><p>While there is <a href="../devDetails/">further information</a> on more advanced options for doing this, the initial install can be done by following these steps:<ol><div class="alert-box windowsOS "><p>It is best that the terminal be in WSL/Ubuntu. If one followed the directions above to get VSC in WSL then the terminal opened in VSC will be in WSL/Ubuntu.</div><div class="alert-box info "><p>One should not close this terminal until OED is shut down because it will receive all OED server message that can be valuable.</div><li>Open a terminal on ones computer. It is fine to use a terminal within VSC. In the terminal do the following:<ol><div class="alert-box info "><p>If one opened the terminal within VSC while in the main OED directory then it will normally already be in the main OED directory and not need the next step. If not, one will need to switch to that directory.</div><li><code>cd "main OED directory"</code><div class="alert-box warning "><p>In the past, some developers have used npm or other commands to start OED. OED recommends against doing this as it can cause issues with running and developing OED.</div><li><code>docker compose up</code><div class="alert-box info "><p>Note that on some systems (mostly some Linux systems), depending on how one installed Docker, one may get a permission error so one will need to do: <code>sudo docker compose up</code> which runs the process with root privileges. If this is the case then one needs to do sudo before all docker commands on thieir system or address this more globally.</div>This will run the entire OED install process. <br>Depending on the speed of ones machine and internet connection, this may take a few minutes. It should go faster after the first install. One will see a lot of output in the terminal where one started OED about installing the database (Postgres), getting needed packages (<strong>this can take a while so one may not see output for a while</strong>) and starting up the web system. Toward the end of the output one should see two items:<ul><li><code>web-1 | webpack 5.76.3 compiled successfully in 975 ms</code> where the exact information may vary. What is important is it says <code>successfully</code>. If it has a failure message then something went wrong.<li><code>web-1 | &lt;s&gt; [webpack.Progress] 100%</code>. One will see a number of other lines with less than 100%. This final line indicates the build is done and the OED web server is ready to accept requests from a web browser.<div class="alert-box warning "><p>If one makes a web request before this line appears then one may get a connection denied, the old version (if making code changes) or an improper web page. Note the OED Docker containers will be started/running before OED can accept web connections.</div></ol><li>To stop OED, go to the terminal where OED was started and enter a <strong>single ^c</strong> (control and letter c). If a second ^c is entered then it will force stop OED and there is a chance the container will not be properly cleaned up so it is advised not to do this. If one cannot find the terminal where OED was started (may it was accidentally closed), then open another terminal as one did to start OED (in correct directory) and do <code>docker compose down</code>. A final option, if none of these work, is to stop the container within Docker.<li>The developer pages often refer to output from OED. It will shown in the terminal where OED was started.</ol><h3 id="usingOED">Using OED</h3><ol><li>Once OED is installed and running, one will want to open it in a web browser. It should not matter which one is used. Enter the address:<code>localhost:3000</code> and load the page. "localhost" indicates the page is being served up from ones machine and "3000" is the default port that OED uses to accept web connections. If all went well, one will see the main OED web page that looks something like:<p><img alt="OED Main Page" src="../images/startupMainPage.png" /> If one see this then the basic OED install worked and their system is properly serving up the OED web system.<li>Though not common, it is possible for the OED web system to run without starting the underlying database system. To verify that the database is running properly, one should <a href="https://openenergydashboard.org/helpV1_0_0/optionsMenu/">log into OED</a> as the admin. The username and password were shown during the install process. By default they are:<br> email: test<br> password: password<br> Yes, the password really is password but remember it is running on ones local machine in a container so it should not be accessible to others. If it fails one should see a message appear briefly in the top, right corner of the page. If this happens, please follow the <a href="#sendConsole">steps below</a> to contact us and include any output in the terminal.<li>If all went well, one now has a fully running development version of OED that can be used to begin coding. Congratulations!</ol><h3 id="VSCExtentions">OED Recommended VSC extensions</h3><p>VSC has several extensions OED thinks are valuable. OED recommends that developers consider using them. These are automatically included in the OED VSC container.<ul><li>Docker: Allows one to work with Docker directly in VSC with many features of the Docker Desktop. Once installed it can be accessed by clicking the Docker icon (<img alt="VSC container msg" src="../images/dockerIcon.png">).<li>GitLens — Git supercharged: This shows detailed information on Git commits, who made changes, file history and more. It makes working with Git inside VSC much nicer.<li>ESLint: This checks that ones code is in a valid structure and format as generally used and required by OED. The automated OED checks on pull request submission will run similar tests so this helps avoid issues.<li>Code Spell Checker: It will help one avoid spelling mistakes that lead to pull request comments as OED expects correct spelling.<li>GitHub Pull Request: It lets one work with GitHub within VSC including creating, commenting on and working with pull requests all with VSC features.</ul><p>These can easily be installed (or see if it already is installed) using the VSC Extensions (<img alt="VSC Extension icon" src="../images/VSCExtensions.png">).<h3 id="OEDDockerTerminal">Using an OED Docker terminal</h3><div class="alert-box warning "><p>Running a terminal in the OED Docker containers differs from running in a standard terminal on ones machine, including opening a terminal from the VSC “terminal” menu. The reason is that the OED Docker terminal has the full OED environment. If one runs outside the OED Docker container terminals then the result may be unpredictable.</div><div class="alert-box info "><p>One can only attach a terminal to the OED Docker container if OED is running</div><p>The developer web pages assume one assesses a terminal inside of the Docker container. There are two main ways of doing this:<ul><li>If one is using VSC with the Docker extension (<img alt="VSC container msg" src="../images/dockerIcon.png">) then one can use it (see <a href="#docker">here</a> for info). Right click on the desired OED Docker container and select "Attach Shell" as shown next: <br><img alt="VSC Docker shell" src="../images/VSCDockerShell.png"> <br>One normally gets a prompt similar to <code>root@20124d33c2c7:/usr/src/app#</code>.<li>Using the Docker Desktop, go to containers, and use the drop down menu (three vertical dots) on the OED container to "Open in terminal" as shown next: <br><img alt="Docker Desktop shell" src="../images/DockerDesktopShell.png"> <br>One normally gets a prompt similar to <code>#</code>.</ul><div class="alert-box info "><p>The terminal in the OED Docker container runs as root. This allows the developer to make any desired change but also allows one to change/damage the OED information. Care should be used.</div><h3 id="DockerInfo">Getting OED Docker information</h3><ul><div class="alert-box info "><p>The following assumes one has the VSC Docker extension as <a href="#VSCExtentions">described above</a>. Similar information is available via the Docker Desktop.</div><li>It should show information on all the Docker images/containers one has. The containers that are currently running have a green triangle next to them. One can get the following choices by right clicking on a container:<ul><li>View Logs: The web container will not show much since the OED output is in the terminal used to start oed (or in nohup.out if using the OED VSC container). The database one will show messages from PostgreSQL. These open a new terminal that one can remove with the trash can icon.<li>Attach Shell: This puts one in a shell within the container that is using the OED environment (see <a href="#OEDDockerTerminal"> for more info.</a>).<ul><li>In the shell inside the database container one can do: <code>psql -U oed</code> to open the Postgres command line. This will allow one to look at the live OED database. One can also see the OED startup files for the database with <code>ls docker-entrypoint-initdb.d.</code><li>In the shell inside the web container, one can look at the environment variables or do other Linux operation. One can run any script in package.json, e.g., <code>npm run check</code>. One can see all the running processes with <code>ps -aux</code>.</ul><li>Inspect: Opens a JSON file that gives detailed information on the container that can be useful for debugging issues.<li>Open in Browser: For the web container, this will go to localhost:3000.<li>Stop, Remove: Stop or remove the container where stop is useful if something does not shut down properly.</ul></ul><h3 id="testData">OED test data</h3><p>When one installs OED, it does not have any data. An actual site would connect up meters to gather data. For a developer, OED has standard test data one can use. The <a href="../testData/">OED test data</a> page has information and directions for doing this. OED suggests one loads up the data now so one can try any features desired in OED. Note that an advantage of this test data is that it is the same for all developers so people should be able to reproduce what one mentions if one has a question or issue.<h3 id="technologies">Technologies OED uses</h3><p>OED uses a number of technologies. One may want further information on these and some are provided on the <a href="../learningTechnologies/">OED technologies page</a>. OED welcomes input on other areas people would like to know about or other resources one finds valuable. Note that one can work on parts of OED without knowing many of the technologies in any depth. For example, one can work on database queries without knowing about the front-end. Thus, many developers begin in areas they know or want to learn first and focus on that needed information. Having said that, almost the entire code base is in JavaScript/TypeScript so a basic understanding of that is usually needed to get started.<h3 id="multiauthor">Multi-author work</h3><p>It is common for a team to work on OED together. If one is doing this and want to give another person acknowledgement on a commit, then see <a href="https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors" rel="noopener noreferrer">GitHub info on multiple authors</a>.<h3 id="issues">Issues</h3><p id="sendConsole">If anyone has any issues please copy the current output from the terminal used to start OED (or nohup.out if using the VSC OED container) and forward it along with any other information to the OED project by <a href="https://openenergydashboard.org/contact/">contacting us</a>. We will look it over and get back to you. We try to do that quickly. It is also fine to send a message to the developer Discord channel to seek answers.<h3 id="VSCInstall">Install and run OED in a VSC container</h3><div class="alert-box warning "><p>This method has the advantages that one does not have to open a terminal or get all the recommended VSC extensions. However, developers have been having issues/failures with this method of running OED. Furthermore, this method generally starts up slower, uses more CPU/memory on ones computer and is harder to see OED developer messages. Given this, it should only be used when desired/necessary and the method of running in a terminal (<a href="#terminalInstall">described here</a>) is normally recommended. See the section on <a href="#OEDVSCIssues">OED VSC issues</a> for more information.</div><div class="alert-box warning "><p>If the last install of OED was from <a href="#terminalInstall">the terminal</a> then it is critical that the two OED containers are remove. The steps are part of the information in the <a href="#OEDVSCIssues">OED VSC issues section</a>. Note the same steps must be followed if going from the OED VSC Docker container to using a terminal install.</div><div class="alert-box info "><p>This only works if one uses VSC as ones IDE. One needs to have the “Remote Development” VSC extension for this to work. Click on the Extensions manager icon on the far left of the VSC window (<img alt="VSC Extension icon" src="../images/VSCExtensions.png" />) to see if one has it. If not, search for “Remote Development” and install it. One will get several Extensions included with this one.</div><p>The OED repository contains the <code>.devcontainer</code> folder that allows VSC to automatically launch and set up the needed Docker containers. Here are the directions:<p>This assumes one has opened the main OED directory in VSC as described above.<p>Typically, VSC will ask to reopen the folder in a container by showing this message: <img alt="VSC container msg" src="../images/VSCContainerMsg.png" style="width: 25vw; min-width: 200px;"><p>One can click the button "Reopen in Container". One will often see a popup in VSC that indicate one can click to see the log: <img alt="VSC container msg" src="../images/VSCDevLog.png" style="width: 25vw; min-width: 200px;"><p>The first time OED installs it can take a while where the time depends on the speed of ones machine and internet connection (to get the needed npm packages). One can see the output of the install and anything OED outputs to the console by looking at the file <code>nohup.out</code> that will be created in ones main OED directory. If one opens this in VSC it should update with new lines at the bottom as they are added. See <a href="../fullInstallOutput/">full install output</a> or <a href="../noNPMInstallOutput/">install without Postgres or npm install output</a> to see a typical install output and for information if something goes wrong.<div class="alert-box warning "><p>If one waits a while (depends on machine speed but normally not more than 5-10 minute) and doesn’t see the install output in <code>nohup.out</code> then something is likely wrong. Note if there is no <code>nohup.out</code> file then the install did not work. See below on possible issues and solutions. OED starts new output from an install with a line such as <code>web-1 | ***** Starting install of OED at Sat Aug 31 21:18:28 UTC 2024 *****</code>. Searching from the bottom of the file for <code>****</code> and going upward should find the latest install output.</div><div class="alert-box info "><p>If VSC does not automatically ask to open in a container, one can click the “Remote Container” icon (<img alt="VSC Remote Container icon" src="../images/VSCRemoteIcon.png" width="32" height="26" style="min-width:32px; display: inline" />) that is normally in the bottom, left of the VSC window and select “Reopen in Container” for the menu that appears.</div><p>Once OED is running one should be able to see the web and database Docker containers running via Docker (either the VSC extension or the desktop). See <a href="#DockerInfo">Docker information</a> for more info on doing this.<p>One can shut down the OED VSC container by clicking the green icon for the Remote Container and selecting "Close Remote Container".<p>All output from the OED server will show in the <code>nohup.out</code> file located in the main OED directory. The latest information is at the bottom.<h4 id="OEDVSCIssues">OED VSC issues</h4><p>As mentioned above, developers are experiencing issues using this system. These mostly revolve around the install failing. When this happens, it is often fixed by doing the following:<ol><li>Exiting the OED VSC Docker container by clicking the green icon for the Remote Container and selecting "Close Remote Container".<li>Normally the OED Docker containers will not be running but stop them using Docker <a href="#DockerInfo">as described above</a>.<li>Remove both OED Docker containers (web and database) but <strong>not the images</strong> <a href="#DockerInfo">as described above</a>.<li>Try restarting OED by reopening the OED VSC container as described above.</ol><div class="alert-box info "><p>If one rebuilds the VSC container too soon after a build failure then it may fail again. Normally the time taken for the steps above avoids this. However, if the rebuild is being done right away then it is best to wait a few seconds before attempting.</div><h3 id="help">Getting help</h3><p>If anyone wants help or have questions about running OED, then see the <a href="https://openenergydashboard.org/">website</a> or the documentation pages and contact information in the links on this page.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/images/DockerDesktopShell.png b/developer/images/DockerDesktopShell.png
new file mode 100644
index 00000000..9651f768
Binary files /dev/null and b/developer/images/DockerDesktopShell.png differ
diff --git a/developer/images/VSCConvertTabs.png b/developer/images/VSCConvertTabs.png
new file mode 100644
index 00000000..ef2cb995
Binary files /dev/null and b/developer/images/VSCConvertTabs.png differ
diff --git a/developer/images/VSCDockerShell.png b/developer/images/VSCDockerShell.png
new file mode 100644
index 00000000..bf77626c
Binary files /dev/null and b/developer/images/VSCDockerShell.png differ
diff --git a/developer/images/VSCIndentSettings.png b/developer/images/VSCIndentSettings.png
new file mode 100644
index 00000000..9d5d7b45
Binary files /dev/null and b/developer/images/VSCIndentSettings.png differ
diff --git a/developer/images/VSCIndentTabs.png b/developer/images/VSCIndentTabs.png
new file mode 100644
index 00000000..0bd27726
Binary files /dev/null and b/developer/images/VSCIndentTabs.png differ
diff --git a/developer/images/VSCSpacesTabs.png b/developer/images/VSCSpacesTabs.png
new file mode 100644
index 00000000..ffcf4991
Binary files /dev/null and b/developer/images/VSCSpacesTabs.png differ
diff --git a/developer/images/VSCWSL.png b/developer/images/VSCWSL.png
new file mode 100644
index 00000000..a1161e70
Binary files /dev/null and b/developer/images/VSCWSL.png differ
diff --git a/developer/images/cloneURL.png b/developer/images/cloneURL.png
new file mode 100644
index 00000000..5e98983b
Binary files /dev/null and b/developer/images/cloneURL.png differ
diff --git a/developer/images/forkButton.png b/developer/images/forkButton.png
new file mode 100644
index 00000000..55302e81
Binary files /dev/null and b/developer/images/forkButton.png differ
diff --git a/developer/images/startupMainPage.png b/developer/images/startupMainPage.png
index 6a2b5a4f..35eb74a4 100644
Binary files a/developer/images/startupMainPage.png and b/developer/images/startupMainPage.png differ
diff --git a/developer/images/ubuntu.png b/developer/images/ubuntu.png
new file mode 100644
index 00000000..ccee82d0
Binary files /dev/null and b/developer/images/ubuntu.png differ
diff --git a/developer/learningTechnologies/index.html b/developer/learningTechnologies/index.html
index 7af9a588..a311b8e2 100644
--- a/developer/learningTechnologies/index.html
+++ b/developer/learningTechnologies/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>OED Developer Documentation</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. As a new developer, it can be daunting to understand and learn all of the technologies used in OED. This page, which everyone is encouraged to update, contains some resources that can be useful in this pursuit. This is not meant to be an exhaustive list nor rate these sites but to provide ones that project members or others have found useful. As always, you can contact the project with questions or for help. The following graphic shows some of the main technologies in OED grouped by where they are used. The &quot;Others&quot; group are technologies that generally span multiple parts of OED and are seen depending on what you are doing. Developers often only need to know the technology in one area or even a subset of that area. This can make the task of learning the needed technologies much more manageable. You may also find the Technology Overview giving an overview of the front-end process to be useful. Git Pro Git is a comprehensive book with both introductory materials and advanced features that is available for free in electronic formats. GitHub has extensive help on the particular git platform that OED uses. JavaScript JavaScript is a very popular language for developing web applications. While it shares part of its name with Java, it is a different language. It is used in the back-end of OED. There are many sources of information on JavaScript with some listed here. Note some discuss how to customize web pages and other features that will not be used as heavily in this project. Mozilla has a JavaScript tutorials along with reference materials. codecademy has a Introduction to JavaScript course. Eloquent JavaScript is an online book that can also be downloaded. WIKIBOOKS is a book/tutorial. w3schools has a JavaScript tutorial. Khan Academy has a JavaScript tutorial but note the early sections on graphics are not as applicable. Learn JS has a JavaScript tutorial that includes online coding with unit testing. This GitHub repo has recommendations for how to learn various programming environments including JavaScript. This list has places to learn JavaScript given different backgrounds. TypeScript TypeScript is a language layered on top of JavaScript that adds typing and other features to make JavaScript more secure. It is used in the front-end of OED. There are many sources to learn TypeScript including one from the TypeScript organization. JavaScript Promises Promises is a system within JavaScript to help deal with the situation when some actions depend on others. In a nutshell, there are times you want to wait on one action to finish before another begins. This is used throughout the OED code base. Digital Ocean has a Understanding JavaScript Promises. There is another site with a JavaScript Promises introduction (and JavaScript too). React React is a JavaScript library for building user interfaces. It is used by many organizations and projects. It is used in the OED front-end. The react community has a React tutorial along with a Quick Start page. This GitHub repo has recommendations for how to learn various programming environments including React. Redux Redux is a JavaScript library to help handle state. OED uses it along with React. It is used in the OED front-end. The Redux community has a Redux tutorial along with reference materials. Postgres For several reasons, OED uses the PostgreSQL database. While much of database code is standard SQL, some is PostgreSQL specific to access specific features. The PostgreSQL website has extensive information and documentation. OED uses pg-promise to interface with PostgreSQL. Its website and many others have information on this system. As the name implies, it also uses promises. Plotly The graphics in OED are produced with Plotly using their JavaScript library. There are many other references for using Plotly. Chai and Mocha OED uses the Chai and Mocha testing frameworks to test the OED code base. Both sites have information on usage as well as many other sites. We generally only use a subset of the features that can be seen by looking at our test code. Other packages OED directly depends on dozens of npm JavaScript packages and indirectly on many more. Some ones that are used more extensively include node (for running the JavaScript), express (for web requests), moment (for date/time objects), lodash (utility functions), react-intl (internationalization) and webpack (bundle app). You will see these and others in the OED code base. It is often best to learn about them as needed."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/learningTechnologies/"><meta property="og:title" content="OED Developer Documentation"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. As a new developer, it can be daunting to understand and learn all of the technologies used in OED. This page, which everyone is encouraged to update, contains some resources that can be useful in this pursuit. This is not meant to be an exhaustive list nor rate these sites but to provide ones that project members or others have found useful. As always, you can contact the project with questions or for help. The following graphic shows some of the main technologies in OED grouped by where they are used. The &quot;Others&quot; group are technologies that generally span multiple parts of OED and are seen depending on what you are doing. Developers often only need to know the technology in one area or even a subset of that area. This can make the task of learning the needed technologies much more manageable. You may also find the Technology Overview giving an overview of the front-end process to be useful. Git Pro Git is a comprehensive book with both introductory materials and advanced features that is available for free in electronic formats. GitHub has extensive help on the particular git platform that OED uses. JavaScript JavaScript is a very popular language for developing web applications. While it shares part of its name with Java, it is a different language. It is used in the back-end of OED. There are many sources of information on JavaScript with some listed here. Note some discuss how to customize web pages and other features that will not be used as heavily in this project. Mozilla has a JavaScript tutorials along with reference materials. codecademy has a Introduction to JavaScript course. Eloquent JavaScript is an online book that can also be downloaded. WIKIBOOKS is a book/tutorial. w3schools has a JavaScript tutorial. Khan Academy has a JavaScript tutorial but note the early sections on graphics are not as applicable. Learn JS has a JavaScript tutorial that includes online coding with unit testing. This GitHub repo has recommendations for how to learn various programming environments including JavaScript. This list has places to learn JavaScript given different backgrounds. TypeScript TypeScript is a language layered on top of JavaScript that adds typing and other features to make JavaScript more secure. It is used in the front-end of OED. There are many sources to learn TypeScript including one from the TypeScript organization. JavaScript Promises Promises is a system within JavaScript to help deal with the situation when some actions depend on others. In a nutshell, there are times you want to wait on one action to finish before another begins. This is used throughout the OED code base. Digital Ocean has a Understanding JavaScript Promises. There is another site with a JavaScript Promises introduction (and JavaScript too). React React is a JavaScript library for building user interfaces. It is used by many organizations and projects. It is used in the OED front-end. The react community has a React tutorial along with a Quick Start page. This GitHub repo has recommendations for how to learn various programming environments including React. Redux Redux is a JavaScript library to help handle state. OED uses it along with React. It is used in the OED front-end. The Redux community has a Redux tutorial along with reference materials. Postgres For several reasons, OED uses the PostgreSQL database. While much of database code is standard SQL, some is PostgreSQL specific to access specific features. The PostgreSQL website has extensive information and documentation. OED uses pg-promise to interface with PostgreSQL. Its website and many others have information on this system. As the name implies, it also uses promises. Plotly The graphics in OED are produced with Plotly using their JavaScript library. There are many other references for using Plotly. Chai and Mocha OED uses the Chai and Mocha testing frameworks to test the OED code base. Both sites have information on usage as well as many other sites. We generally only use a subset of the features that can be seen by looking at our test code. Other packages OED directly depends on dozens of npm JavaScript packages and indirectly on many more. Some ones that are used more extensively include node (for running the JavaScript), express (for web requests), moment (for date/time objects), lodash (utility functions), react-intl (internationalization) and webpack (bundle app). You will see these and others in the OED code base. It is often best to learn about them as needed."><meta property="og:url" content="https://openenergydashboard.org/developer/learningTechnologies/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Learn OED Technology</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">Learning Technology<h1>Learn OED Technology</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>As a new developer, it can be daunting to understand and learn all of the technologies used in OED. This page, which everyone is encouraged to update, contains some resources that can be useful in this pursuit. This is not meant to be an exhaustive list nor rate these sites but to provide ones that project members or others have found useful. As always, you can contact the project with questions or for help.<p>The following graphic shows some of the main technologies in OED grouped by where they are used. The "Others" group are technologies that generally span multiple parts of OED and are seen depending on what you are doing. Developers often only need to know the technology in one area or even a subset of that area. This can make the task of learning the needed technologies much more manageable.<p><img alt="OED technologies" src="../images/OEDTechnology.jpg"><p>You may also find the <a href="../technologies/">Technology Overview</a> giving an overview of the front-end process to be useful.<h2>Git</h2><ul><li> <a href="https://git-scm.com/book/en/v2" rel="noopener noreferrer">Pro Git</a> is a comprehensive book with both introductory materials and advanced features that is available for free in electronic formats.<li> <a href="https://docs.github.com/en" rel="noopener noreferrer">GitHub</a> has extensive help on the particular git platform that OED uses.</ul><h2>JavaScript</h2><p>JavaScript is a very popular language for developing web applications. While it shares part of its name with Java, it is a different language. It is used in the back-end of OED. There are many sources of information on JavaScript with some listed here. Note some discuss how to customize web pages and other features that will not be used as heavily in this project.<ul><li>Mozilla has a <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript" rel="noopener noreferrer">JavaScript tutorials along with reference materials</a>.<li>codecademy has a <a href="https://www.codecademy.com/learn/introduction-to-javascript?composer_curriculum_redirect=javascript" rel="noopener noreferrer">Introduction to JavaScript</a> course.<li> <a href="http://eloquentjavascript.net/" rel="noopener noreferrer">Eloquent JavaScript</a> is an online book that can also be downloaded.<li> <a href="https://en.wikibooks.org/wiki/JavaScript/Introduction" rel="noopener noreferrer">WIKIBOOKS is a book/tutorial</a>.<li>w3schools has a <a href="https://www.w3schools.com/js/" rel="noopener noreferrer">JavaScript tutorial</a>.<li>Khan Academy has a <a href="https://www.khanacademy.org/computing/computer-programming/programming" rel="noopener noreferrer">JavaScript tutorial</a> but note the early sections on graphics are not as applicable.<li>Learn JS has a <a href="https://www.learn-js.org/" rel="noopener noreferrer">JavaScript tutorial</a> that includes online coding with unit testing.<li><a href="https://github.com/practical-tutorials/project-based-learning">This GitHub repo</a> has recommendations for how to learn various programming environments including JavaScript.<li><a href="https://www.liveabout.com/learn-javascript-online-2071405">This list</a> has places to learn JavaScript given different backgrounds.</ul><h2>TypeScript</h2><p>TypeScript is a language layered on top of JavaScript that adds typing and other features to make JavaScript more secure. It is used in the front-end of OED. There are many sources to learn TypeScript including one from the <a href="https://www.typescriptlang.org/docs/" rel="noopener noreferrer">TypeScript organization</a>.<h2>JavaScript Promises</h2><p>Promises is a system within JavaScript to help deal with the situation when some actions depend on others. In a nutshell, there are times you want to wait on one action to finish before another begins. This is used throughout the OED code base.<ul><li>Digital Ocean has a <a href="https://www.digitalocean.com/community/tutorials/understanding-javascript-promises" rel="noopener noreferrer">Understanding JavaScript Promises</a>.<li>There is another site with a <a href="https://javascript.info/async" rel="noopener noreferrer">JavaScript Promises</a> introduction (and JavaScript too).</ul><h2>React</h2><p>React is a JavaScript library for building user interfaces. It is used by many organizations and projects. It is used in the OED front-end.<ul><li>The react community has a <a href="https://react.dev/learn/tutorial-tic-tac-toe" rel="noopener noreferrer">React tutorial</a> along with a <a href="https://react.dev/learn" rel="noopener noreferrer">Quick Start</a> page.<li><a href="https://github.com/practical-tutorials/project-based-learning">This GitHub repo</a> has recommendations for how to learn various programming environments including React.</ul><h2>Redux</h2><p>Redux is a JavaScript library to help handle state. OED uses it along with React. It is used in the OED front-end.<ul><li>The Redux community has a <a href="https://redux.js.org/tutorials/index" rel="noopener noreferrer">Redux tutorial</a> along with reference materials.</ul><h2>Postgres</h2><p>For several reasons, OED uses the PostgreSQL database. While much of database code is standard SQL, some is PostgreSQL specific to access specific features.<ul><li>The PostgreSQL <a href="https://www.postgresql.org/" rel="noopener noreferrer">website</a> has extensive information and documentation.<li>OED uses <a href="https://github.com/vitaly-t/pg-promise" rel="noopener noreferrer">pg-promise</a> to interface with PostgreSQL. Its website and many others have information on this system. As the name implies, it also uses promises.</ul><h2>Plotly</h2><p>The graphics in OED are produced with Plotly using their <a href="https://plotly.com/javascript/" rel="noopener noreferrer">JavaScript library</a>. There are many other references for using Plotly.<h2>Chai and Mocha</h2><p>OED uses the <a href="https://www.chaijs.com/" rel="noopener noreferrer">Chai</a> and <a href="https://mochajs.org/" rel="noopener noreferrer">Mocha</a> testing frameworks to test the OED code base. Both sites have information on usage as well as many other sites. We generally only use a subset of the features that can be seen by looking at our test code.<h2>Other packages</h2><p>OED directly depends on dozens of <a href="https://www.npmjs.com/" rrel="noopener noreferrer">npm</a> JavaScript packages and indirectly on many more. Some ones that are used more extensively include node (for running the JavaScript), express (for web requests), moment (for date/time objects), lodash (utility functions), react-intl (internationalization) and webpack (bundle app). You will see these and others in the OED code base. It is often best to learn about them as needed.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>OED Developer Documentation</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. As a new developer, it can be daunting to understand and learn all of the technologies used in OED. This page, which everyone is encouraged to update, contains some resources that can be useful in this pursuit. This is not meant to be an exhaustive list nor rate these sites but to provide ones that project members or others have found useful. As always, you can contact the project with questions or for help. The following graphic shows some of the main technologies in OED grouped by where they are used. The &quot;Others&quot; group are technologies that generally span multiple parts of OED and are seen depending on what you are doing. Developers often only need to know the technology in one area or even a subset of that area. This can make the task of learning the needed technologies much more manageable. You may also find the Technology Overview giving an overview of the front-end process to be useful. Git Pro Git is a comprehensive book with both introductory materials and advanced features that is available for free in electronic formats. GitHub has extensive help on the particular git platform that OED uses. JavaScript JavaScript is a very popular language for developing web applications. While it shares part of its name with Java, it is a different language. It is used in the back-end of OED. There are many sources of information on JavaScript with some listed here. Note some discuss how to customize web pages and other features that will not be used as heavily in this project. Mozilla has a JavaScript tutorials along with reference materials. codecademy has a Introduction to JavaScript course. Eloquent JavaScript is an online book that can also be downloaded. WIKIBOOKS is a book/tutorial. w3schools has a JavaScript tutorial. Khan Academy has a JavaScript tutorial but note the early sections on graphics are not as applicable. Learn JS has a JavaScript tutorial that includes online coding with unit testing. This GitHub repo has recommendations for how to learn various programming environments including JavaScript. This list has places to learn JavaScript given different backgrounds. TypeScript TypeScript is a language layered on top of JavaScript that adds typing and other features to make JavaScript more secure. It is used in the front-end of OED. There are many sources to learn TypeScript including one from the TypeScript organization. JavaScript Promises Promises is a system within JavaScript to help deal with the situation when some actions depend on others. In a nutshell, there are times you want to wait on one action to finish before another begins. This is used throughout the OED code base. Digital Ocean has a Understanding JavaScript Promises. There is another site with a JavaScript Promises introduction (and JavaScript too). React React is a JavaScript library for building user interfaces. It is used by many organizations and projects. It is used in the OED front-end. The react community has a React tutorial along with a Quick Start page. This GitHub repo has recommendations for how to learn various programming environments including React. Redux Redux is a JavaScript library to help handle state. OED uses it along with React. It is used in the OED front-end. The Redux community has a Redux tutorial along with reference materials. Postgres For several reasons, OED uses the PostgreSQL database. While much of database code is standard SQL, some is PostgreSQL specific to access specific features. The PostgreSQL website has extensive information and documentation. OED uses pg-promise to interface with PostgreSQL. Its website and many others have information on this system. As the name implies, it also uses promises. Plotly The graphics in OED are produced with Plotly using their JavaScript library. There are many other references for using Plotly. Chai and Mocha OED uses the Chai and Mocha testing frameworks to test the OED code base. Both sites have information on usage as well as many other sites. We generally only use a subset of the features that can be seen by looking at our test code. Other packages OED directly depends on dozens of npm JavaScript packages and indirectly on many more. Some ones that are used more extensively include node (for running the JavaScript), express (for web requests), moment (for date/time objects), lodash (utility functions), react-intl (internationalization) and webpack (bundle app). You will see these and others in the OED code base. It is often best to learn about them as needed."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/learningTechnologies/"><meta property="og:title" content="OED Developer Documentation"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. As a new developer, it can be daunting to understand and learn all of the technologies used in OED. This page, which everyone is encouraged to update, contains some resources that can be useful in this pursuit. This is not meant to be an exhaustive list nor rate these sites but to provide ones that project members or others have found useful. As always, you can contact the project with questions or for help. The following graphic shows some of the main technologies in OED grouped by where they are used. The &quot;Others&quot; group are technologies that generally span multiple parts of OED and are seen depending on what you are doing. Developers often only need to know the technology in one area or even a subset of that area. This can make the task of learning the needed technologies much more manageable. You may also find the Technology Overview giving an overview of the front-end process to be useful. Git Pro Git is a comprehensive book with both introductory materials and advanced features that is available for free in electronic formats. GitHub has extensive help on the particular git platform that OED uses. JavaScript JavaScript is a very popular language for developing web applications. While it shares part of its name with Java, it is a different language. It is used in the back-end of OED. There are many sources of information on JavaScript with some listed here. Note some discuss how to customize web pages and other features that will not be used as heavily in this project. Mozilla has a JavaScript tutorials along with reference materials. codecademy has a Introduction to JavaScript course. Eloquent JavaScript is an online book that can also be downloaded. WIKIBOOKS is a book/tutorial. w3schools has a JavaScript tutorial. Khan Academy has a JavaScript tutorial but note the early sections on graphics are not as applicable. Learn JS has a JavaScript tutorial that includes online coding with unit testing. This GitHub repo has recommendations for how to learn various programming environments including JavaScript. This list has places to learn JavaScript given different backgrounds. TypeScript TypeScript is a language layered on top of JavaScript that adds typing and other features to make JavaScript more secure. It is used in the front-end of OED. There are many sources to learn TypeScript including one from the TypeScript organization. JavaScript Promises Promises is a system within JavaScript to help deal with the situation when some actions depend on others. In a nutshell, there are times you want to wait on one action to finish before another begins. This is used throughout the OED code base. Digital Ocean has a Understanding JavaScript Promises. There is another site with a JavaScript Promises introduction (and JavaScript too). React React is a JavaScript library for building user interfaces. It is used by many organizations and projects. It is used in the OED front-end. The react community has a React tutorial along with a Quick Start page. This GitHub repo has recommendations for how to learn various programming environments including React. Redux Redux is a JavaScript library to help handle state. OED uses it along with React. It is used in the OED front-end. The Redux community has a Redux tutorial along with reference materials. Postgres For several reasons, OED uses the PostgreSQL database. While much of database code is standard SQL, some is PostgreSQL specific to access specific features. The PostgreSQL website has extensive information and documentation. OED uses pg-promise to interface with PostgreSQL. Its website and many others have information on this system. As the name implies, it also uses promises. Plotly The graphics in OED are produced with Plotly using their JavaScript library. There are many other references for using Plotly. Chai and Mocha OED uses the Chai and Mocha testing frameworks to test the OED code base. Both sites have information on usage as well as many other sites. We generally only use a subset of the features that can be seen by looking at our test code. Other packages OED directly depends on dozens of npm JavaScript packages and indirectly on many more. Some ones that are used more extensively include node (for running the JavaScript), express (for web requests), moment (for date/time objects), lodash (utility functions), react-intl (internationalization) and webpack (bundle app). You will see these and others in the OED code base. It is often best to learn about them as needed."><meta property="og:url" content="https://openenergydashboard.org/developer/learningTechnologies/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Learn OED Technology</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">Learning Technology<h1>Learn OED Technology</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>As a new developer, it can be daunting to understand and learn all of the technologies used in OED. This page, which everyone is encouraged to update, contains some resources that can be useful in this pursuit. This is not meant to be an exhaustive list nor rate these sites but to provide ones that project members or others have found useful. As always, you can contact the project with questions or for help.<p>The following graphic shows some of the main technologies in OED grouped by where they are used. The "Others" group are technologies that generally span multiple parts of OED and are seen depending on what you are doing. Developers often only need to know the technology in one area or even a subset of that area. This can make the task of learning the needed technologies much more manageable.<p><img alt="OED technologies" src="../images/OEDTechnology.jpg"><p>You may also find the <a href="../technologies/">Technology Overview</a> giving an overview of the front-end process to be useful.<h2>Git</h2><ul><li> <a href="https://git-scm.com/book/en/v2" rel="noopener noreferrer">Pro Git</a> is a comprehensive book with both introductory materials and advanced features that is available for free in electronic formats.<li> <a href="https://docs.github.com/en" rel="noopener noreferrer">GitHub</a> has extensive help on the particular git platform that OED uses.</ul><h2>JavaScript</h2><p>JavaScript is a very popular language for developing web applications. While it shares part of its name with Java, it is a different language. It is used in the back-end of OED. There are many sources of information on JavaScript with some listed here. Note some discuss how to customize web pages and other features that will not be used as heavily in this project.<ul><li>Mozilla has a <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript" rel="noopener noreferrer">JavaScript tutorials along with reference materials</a>.<li>codecademy has a <a href="https://www.codecademy.com/learn/introduction-to-javascript?composer_curriculum_redirect=javascript" rel="noopener noreferrer">Introduction to JavaScript</a> course.<li> <a href="http://eloquentjavascript.net/" rel="noopener noreferrer">Eloquent JavaScript</a> is an online book that can also be downloaded.<li> <a href="https://en.wikibooks.org/wiki/JavaScript/Introduction" rel="noopener noreferrer">WIKIBOOKS is a book/tutorial</a>.<li>w3schools has a <a href="https://www.w3schools.com/js/" rel="noopener noreferrer">JavaScript tutorial</a>.<li>Khan Academy has a <a href="https://www.khanacademy.org/computing/computer-programming/programming" rel="noopener noreferrer">JavaScript tutorial</a> but note the early sections on graphics are not as applicable.<li>Learn JS has a <a href="https://www.learn-js.org/" rel="noopener noreferrer">JavaScript tutorial</a> that includes online coding with unit testing.<li><a href="https://github.com/practical-tutorials/project-based-learning">This GitHub repo</a> has recommendations for how to learn various programming environments including JavaScript.<li><a href="https://www.liveabout.com/learn-javascript-online-2071405">This list</a> has places to learn JavaScript given different backgrounds.</ul><h2>TypeScript</h2><p>TypeScript is a language layered on top of JavaScript that adds typing and other features to make JavaScript more secure. It is used in the front-end of OED. There are many sources to learn TypeScript including one from the <a href="https://www.typescriptlang.org/docs/" rel="noopener noreferrer">TypeScript organization</a>.<h2>JavaScript Promises</h2><p>Promises is a system within JavaScript to help deal with the situation when some actions depend on others. In a nutshell, there are times you want to wait on one action to finish before another begins. This is used throughout the OED code base.<ul><li>Digital Ocean has a <a href="https://www.digitalocean.com/community/tutorials/understanding-javascript-promises" rel="noopener noreferrer">Understanding JavaScript Promises</a>.<li>There is another site with a <a href="https://javascript.info/async" rel="noopener noreferrer">JavaScript Promises</a> introduction (and JavaScript too).</ul><h2>React</h2><p>React is a JavaScript library for building user interfaces. It is used by many organizations and projects. It is used in the OED front-end.<ul><li>The react community has a <a href="https://react.dev/learn/tutorial-tic-tac-toe" rel="noopener noreferrer">React tutorial</a> along with a <a href="https://react.dev/learn" rel="noopener noreferrer">Quick Start</a> page.<li><a href="https://github.com/practical-tutorials/project-based-learning">This GitHub repo</a> has recommendations for how to learn various programming environments including React.</ul><h2>Redux</h2><p>Redux is a JavaScript library to help handle state. OED uses it along with React. It is used in the OED front-end.<ul><li>The Redux community has a <a href="https://redux.js.org/tutorials/index" rel="noopener noreferrer">Redux tutorial</a> along with reference materials.</ul><h2>Postgres</h2><p>For several reasons, OED uses the PostgreSQL database. While much of database code is standard SQL, some is PostgreSQL specific to access specific features.<ul><li>The PostgreSQL <a href="https://www.postgresql.org/" rel="noopener noreferrer">website</a> has extensive information and documentation.<li>OED uses <a href="https://github.com/vitaly-t/pg-promise" rel="noopener noreferrer">pg-promise</a> to interface with PostgreSQL. Its website and many others have information on this system. As the name implies, it also uses promises.</ul><h2>Plotly</h2><p>The graphics in OED are produced with Plotly using their <a href="https://plotly.com/javascript/" rel="noopener noreferrer">JavaScript library</a>. There are many other references for using Plotly.<h2>Chai and Mocha</h2><p>OED uses the <a href="https://www.chaijs.com/" rel="noopener noreferrer">Chai</a> and <a href="https://mochajs.org/" rel="noopener noreferrer">Mocha</a> testing frameworks to test the OED code base. Both sites have information on usage as well as many other sites. We generally only use a subset of the features that can be seen by looking at our test code.<h2>Other packages</h2><p>OED directly depends on dozens of <a href="https://www.npmjs.com/" rrel="noopener noreferrer">npm</a> JavaScript packages and indirectly on many more. Some ones that are used more extensively include node (for running the JavaScript), express (for web requests), moment (for date/time objects), lodash (utility functions), react-intl (internationalization) and webpack (bundle app). You will see these and others in the OED code base. It is often best to learn about them as needed.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/noNPMInstallOutput/index.html b/developer/noNPMInstallOutput/index.html
index eeb4e4a8..c8b427c4 100644
--- a/developer/noNPMInstallOutput/index.html
+++ b/developer/noNPMInstallOutput/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>No npm/DB Install Output</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. If you have previously installed the PostgreSQL database and it can skip installing the node modules then it will be faster and skip a number of steps. Below is typical output for this process. Please note: This output was created on 20 October 2023. The exact output will vary with machine type and changes to OED. This output will be in the nohup.out file for a VSC install. You may also see the log messages from the last time PostgreSQL ran in the earlier parts of the output. These could be short or long lists. They might seem to indicate issues but are not related to this attempt to install OED. For unknown reasons, the OED install fails to run at times. Here are two known fixes: Close the VSC container by clicking on the green &quot;Dev Container&quot; in the VSC info bar and choose &quot;Close Remote Connection&quot;. Then go to the VSC Docker Extension, right click on the web/vsc container and choose &quot;Remove&quot;. Repeat to remove the database Docker Container. If you reopen the OED workspace in the VSC container it should now work. This will likely get OED to run but you will probably have the same problem next time. Open a terminal in the web/vsc Docker container by right clicking on the that container in the VSC Docker extension and choosing &quot;Attach Shell&quot;. In the terminal that opens, enter ./src/scripts/installOED.sh &gt;&gt; nohup.out 2&gt;&amp;1 &amp; and hit return. This should cause the OED install to happen where you will see output in the nohup.out file. You can close the remote connection, as usual, to stop OED. Output [+] Building 0.0s (0/0) docker:default [+] Running 2/0 ✔ Container oed-database-1 Created 0.0s ✔ Container oed-web-1 Created 0.0s Attaching to oed-database-1, oed-web-1 oed-database-1 | oed-database-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization oed-database-1 | oed-web-1 | oed-web-1 | oed-web-1 | ***** Starting install of OED at Fri Oct 20 17:20:04 UTC 2023 ***** oed-web-1 | oed-web-1 | oed-web-1 | skipping NPM install as requested or because node_modules seems up to date oed-web-1 | oed-database-1 | 2023-10-20 17:20:04.454 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database-1 | 2023-10-20 17:20:04.456 UTC [1] LOG: listening on IPv4 address &quot;0.0.0.0&quot;, port 5432 oed-database-1 | 2023-10-20 17:20:04.457 UTC [1] LOG: listening on IPv6 address &quot;::&quot;, port 5432 oed-database-1 | 2023-10-20 17:20:04.462 UTC [1] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database-1 | 2023-10-20 17:20:04.471 UTC [29] LOG: database system was shut down at 2023-10-19 18:43:13 UTC oed-database-1 | 2023-10-20 17:20:04.496 UTC [1] LOG: database system is ready to accept connections oed-web-1 | Attempting to create database... oed-web-1 | oed-web-1 | -----start of npm run createdb output----- oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 createdb oed-web-1 | &gt; node ./src/server/services/createDB.js oed-web-1 | oed-web-1 | -----end of npm run createdb output----- oed-web-1 | oed-web-1 | database creation had no errors so assume schema creation worked. oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 createUser oed-web-1 | &gt; node ./src/server/services/user/createUser.js test@example.com password oed-web-1 | oed-web-1 | [INFO@2023-10-20T17:20:19.545+00:00] User test@example.com existed so not created oed-web-1 | oed-web-1 | User creation had no errors so default user &#39;test@example.com&#39; with password &#39;password&#39; should exist oed-web-1 | Creating developer DB function oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 developerdb oed-web-1 | &gt; node -e &#39;require(&quot;./src/server/util/developer.js&quot;).createShiftReadingsFunction()&#39; oed-web-1 | oed-web-1 | OED install finished oed-web-1 | Starting OED in development mode oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 start:dev oed-web-1 | &gt; nodemon --legacy-watch --inspect=0.0.0.0 ./src/bin/www oed-web-1 | oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 webpack:dev oed-web-1 | &gt; webpack watch --color --progress --mode development oed-web-1 | oed-web-1 | [nodemon] 2.0.22 oed-web-1 | [nodemon] to restart at any time, enter `rs` oed-web-1 | [nodemon] watching path(s): src/server/**/* src/bin/**/* src/common/**/* oed-web-1 | [nodemon] watching extensions: js,mjs,json oed-web-1 | [nodemon] starting `node --inspect=0.0.0.0 ./src/bin/www` oed-web-1 | Debugger listening on ws://0.0.0.0:9229/4450d153-6314-4eb6-af17-5b8a00a43f7c oed-web-1 | For help, see: https://nodejs.org/en/docs/inspector oed-web-1 | [INFO@2023-10-20T17:20:30.828+00:00] Listening on port 3000 oed-web-1 | oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run webpack-cli oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory LodashModuleReplacementPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile ProgressPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile ExternalsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation WorkerPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation SplitChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ResolverCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProgressPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProvidePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ModuleInfoHeaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JsonModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AssetModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EntryPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RuntimePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DataUriPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FileUriPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CompatibilityPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation HarmonyModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AMDPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireJsStuffPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CommonJsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NodeStuffPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation APIPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ConstPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation UseStrictPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireIncludePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireEnsurePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SystemPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportMetaPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation URLPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedModuleIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedChunkIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefinePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation TemplatedPathPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/1 dependencies 0/0 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 65% building 1/1 entries 3747/3747 dependencies 1071/1071 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 65% building oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph ResolverCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph InferAsyncModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph FlagDependencyExportsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins WarnCaseSensitiveModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization SideEffectsFlagPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization EnsureChunkConditionsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization MergeDuplicateChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization SplitChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids NamedModuleIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids NamedChunkIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js restored cached SourceMap oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit SizeLimitsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% oed-web-1 | oed-web-1 | asset bundle.js 15 MiB [emitted] [big] (name: application) 1 related asset oed-web-1 | orphan modules 131 KiB [orphan] 67 modules oed-web-1 | runtime modules 2.82 KiB 9 modules oed-web-1 | modules by path ./node_modules/ 12.9 MiB 739 modules oed-web-1 | modules by path ./src/ 1.15 MiB 172 modules oed-web-1 | asset modules 4.4 KiB oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 181 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 165 bytes [built] [code generated] oed-web-1 | + 10 modules oed-web-1 | webpack 5.76.0 compiled successfully in 27406 ms oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web-1 | Postgres output If you right click on the database web container in VSC and select &quot;View Logs&quot;, it will open a terminal where you will see the messages from Postgres."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/noNPMInstallOutput/"><meta property="og:title" content="No npm/DB Install Output"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. If you have previously installed the PostgreSQL database and it can skip installing the node modules then it will be faster and skip a number of steps. Below is typical output for this process. Please note: This output was created on 20 October 2023. The exact output will vary with machine type and changes to OED. This output will be in the nohup.out file for a VSC install. You may also see the log messages from the last time PostgreSQL ran in the earlier parts of the output. These could be short or long lists. They might seem to indicate issues but are not related to this attempt to install OED. For unknown reasons, the OED install fails to run at times. Here are two known fixes: Close the VSC container by clicking on the green &quot;Dev Container&quot; in the VSC info bar and choose &quot;Close Remote Connection&quot;. Then go to the VSC Docker Extension, right click on the web/vsc container and choose &quot;Remove&quot;. Repeat to remove the database Docker Container. If you reopen the OED workspace in the VSC container it should now work. This will likely get OED to run but you will probably have the same problem next time. Open a terminal in the web/vsc Docker container by right clicking on the that container in the VSC Docker extension and choosing &quot;Attach Shell&quot;. In the terminal that opens, enter ./src/scripts/installOED.sh &gt;&gt; nohup.out 2&gt;&amp;1 &amp; and hit return. This should cause the OED install to happen where you will see output in the nohup.out file. You can close the remote connection, as usual, to stop OED. Output [+] Building 0.0s (0/0) docker:default [+] Running 2/0 ✔ Container oed-database-1 Created 0.0s ✔ Container oed-web-1 Created 0.0s Attaching to oed-database-1, oed-web-1 oed-database-1 | oed-database-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization oed-database-1 | oed-web-1 | oed-web-1 | oed-web-1 | ***** Starting install of OED at Fri Oct 20 17:20:04 UTC 2023 ***** oed-web-1 | oed-web-1 | oed-web-1 | skipping NPM install as requested or because node_modules seems up to date oed-web-1 | oed-database-1 | 2023-10-20 17:20:04.454 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database-1 | 2023-10-20 17:20:04.456 UTC [1] LOG: listening on IPv4 address &quot;0.0.0.0&quot;, port 5432 oed-database-1 | 2023-10-20 17:20:04.457 UTC [1] LOG: listening on IPv6 address &quot;::&quot;, port 5432 oed-database-1 | 2023-10-20 17:20:04.462 UTC [1] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database-1 | 2023-10-20 17:20:04.471 UTC [29] LOG: database system was shut down at 2023-10-19 18:43:13 UTC oed-database-1 | 2023-10-20 17:20:04.496 UTC [1] LOG: database system is ready to accept connections oed-web-1 | Attempting to create database... oed-web-1 | oed-web-1 | -----start of npm run createdb output----- oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 createdb oed-web-1 | &gt; node ./src/server/services/createDB.js oed-web-1 | oed-web-1 | -----end of npm run createdb output----- oed-web-1 | oed-web-1 | database creation had no errors so assume schema creation worked. oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 createUser oed-web-1 | &gt; node ./src/server/services/user/createUser.js test@example.com password oed-web-1 | oed-web-1 | [INFO@2023-10-20T17:20:19.545+00:00] User test@example.com existed so not created oed-web-1 | oed-web-1 | User creation had no errors so default user &#39;test@example.com&#39; with password &#39;password&#39; should exist oed-web-1 | Creating developer DB function oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 developerdb oed-web-1 | &gt; node -e &#39;require(&quot;./src/server/util/developer.js&quot;).createShiftReadingsFunction()&#39; oed-web-1 | oed-web-1 | OED install finished oed-web-1 | Starting OED in development mode oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 start:dev oed-web-1 | &gt; nodemon --legacy-watch --inspect=0.0.0.0 ./src/bin/www oed-web-1 | oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 webpack:dev oed-web-1 | &gt; webpack watch --color --progress --mode development oed-web-1 | oed-web-1 | [nodemon] 2.0.22 oed-web-1 | [nodemon] to restart at any time, enter `rs` oed-web-1 | [nodemon] watching path(s): src/server/**/* src/bin/**/* src/common/**/* oed-web-1 | [nodemon] watching extensions: js,mjs,json oed-web-1 | [nodemon] starting `node --inspect=0.0.0.0 ./src/bin/www` oed-web-1 | Debugger listening on ws://0.0.0.0:9229/4450d153-6314-4eb6-af17-5b8a00a43f7c oed-web-1 | For help, see: https://nodejs.org/en/docs/inspector oed-web-1 | [INFO@2023-10-20T17:20:30.828+00:00] Listening on port 3000 oed-web-1 | oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run webpack-cli oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory LodashModuleReplacementPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile ProgressPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile ExternalsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation WorkerPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation SplitChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ResolverCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProgressPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProvidePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ModuleInfoHeaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JsonModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AssetModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EntryPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RuntimePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DataUriPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FileUriPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CompatibilityPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation HarmonyModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AMDPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireJsStuffPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CommonJsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NodeStuffPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation APIPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ConstPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation UseStrictPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireIncludePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireEnsurePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SystemPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportMetaPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation URLPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedModuleIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedChunkIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefinePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation TemplatedPathPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/1 dependencies 0/0 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 65% building 1/1 entries 3747/3747 dependencies 1071/1071 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 65% building oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph ResolverCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph InferAsyncModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph FlagDependencyExportsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins WarnCaseSensitiveModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization SideEffectsFlagPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization EnsureChunkConditionsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization MergeDuplicateChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization SplitChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids NamedModuleIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids NamedChunkIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js restored cached SourceMap oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit SizeLimitsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% oed-web-1 | oed-web-1 | asset bundle.js 15 MiB [emitted] [big] (name: application) 1 related asset oed-web-1 | orphan modules 131 KiB [orphan] 67 modules oed-web-1 | runtime modules 2.82 KiB 9 modules oed-web-1 | modules by path ./node_modules/ 12.9 MiB 739 modules oed-web-1 | modules by path ./src/ 1.15 MiB 172 modules oed-web-1 | asset modules 4.4 KiB oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 181 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 165 bytes [built] [code generated] oed-web-1 | + 10 modules oed-web-1 | webpack 5.76.0 compiled successfully in 27406 ms oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web-1 | Postgres output If you right click on the database web container in VSC and select &quot;View Logs&quot;, it will open a terminal where you will see the messages from Postgres."><meta property="og:url" content="https://openenergydashboard.org/developer/noNPMInstallOutput/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">No npm/DB Install Output</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>No npm/DB Install Output</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>If you have previously installed the PostgreSQL database and it can skip installing the node modules then it will be faster and skip a number of steps. Below is typical output for this process. Please note:<ul><li>This output was created on 20 October 2023. The exact output will vary with machine type and changes to OED. This output will be in the nohup.out file for a VSC install.<li>You may also see the log messages from the last time PostgreSQL ran in the earlier parts of the output. These could be short or long lists. They might seem to indicate issues but are not related to this attempt to install OED.<li>For unknown reasons, the OED install fails to run at times. Here are two known fixes:<ul><li>Close the VSC container by clicking on the green "Dev Container" in the VSC info bar and choose "Close Remote Connection". Then go to the VSC Docker Extension, right click on the web/vsc container and choose "Remove". Repeat to remove the database Docker Container. If you reopen the OED workspace in the VSC container it should now work.<li>This will likely get OED to run but you will probably have the same problem next time. Open a terminal in the web/vsc Docker container by right clicking on the that container in the VSC Docker extension and choosing "Attach Shell". In the terminal that opens, enter <code>./src/scripts/installOED.sh >> nohup.out 2>&1 &</code> and hit return. This should cause the OED install to happen where you will see output in the nohup.out file. You can close the remote connection, as usual, to stop OED.</ul></ul><h3>Output</h3><pre>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>No npm/DB Install Output</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. If you have previously installed the PostgreSQL database and it can skip installing the node modules then it will be faster and skip a number of steps. Below is typical output for this process. Please note: This output was created on 20 October 2023. The exact output will vary with machine type and changes to OED. This output will be in the nohup.out file for a VSC install. You may also see the log messages from the last time PostgreSQL ran in the earlier parts of the output. These could be short or long lists. They might seem to indicate issues but are not related to this attempt to install OED. For unknown reasons, the OED install fails to run at times. Here are two known fixes: Close the VSC container by clicking on the green &quot;Dev Container&quot; in the VSC info bar and choose &quot;Close Remote Connection&quot;. Then go to the VSC Docker Extension, right click on the web/vsc container and choose &quot;Remove&quot;. Repeat to remove the database Docker Container. If you reopen the OED workspace in the VSC container it should now work. This will likely get OED to run but you will probably have the same problem next time. Open a terminal in the web/vsc Docker container by right clicking on the that container in the VSC Docker extension and choosing &quot;Attach Shell&quot;. In the terminal that opens, enter ./src/scripts/installOED.sh &gt;&gt; nohup.out 2&gt;&amp;1 &amp; and hit return. This should cause the OED install to happen where you will see output in the nohup.out file. You can close the remote connection, as usual, to stop OED. Output [+] Building 0.0s (0/0) docker:default [+] Running 2/0 ✔ Container oed-database-1 Created 0.0s ✔ Container oed-web-1 Created 0.0s Attaching to oed-database-1, oed-web-1 oed-database-1 | oed-database-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization oed-database-1 | oed-web-1 | oed-web-1 | oed-web-1 | ***** Starting install of OED at Fri Oct 20 17:20:04 UTC 2023 ***** oed-web-1 | oed-web-1 | oed-web-1 | skipping NPM install as requested or because node_modules seems up to date oed-web-1 | oed-database-1 | 2023-10-20 17:20:04.454 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database-1 | 2023-10-20 17:20:04.456 UTC [1] LOG: listening on IPv4 address &quot;0.0.0.0&quot;, port 5432 oed-database-1 | 2023-10-20 17:20:04.457 UTC [1] LOG: listening on IPv6 address &quot;::&quot;, port 5432 oed-database-1 | 2023-10-20 17:20:04.462 UTC [1] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database-1 | 2023-10-20 17:20:04.471 UTC [29] LOG: database system was shut down at 2023-10-19 18:43:13 UTC oed-database-1 | 2023-10-20 17:20:04.496 UTC [1] LOG: database system is ready to accept connections oed-web-1 | Attempting to create database... oed-web-1 | oed-web-1 | -----start of npm run createdb output----- oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 createdb oed-web-1 | &gt; node ./src/server/services/createDB.js oed-web-1 | oed-web-1 | -----end of npm run createdb output----- oed-web-1 | oed-web-1 | database creation had no errors so assume schema creation worked. oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 createUser oed-web-1 | &gt; node ./src/server/services/user/createUser.js test@example.com password oed-web-1 | oed-web-1 | [INFO@2023-10-20T17:20:19.545+00:00] User test@example.com existed so not created oed-web-1 | oed-web-1 | User creation had no errors so default user &#39;test@example.com&#39; with password &#39;password&#39; should exist oed-web-1 | Creating developer DB function oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 developerdb oed-web-1 | &gt; node -e &#39;require(&quot;./src/server/util/developer.js&quot;).createShiftReadingsFunction()&#39; oed-web-1 | oed-web-1 | OED install finished oed-web-1 | Starting OED in development mode oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 start:dev oed-web-1 | &gt; nodemon --legacy-watch --inspect=0.0.0.0 ./src/bin/www oed-web-1 | oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 webpack:dev oed-web-1 | &gt; webpack watch --color --progress --mode development oed-web-1 | oed-web-1 | [nodemon] 2.0.22 oed-web-1 | [nodemon] to restart at any time, enter `rs` oed-web-1 | [nodemon] watching path(s): src/server/**/* src/bin/**/* src/common/**/* oed-web-1 | [nodemon] watching extensions: js,mjs,json oed-web-1 | [nodemon] starting `node --inspect=0.0.0.0 ./src/bin/www` oed-web-1 | Debugger listening on ws://0.0.0.0:9229/4450d153-6314-4eb6-af17-5b8a00a43f7c oed-web-1 | For help, see: https://nodejs.org/en/docs/inspector oed-web-1 | [INFO@2023-10-20T17:20:30.828+00:00] Listening on port 3000 oed-web-1 | oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run webpack-cli oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory LodashModuleReplacementPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile ProgressPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile ExternalsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation WorkerPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation SplitChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ResolverCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProgressPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProvidePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ModuleInfoHeaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JsonModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AssetModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EntryPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RuntimePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DataUriPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FileUriPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CompatibilityPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation HarmonyModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AMDPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireJsStuffPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CommonJsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NodeStuffPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation APIPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ConstPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation UseStrictPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireIncludePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireEnsurePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SystemPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportMetaPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation URLPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedModuleIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedChunkIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefinePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation TemplatedPathPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/1 dependencies 0/0 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 65% building 1/1 entries 3747/3747 dependencies 1071/1071 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 65% building oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph ResolverCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph InferAsyncModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph FlagDependencyExportsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins WarnCaseSensitiveModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization SideEffectsFlagPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization EnsureChunkConditionsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization MergeDuplicateChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization SplitChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids NamedModuleIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids NamedChunkIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js restored cached SourceMap oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit SizeLimitsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% oed-web-1 | oed-web-1 | asset bundle.js 15 MiB [emitted] [big] (name: application) 1 related asset oed-web-1 | orphan modules 131 KiB [orphan] 67 modules oed-web-1 | runtime modules 2.82 KiB 9 modules oed-web-1 | modules by path ./node_modules/ 12.9 MiB 739 modules oed-web-1 | modules by path ./src/ 1.15 MiB 172 modules oed-web-1 | asset modules 4.4 KiB oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 181 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 165 bytes [built] [code generated] oed-web-1 | + 10 modules oed-web-1 | webpack 5.76.0 compiled successfully in 27406 ms oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web-1 | Postgres output If you right click on the database web container in VSC and select &quot;View Logs&quot;, it will open a terminal where you will see the messages from Postgres."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/noNPMInstallOutput/"><meta property="og:title" content="No npm/DB Install Output"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. If you have previously installed the PostgreSQL database and it can skip installing the node modules then it will be faster and skip a number of steps. Below is typical output for this process. Please note: This output was created on 20 October 2023. The exact output will vary with machine type and changes to OED. This output will be in the nohup.out file for a VSC install. You may also see the log messages from the last time PostgreSQL ran in the earlier parts of the output. These could be short or long lists. They might seem to indicate issues but are not related to this attempt to install OED. For unknown reasons, the OED install fails to run at times. Here are two known fixes: Close the VSC container by clicking on the green &quot;Dev Container&quot; in the VSC info bar and choose &quot;Close Remote Connection&quot;. Then go to the VSC Docker Extension, right click on the web/vsc container and choose &quot;Remove&quot;. Repeat to remove the database Docker Container. If you reopen the OED workspace in the VSC container it should now work. This will likely get OED to run but you will probably have the same problem next time. Open a terminal in the web/vsc Docker container by right clicking on the that container in the VSC Docker extension and choosing &quot;Attach Shell&quot;. In the terminal that opens, enter ./src/scripts/installOED.sh &gt;&gt; nohup.out 2&gt;&amp;1 &amp; and hit return. This should cause the OED install to happen where you will see output in the nohup.out file. You can close the remote connection, as usual, to stop OED. Output [+] Building 0.0s (0/0) docker:default [+] Running 2/0 ✔ Container oed-database-1 Created 0.0s ✔ Container oed-web-1 Created 0.0s Attaching to oed-database-1, oed-web-1 oed-database-1 | oed-database-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization oed-database-1 | oed-web-1 | oed-web-1 | oed-web-1 | ***** Starting install of OED at Fri Oct 20 17:20:04 UTC 2023 ***** oed-web-1 | oed-web-1 | oed-web-1 | skipping NPM install as requested or because node_modules seems up to date oed-web-1 | oed-database-1 | 2023-10-20 17:20:04.454 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit oed-database-1 | 2023-10-20 17:20:04.456 UTC [1] LOG: listening on IPv4 address &quot;0.0.0.0&quot;, port 5432 oed-database-1 | 2023-10-20 17:20:04.457 UTC [1] LOG: listening on IPv6 address &quot;::&quot;, port 5432 oed-database-1 | 2023-10-20 17:20:04.462 UTC [1] LOG: listening on Unix socket &quot;/var/run/postgresql/.s.PGSQL.5432&quot; oed-database-1 | 2023-10-20 17:20:04.471 UTC [29] LOG: database system was shut down at 2023-10-19 18:43:13 UTC oed-database-1 | 2023-10-20 17:20:04.496 UTC [1] LOG: database system is ready to accept connections oed-web-1 | Attempting to create database... oed-web-1 | oed-web-1 | -----start of npm run createdb output----- oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 createdb oed-web-1 | &gt; node ./src/server/services/createDB.js oed-web-1 | oed-web-1 | -----end of npm run createdb output----- oed-web-1 | oed-web-1 | database creation had no errors so assume schema creation worked. oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 createUser oed-web-1 | &gt; node ./src/server/services/user/createUser.js test@example.com password oed-web-1 | oed-web-1 | [INFO@2023-10-20T17:20:19.545+00:00] User test@example.com existed so not created oed-web-1 | oed-web-1 | User creation had no errors so default user &#39;test@example.com&#39; with password &#39;password&#39; should exist oed-web-1 | Creating developer DB function oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 developerdb oed-web-1 | &gt; node -e &#39;require(&quot;./src/server/util/developer.js&quot;).createShiftReadingsFunction()&#39; oed-web-1 | oed-web-1 | OED install finished oed-web-1 | Starting OED in development mode oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 start:dev oed-web-1 | &gt; nodemon --legacy-watch --inspect=0.0.0.0 ./src/bin/www oed-web-1 | oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 webpack:dev oed-web-1 | &gt; webpack watch --color --progress --mode development oed-web-1 | oed-web-1 | [nodemon] 2.0.22 oed-web-1 | [nodemon] to restart at any time, enter `rs` oed-web-1 | [nodemon] watching path(s): src/server/**/* src/bin/**/* src/common/**/* oed-web-1 | [nodemon] watching extensions: js,mjs,json oed-web-1 | [nodemon] starting `node --inspect=0.0.0.0 ./src/bin/www` oed-web-1 | Debugger listening on ws://0.0.0.0:9229/4450d153-6314-4eb6-af17-5b8a00a43f7c oed-web-1 | For help, see: https://nodejs.org/en/docs/inspector oed-web-1 | [INFO@2023-10-20T17:20:30.828+00:00] Listening on port 3000 oed-web-1 | oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run webpack-cli oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 3% setup watch run oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory LodashModuleReplacementPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 4% setup normal module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 5% setup context module factory oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile ProgressPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 6% setup before compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile ExternalsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 7% setup compile oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation WorkerPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation SplitChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation ResolverCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 8% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProgressPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ProvidePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ModuleInfoHeaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JsonModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AssetModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EntryPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RuntimePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DataUriPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FileUriPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CompatibilityPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation HarmonyModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AMDPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireJsStuffPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation CommonJsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation LoaderPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NodeStuffPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation APIPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ConstPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation UseStrictPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireIncludePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireEnsurePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RequireContextPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SystemPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation ImportMetaPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation URLPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedModuleIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation NamedChunkIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation DefinePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation TemplatedPathPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 9% setup compilation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 10% building 0/1 entries 1/1 dependencies 0/0 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 65% building 1/1 entries 3747/3747 dependencies 1071/1071 modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 65% building oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 69% building finish oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph ResolverCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph InferAsyncModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph FlagDependencyExportsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing finish module graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins WarnCaseSensitiveModulesPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 70% sealing plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization SideEffectsFlagPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 71% sealing after dependencies optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 72% sealing chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing after chunk graph oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 73% sealing optimizing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 74% sealing module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing after module optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization EnsureChunkConditionsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization MergeDuplicateChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization SplitChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization RemoveEmptyChunksPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 75% sealing chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 76% sealing after chunk optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 77% sealing after module and chunk tree optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 78% sealing after chunk modules optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 79% sealing module reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing before module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids NamedModuleIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 80% sealing module ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 81% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing module id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 82% sealing chunk reviving oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 83% sealing before chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids NamedChunkIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk ids oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 84% sealing chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 85% sealing after chunk id optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record modules oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks RecordIdsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 86% sealing record chunks oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing module hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 87% sealing code generation oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 88% sealing runtime requirements oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 89% sealing after hashing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 90% sealing record hash oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing module assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 91% sealing chunk assets processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin bundle.js restored cached SourceMap oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin resolve sources oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing SourceMapDevToolPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 92% sealing asset processing oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing after asset optimization oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 93% sealing recording oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 94% sealing after seal oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 95% emitting emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit SizeLimitsPlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 98% emitting after emit oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% done plugins oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% oed-web-1 | oed-web-1 | asset bundle.js 15 MiB [emitted] [big] (name: application) 1 related asset oed-web-1 | orphan modules 131 KiB [orphan] 67 modules oed-web-1 | runtime modules 2.82 KiB 9 modules oed-web-1 | modules by path ./node_modules/ 12.9 MiB 739 modules oed-web-1 | modules by path ./src/ 1.15 MiB 172 modules oed-web-1 | asset modules 4.4 KiB oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 181 bytes [built] [code generated] oed-web-1 | data:image/svg+xml,%3csvg xmlns=%27.. 165 bytes [built] [code generated] oed-web-1 | + 10 modules oed-web-1 | webpack 5.76.0 compiled successfully in 27406 ms oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache store build dependencies oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle IdleFileCachePlugin oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 99% cache begin idle oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web-1 | Postgres output If you right click on the database web container in VSC and select &quot;View Logs&quot;, it will open a terminal where you will see the messages from Postgres."><meta property="og:url" content="https://openenergydashboard.org/developer/noNPMInstallOutput/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">No npm/DB Install Output</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>No npm/DB Install Output</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>If you have previously installed the PostgreSQL database and it can skip installing the node modules then it will be faster and skip a number of steps. Below is typical output for this process. Please note:<ul><li>This output was created on 20 October 2023. The exact output will vary with machine type and changes to OED. This output will be in the nohup.out file for a VSC install.<li>You may also see the log messages from the last time PostgreSQL ran in the earlier parts of the output. These could be short or long lists. They might seem to indicate issues but are not related to this attempt to install OED.<li>For unknown reasons, the OED install fails to run at times. Here are two known fixes:<ul><li>Close the VSC container by clicking on the green "Dev Container" in the VSC info bar and choose "Close Remote Connection". Then go to the VSC Docker Extension, right click on the web/vsc container and choose "Remove". Repeat to remove the database Docker Container. If you reopen the OED workspace in the VSC container it should now work.<li>This will likely get OED to run but you will probably have the same problem next time. Open a terminal in the web/vsc Docker container by right clicking on the that container in the VSC Docker extension and choosing "Attach Shell". In the terminal that opens, enter <code>./src/scripts/installOED.sh >> nohup.out 2>&1 &</code> and hit return. This should cause the OED install to happen where you will see output in the nohup.out file. You can close the remote connection, as usual, to stop OED.</ul></ul><h3>Output</h3><pre>
 [+] Building 0.0s (0/0)                                                                                                                                                                                             docker:default
 [+] Running 2/0
  ✔ Container oed-database-1  Created                                                                                                                                                                                     0.0s 
diff --git a/developer/npm/index.html b/developer/npm/index.html
index 4b1d23c4..3320f97f 100644
--- a/developer/npm/index.html
+++ b/developer/npm/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>npm scripts</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED has many scripts to support its use for development and sometimes in production settings. These can be run by executing npm run [SCRIPT] in the web docker compose service (e.g. docker compose run --rm web npm run [SCRIPT] [args]) or by entering the OED web container as a developer. App actions: Note these are not standard ways for developers to run parts of OED but can be used at times or in scripts. start starts the NodeJS webserver. start:dev starts the NodeJS webserver with Nodemon, so it restarts automatically. webpack:dev runs Webpack in development mode and dynamically rebuilding the client-side application when files change. webpack:build runs Webpack once in production mode. webpack runs Webpack once in development mode. Validation and CI actions: check runs all the below non-test checks (that is, all static checks) check:header ensures that there are no source files without MPL headers. check:typescript ensures that there are no JavaScript source files in the TypeScript portion of the project. check:types runs the TypeScript compiler without emitting code (i.e. just checks for type errors). check:lint runs TSLint against the project to ensure style conformity. test runs the automated test suite on the server. testsome &amp;lt;path to desired test file where can have multiple times&amp;gt; runs the automated test on the provided test file(s). Administration: Note many of these are described in more detail on the installation page (this is for site setup and not for developers but the information may be useful to some developers). createdb creates the database schema in an uninitialized database. It will not update the schema for some parts of OED on major changes. migratedb should upgrade the database after upgrading the software to a new version. addMamacMeters adds meters from a CSV file. updateMamacMeters fetches new data from previously imported Mamac meters. updateEgaugeMeters fetches new data from previously setup eGauge meters. refreshReadingViews aggregates readings data in the database for daily graphing has the latest data. refreshDailyReadingViews same as refreshReadingViews but using newer names. refreshHourlyReadingViews aggregates readings data in the database for hourly graphing has the latest data. refreshAllReadingViews does both the refreshDailyReadingViews and refreshHourlyReadingViews. createUser creates a new user. If given no arguments, it is interactive; you can also pass the username and password as command line arguments. This is not normally used any more since the admin web page allows adding/modifying users except on initial site setup . editUser edits the password of an existing user. This is not normally used any more since the admin web page allows adding/modifying users except or reset a password. sendLogEmail sends an email with the latest errors/warnings to the specified email. developerdb creates DB functions for developers to shift meter data for compare testing. updateCikAndViews causes a running OED to redo the cik in the DB and to update the daily and hourly views due to this change. obvius:showConfigfiles shows the Obvius config files stored in the DB; usually for debugging. obvius:purgeConfigfiles deletes the Obvius config files stored in the DB; usually for debugging and is destructive. Test data Developers interested in how to create the test data and related script should consult the testing page."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/npm/"><meta property="og:title" content="npm scripts"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED has many scripts to support its use for development and sometimes in production settings. These can be run by executing npm run [SCRIPT] in the web docker compose service (e.g. docker compose run --rm web npm run [SCRIPT] [args]) or by entering the OED web container as a developer. App actions: Note these are not standard ways for developers to run parts of OED but can be used at times or in scripts. start starts the NodeJS webserver. start:dev starts the NodeJS webserver with Nodemon, so it restarts automatically. webpack:dev runs Webpack in development mode and dynamically rebuilding the client-side application when files change. webpack:build runs Webpack once in production mode. webpack runs Webpack once in development mode. Validation and CI actions: check runs all the below non-test checks (that is, all static checks) check:header ensures that there are no source files without MPL headers. check:typescript ensures that there are no JavaScript source files in the TypeScript portion of the project. check:types runs the TypeScript compiler without emitting code (i.e. just checks for type errors). check:lint runs TSLint against the project to ensure style conformity. test runs the automated test suite on the server. testsome &amp;lt;path to desired test file where can have multiple times&amp;gt; runs the automated test on the provided test file(s). Administration: Note many of these are described in more detail on the installation page (this is for site setup and not for developers but the information may be useful to some developers). createdb creates the database schema in an uninitialized database. It will not update the schema for some parts of OED on major changes. migratedb should upgrade the database after upgrading the software to a new version. addMamacMeters adds meters from a CSV file. updateMamacMeters fetches new data from previously imported Mamac meters. updateEgaugeMeters fetches new data from previously setup eGauge meters. refreshReadingViews aggregates readings data in the database for daily graphing has the latest data. refreshDailyReadingViews same as refreshReadingViews but using newer names. refreshHourlyReadingViews aggregates readings data in the database for hourly graphing has the latest data. refreshAllReadingViews does both the refreshDailyReadingViews and refreshHourlyReadingViews. createUser creates a new user. If given no arguments, it is interactive; you can also pass the username and password as command line arguments. This is not normally used any more since the admin web page allows adding/modifying users except on initial site setup . editUser edits the password of an existing user. This is not normally used any more since the admin web page allows adding/modifying users except or reset a password. sendLogEmail sends an email with the latest errors/warnings to the specified email. developerdb creates DB functions for developers to shift meter data for compare testing. updateCikAndViews causes a running OED to redo the cik in the DB and to update the daily and hourly views due to this change. obvius:showConfigfiles shows the Obvius config files stored in the DB; usually for debugging. obvius:purgeConfigfiles deletes the Obvius config files stored in the DB; usually for debugging and is destructive. Test data Developers interested in how to create the test data and related script should consult the testing page."><meta property="og:url" content="https://openenergydashboard.org/developer/npm/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">npm scripts</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>npm scripts</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>OED has many scripts to support its use for development and sometimes in production settings. These can be run by executing <code>npm run [SCRIPT]</code> in the <code>web</code> docker compose service (e.g. <code>docker compose run --rm web npm run [SCRIPT] [args]</code>) or by entering the OED web container as a developer.<h2>App actions:</h2><p>Note these are not standard ways for developers to run parts of OED but can be used at times or in scripts.<ul><li><code>start</code> starts the NodeJS webserver.<li><code>start:dev</code> starts the NodeJS webserver with Nodemon, so it restarts automatically.<li><code>webpack:dev</code> runs Webpack in development mode and dynamically rebuilding the client-side application when files change.<li><code>webpack:build</code> runs Webpack once in production mode.<li><code>webpack</code> runs Webpack once in development mode.</ul><h2>Validation and CI actions:</h2><ul><li><code>check</code> runs all the below non-test checks (that is, all static checks)<li><code>check:header</code> ensures that there are no source files without MPL headers.<li><code>check:typescript</code> ensures that there are no JavaScript source files in the TypeScript portion of the project.<li><code>check:types</code> runs the TypeScript compiler without emitting code (i.e. just checks for type errors).<li><code>check:lint</code> runs TSLint against the project to ensure style conformity.<li><code>test</code> runs the automated test suite on the server.<li><code>testsome &lt;path to desired test file where can have multiple times&gt;</code> runs the automated test on the provided test file(s).</ul><h2>Administration:</h2><p>Note many of these are described in more detail on the <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">installation page</a> (this is for site setup and not for developers but the information may be useful to some developers).<ul><li><code>createdb</code> creates the database schema in an uninitialized database. It will not update the schema for some parts of OED on major changes.<li><code>migratedb</code> should upgrade the database after upgrading the software to a new version.<li><code>addMamacMeters</code> adds meters from a CSV file.<li><code>updateMamacMeters</code> fetches new data from previously imported Mamac meters.<li><code>updateEgaugeMeters</code> fetches new data from previously setup eGauge meters.<li><code>refreshReadingViews</code> aggregates readings data in the database for daily graphing has the latest data.<li><code>refreshDailyReadingViews</code> same as refreshReadingViews but using newer names.<li><code>refreshHourlyReadingViews</code> aggregates readings data in the database for hourly graphing has the latest data.<li><code>refreshAllReadingViews</code> does both the refreshDailyReadingViews and refreshHourlyReadingViews.<li><code>createUser</code> creates a new user. If given no arguments, it is interactive; you can also pass the username and password as command line arguments. This is not normally used any more since the admin web page allows adding/modifying users except on initial site setup .<li><code>editUser</code> edits the password of an existing user. This is not normally used any more since the admin web page allows adding/modifying users except or reset a password.<li><code>sendLogEmail</code> sends an email with the latest errors/warnings to the specified email.<li><code>developerdb</code> creates DB functions for developers to shift meter data for compare testing.<li><code>updateCikAndViews</code> causes a running OED to redo the cik in the DB and to update the daily and hourly views due to this change.<li><code>obvius:showConfigfiles</code> shows the Obvius config files stored in the DB; usually for debugging.<li><code>obvius:purgeConfigfiles</code> deletes the Obvius config files stored in the DB; usually for debugging and is destructive.</ul><h2>Test data</h2><p>Developers interested in how to create the test data and related script should consult the <a href="../testData/">testing page</a>.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>npm scripts</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED has many scripts to support its use for development and sometimes in production settings. These can be run by executing npm run [SCRIPT] in the web docker compose service (e.g. docker compose run --rm web npm run [SCRIPT] [args]) or by entering the OED web container as a developer. App actions: Note these are not standard ways for developers to run parts of OED but can be used at times or in scripts. start starts the NodeJS webserver. start:dev starts the NodeJS webserver with Nodemon, so it restarts automatically. webpack:dev runs Webpack in development mode and dynamically rebuilding the client-side application when files change. webpack:build runs Webpack once in production mode. webpack runs Webpack once in development mode. Validation and CI actions: check runs all the below non-test checks (that is, all static checks) check:header ensures that there are no source files without MPL headers. check:typescript ensures that there are no JavaScript source files in the TypeScript portion of the project. check:types runs the TypeScript compiler without emitting code (i.e. just checks for type errors). check:lint runs TSLint against the project to ensure style conformity. test runs the automated test suite on the server. testsome &amp;lt;path to desired test file where can have multiple times&amp;gt; runs the automated test on the provided test file(s). Administration: Note many of these are described in more detail on the installation page (this is for site setup and not for developers but the information may be useful to some developers). createdb creates the database schema in an uninitialized database. It will not update the schema for some parts of OED on major changes. migratedb should upgrade the database after upgrading the software to a new version. addMamacMeters adds meters from a CSV file. updateMamacMeters fetches new data from previously imported Mamac meters. updateEgaugeMeters fetches new data from previously setup eGauge meters. refreshReadingViews aggregates readings data in the database for daily graphing has the latest data. refreshDailyReadingViews same as refreshReadingViews but using newer names. refreshHourlyReadingViews aggregates readings data in the database for hourly graphing has the latest data. refreshAllReadingViews does both the refreshDailyReadingViews and refreshHourlyReadingViews. createUser creates a new user. If given no arguments, it is interactive; you can also pass the username and password as command line arguments. This is not normally used any more since the admin web page allows adding/modifying users except on initial site setup . editUser edits the password of an existing user. This is not normally used any more since the admin web page allows adding/modifying users except or reset a password. sendLogEmail sends an email with the latest errors/warnings to the specified email. developerdb creates DB functions for developers to shift meter data for compare testing. updateCikAndViews causes a running OED to redo the cik in the DB and to update the daily and hourly views due to this change. obvius:showConfigfiles shows the Obvius config files stored in the DB; usually for debugging. obvius:purgeConfigfiles deletes the Obvius config files stored in the DB; usually for debugging and is destructive. Test data Developers interested in how to create the test data and related script should consult the testing page."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/npm/"><meta property="og:title" content="npm scripts"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED has many scripts to support its use for development and sometimes in production settings. These can be run by executing npm run [SCRIPT] in the web docker compose service (e.g. docker compose run --rm web npm run [SCRIPT] [args]) or by entering the OED web container as a developer. App actions: Note these are not standard ways for developers to run parts of OED but can be used at times or in scripts. start starts the NodeJS webserver. start:dev starts the NodeJS webserver with Nodemon, so it restarts automatically. webpack:dev runs Webpack in development mode and dynamically rebuilding the client-side application when files change. webpack:build runs Webpack once in production mode. webpack runs Webpack once in development mode. Validation and CI actions: check runs all the below non-test checks (that is, all static checks) check:header ensures that there are no source files without MPL headers. check:typescript ensures that there are no JavaScript source files in the TypeScript portion of the project. check:types runs the TypeScript compiler without emitting code (i.e. just checks for type errors). check:lint runs TSLint against the project to ensure style conformity. test runs the automated test suite on the server. testsome &amp;lt;path to desired test file where can have multiple times&amp;gt; runs the automated test on the provided test file(s). Administration: Note many of these are described in more detail on the installation page (this is for site setup and not for developers but the information may be useful to some developers). createdb creates the database schema in an uninitialized database. It will not update the schema for some parts of OED on major changes. migratedb should upgrade the database after upgrading the software to a new version. addMamacMeters adds meters from a CSV file. updateMamacMeters fetches new data from previously imported Mamac meters. updateEgaugeMeters fetches new data from previously setup eGauge meters. refreshReadingViews aggregates readings data in the database for daily graphing has the latest data. refreshDailyReadingViews same as refreshReadingViews but using newer names. refreshHourlyReadingViews aggregates readings data in the database for hourly graphing has the latest data. refreshAllReadingViews does both the refreshDailyReadingViews and refreshHourlyReadingViews. createUser creates a new user. If given no arguments, it is interactive; you can also pass the username and password as command line arguments. This is not normally used any more since the admin web page allows adding/modifying users except on initial site setup . editUser edits the password of an existing user. This is not normally used any more since the admin web page allows adding/modifying users except or reset a password. sendLogEmail sends an email with the latest errors/warnings to the specified email. developerdb creates DB functions for developers to shift meter data for compare testing. updateCikAndViews causes a running OED to redo the cik in the DB and to update the daily and hourly views due to this change. obvius:showConfigfiles shows the Obvius config files stored in the DB; usually for debugging. obvius:purgeConfigfiles deletes the Obvius config files stored in the DB; usually for debugging and is destructive. Test data Developers interested in how to create the test data and related script should consult the testing page."><meta property="og:url" content="https://openenergydashboard.org/developer/npm/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">npm scripts</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>npm scripts</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>OED has many scripts to support its use for development and sometimes in production settings. These can be run by executing <code>npm run [SCRIPT]</code> in the <code>web</code> docker compose service (e.g. <code>docker compose run --rm web npm run [SCRIPT] [args]</code>) or by entering the OED web container as a developer.<h2>App actions:</h2><p>Note these are not standard ways for developers to run parts of OED but can be used at times or in scripts.<ul><li><code>start</code> starts the NodeJS webserver.<li><code>start:dev</code> starts the NodeJS webserver with Nodemon, so it restarts automatically.<li><code>webpack:dev</code> runs Webpack in development mode and dynamically rebuilding the client-side application when files change.<li><code>webpack:build</code> runs Webpack once in production mode.<li><code>webpack</code> runs Webpack once in development mode.</ul><h2>Validation and CI actions:</h2><ul><li><code>check</code> runs all the below non-test checks (that is, all static checks)<li><code>check:header</code> ensures that there are no source files without MPL headers.<li><code>check:typescript</code> ensures that there are no JavaScript source files in the TypeScript portion of the project.<li><code>check:types</code> runs the TypeScript compiler without emitting code (i.e. just checks for type errors).<li><code>check:lint</code> runs TSLint against the project to ensure style conformity.<li><code>test</code> runs the automated test suite on the server.<li><code>testsome &lt;path to desired test file where can have multiple times&gt;</code> runs the automated test on the provided test file(s).</ul><h2>Administration:</h2><p>Note many of these are described in more detail on the <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">installation page</a> (this is for site setup and not for developers but the information may be useful to some developers).<ul><li><code>createdb</code> creates the database schema in an uninitialized database. It will not update the schema for some parts of OED on major changes.<li><code>migratedb</code> should upgrade the database after upgrading the software to a new version.<li><code>addMamacMeters</code> adds meters from a CSV file.<li><code>updateMamacMeters</code> fetches new data from previously imported Mamac meters.<li><code>updateEgaugeMeters</code> fetches new data from previously setup eGauge meters.<li><code>refreshReadingViews</code> aggregates readings data in the database for daily graphing has the latest data.<li><code>refreshDailyReadingViews</code> same as refreshReadingViews but using newer names.<li><code>refreshHourlyReadingViews</code> aggregates readings data in the database for hourly graphing has the latest data.<li><code>refreshAllReadingViews</code> does both the refreshDailyReadingViews and refreshHourlyReadingViews.<li><code>createUser</code> creates a new user. If given no arguments, it is interactive; you can also pass the username and password as command line arguments. This is not normally used any more since the admin web page allows adding/modifying users except on initial site setup .<li><code>editUser</code> edits the password of an existing user. This is not normally used any more since the admin web page allows adding/modifying users except or reset a password.<li><code>sendLogEmail</code> sends an email with the latest errors/warnings to the specified email.<li><code>developerdb</code> creates DB functions for developers to shift meter data for compare testing.<li><code>updateCikAndViews</code> causes a running OED to redo the cik in the DB and to update the daily and hourly views due to this change.<li><code>obvius:showConfigfiles</code> shows the Obvius config files stored in the DB; usually for debugging.<li><code>obvius:purgeConfigfiles</code> deletes the Obvius config files stored in the DB; usually for debugging and is destructive.</ul><h2>Test data</h2><p>Developers interested in how to create the test data and related script should consult the <a href="../testData/">testing page</a>.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/pr/index.html b/developer/pr/index.html
index 760ba048..5f3f9fb9 100644
--- a/developer/pr/index.html
+++ b/developer/pr/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>PRs</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. While developing your code, we suggest you do the following: Create a branch of development branch (the main OED branch that is the default when you clone OED) and give it a name that indicates the work you intend to do. One can do this after the work is complete if not done earlier. Reusing a branch can cause unexpected updates to a pull request. Write test cases for your code. We use Mocha/Chai for testing and a description of its location and use in OED is available. We need to have all code carefully tested to know it is working when created but also stays working as future changes are made to OED. Writing good test code takes real effort but it needs to be done. If not done then that should be stated as a limitation of any pull request. Make sure you run OED in a web browser and it works as expected. Please check any feature that might have been impacted by your work and do a quick general check of the system so you know it works. Consider if your changes impacted code or documentation that needs updating. For example, did your code change OED usage so the documentation pages needed updating? Did you add a script so the Code Organization web page needs update? Did you change database usage or a function used elsewhere in OED so other code update is needed? It is impossible to give a full list but checking this out helps the project. In some cases you can note the needed changes in your pull request to make sure they get done outside your work. Run our checks. Lint is a system that verifies that your code does not have certain syntax or running issues along with making sure it follows our expectations for code style. It also verifies that each file has the needed license at the top and that TypeScript is used where expected. You will likely find it easier if you run this check early to find any issues so you don&#39;t repeat them many times (those working in VSC should see some being tested as your are coding). The checks are run in a terminal in the web/vsc Docker container: npm run check Run our code tests. These run all the test cases to verify the code is running correctly. It is similar to running lint where you use: npm run test This can take several minutes. A summary will be given at the bottom. If you see any errors then they should be checked out. Let us know if you need help. You will do the same command to check any new tests you add. See other info for faster running of single tests for debugging. Also note that the tests deliberately try to do invalid operations to test OED. This causes warning/errors in the OED output as well as in the PostgreSQL log that will be shown in the next install. Make sure you keep your fork up to date with development on the main OED GitHub. Other people may integrate new code into OED and your work needs to be in sync with that work. When your fork has code that is ready to add to the OED code base, create a pull request from your branch into development on the main OED GitHub repository (GitHub documentation). The pull request template should include the following: An area at the top to describe this PR. It states: &quot;Please include a summary of the change and which issue is touched on. Please also include relevant motivation and context.&quot; This is also the area to add recognition of others that worked on code. Use the @&amp;lt;GitHub name&amp;gt; where you put in the person&#39;s actual GitHub name (user id) without the angle brackets and GitHub will automatically link to their GitHub account. Note any issues this pull request addresses. Check to see if you are addressing any open issues. If so, please note in the pull request description. If your pull request completely fixes/addresses an open issue then put the words &quot;Fixes #XXX&quot;, where XXX is the issue number. If it only partly addresses an issue then use &quot;Partly Addresses #XXX&quot;. If it fixes an open issue then everyone will see a note in the pull request (after opened) indicating it will close this issue when merged and there is also a related note in the issue. There is a checkbox to indicate: &quot;Note merging this changes the database configuration.&quot; This indicates that the database needs to be updated for these changes to work correctly. Normally there will be migration files to update the database. However, many developers will choose to reinitialize the database to do a clean install to be sure everything works correctly. There is a checkbox to indicate: &quot;This change requires a documentation update&quot;. This indicates that some documentation (documentation pages, developer or website) needs modification based on the changes in the pull request. There is a checkbox to indicate: &quot;I have followed the [OED pull request](../pr/) ideas&quot; There is a checkbox to indicate: &quot;I have removed text in ( ) from the issue request&quot;. The template puts directions in ( ) and they should be removed once done to save space and make the pull request cleaner. There is a checkbox to indicate: &quot;You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section.&quot; An area to list any limitations of the PR: &quot;Describe any issues that remain or work that should still be done.&quot; If your work is not yet ready and you are sharing to get early feedback, please mark the pull request as a draft. When your pull request is submitted, automated GitHub Actions will run including static code checks and the OED test code that will do the checks and tests. If they pass then a green check mark will be put next to them and your pull request can be considered. If they fail, you should see why and fix the issue on your branch. When you push the change to your GitHub account (with the fork of OED), your pull request will automatically be updated and recheck. Note that the tests will not automatically run if this is your first pull request to OED. In that case it will wait until the project authorizes it to run. You can tell if there were any issues with the automated GitHub Actions by looking at the commit on the pull request. Toward the right side of the line with the commit there will either be a green check mark (everything is okay) or a red x (indicating issues). (It could be yellow of the checks have not finished which normally takes 1-4 minutes.) If you click on either, a popup has a link to the &quot;details&quot;. Normally the issue is with the OED tests (and not from the automated testing setup). To see these, open up the section labeled &quot;node tests&quot;. This will show all the checks (lint, typescript, etc.) and the automated unit tests. Normally there will be an error message (either at the end or in several places). This should indicate where the error occurred and help in tracking it down. Note that an error can cause the testing to stop so it is possible there are more errors that will show up once the earlier one is fixed. See above about running the tests on your machine and the developer details page has information on running a limited number of tests. Once your pull request is passing all automated checks, it needs to be reviewed by at least one OED team member with that privilege. The review might make suggestions and may request changes. Once that process is complete, a senior member of the team will either approve the pull request or make other comments (if not already reviewed by a senior member). Once approved, the pull request can be merged into development for inclusion into the OED code base. As always, if you have questions about this process or run into issues, you can contact the development team using the link at the bottom of this page."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/pr/"><meta property="og:title" content="PRs"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. While developing your code, we suggest you do the following: Create a branch of development branch (the main OED branch that is the default when you clone OED) and give it a name that indicates the work you intend to do. One can do this after the work is complete if not done earlier. Reusing a branch can cause unexpected updates to a pull request. Write test cases for your code. We use Mocha/Chai for testing and a description of its location and use in OED is available. We need to have all code carefully tested to know it is working when created but also stays working as future changes are made to OED. Writing good test code takes real effort but it needs to be done. If not done then that should be stated as a limitation of any pull request. Make sure you run OED in a web browser and it works as expected. Please check any feature that might have been impacted by your work and do a quick general check of the system so you know it works. Consider if your changes impacted code or documentation that needs updating. For example, did your code change OED usage so the documentation pages needed updating? Did you add a script so the Code Organization web page needs update? Did you change database usage or a function used elsewhere in OED so other code update is needed? It is impossible to give a full list but checking this out helps the project. In some cases you can note the needed changes in your pull request to make sure they get done outside your work. Run our checks. Lint is a system that verifies that your code does not have certain syntax or running issues along with making sure it follows our expectations for code style. It also verifies that each file has the needed license at the top and that TypeScript is used where expected. You will likely find it easier if you run this check early to find any issues so you don&#39;t repeat them many times (those working in VSC should see some being tested as your are coding). The checks are run in a terminal in the web/vsc Docker container: npm run check Run our code tests. These run all the test cases to verify the code is running correctly. It is similar to running lint where you use: npm run test This can take several minutes. A summary will be given at the bottom. If you see any errors then they should be checked out. Let us know if you need help. You will do the same command to check any new tests you add. See other info for faster running of single tests for debugging. Also note that the tests deliberately try to do invalid operations to test OED. This causes warning/errors in the OED output as well as in the PostgreSQL log that will be shown in the next install. Make sure you keep your fork up to date with development on the main OED GitHub. Other people may integrate new code into OED and your work needs to be in sync with that work. When your fork has code that is ready to add to the OED code base, create a pull request from your branch into development on the main OED GitHub repository (GitHub documentation). The pull request template should include the following: An area at the top to describe this PR. It states: &quot;Please include a summary of the change and which issue is touched on. Please also include relevant motivation and context.&quot; This is also the area to add recognition of others that worked on code. Use the @&amp;lt;GitHub name&amp;gt; where you put in the person&#39;s actual GitHub name (user id) without the angle brackets and GitHub will automatically link to their GitHub account. Note any issues this pull request addresses. Check to see if you are addressing any open issues. If so, please note in the pull request description. If your pull request completely fixes/addresses an open issue then put the words &quot;Fixes #XXX&quot;, where XXX is the issue number. If it only partly addresses an issue then use &quot;Partly Addresses #XXX&quot;. If it fixes an open issue then everyone will see a note in the pull request (after opened) indicating it will close this issue when merged and there is also a related note in the issue. There is a checkbox to indicate: &quot;Note merging this changes the database configuration.&quot; This indicates that the database needs to be updated for these changes to work correctly. Normally there will be migration files to update the database. However, many developers will choose to reinitialize the database to do a clean install to be sure everything works correctly. There is a checkbox to indicate: &quot;This change requires a documentation update&quot;. This indicates that some documentation (documentation pages, developer or website) needs modification based on the changes in the pull request. There is a checkbox to indicate: &quot;I have followed the [OED pull request](../pr/) ideas&quot; There is a checkbox to indicate: &quot;I have removed text in ( ) from the issue request&quot;. The template puts directions in ( ) and they should be removed once done to save space and make the pull request cleaner. There is a checkbox to indicate: &quot;You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section.&quot; An area to list any limitations of the PR: &quot;Describe any issues that remain or work that should still be done.&quot; If your work is not yet ready and you are sharing to get early feedback, please mark the pull request as a draft. When your pull request is submitted, automated GitHub Actions will run including static code checks and the OED test code that will do the checks and tests. If they pass then a green check mark will be put next to them and your pull request can be considered. If they fail, you should see why and fix the issue on your branch. When you push the change to your GitHub account (with the fork of OED), your pull request will automatically be updated and recheck. Note that the tests will not automatically run if this is your first pull request to OED. In that case it will wait until the project authorizes it to run. You can tell if there were any issues with the automated GitHub Actions by looking at the commit on the pull request. Toward the right side of the line with the commit there will either be a green check mark (everything is okay) or a red x (indicating issues). (It could be yellow of the checks have not finished which normally takes 1-4 minutes.) If you click on either, a popup has a link to the &quot;details&quot;. Normally the issue is with the OED tests (and not from the automated testing setup). To see these, open up the section labeled &quot;node tests&quot;. This will show all the checks (lint, typescript, etc.) and the automated unit tests. Normally there will be an error message (either at the end or in several places). This should indicate where the error occurred and help in tracking it down. Note that an error can cause the testing to stop so it is possible there are more errors that will show up once the earlier one is fixed. See above about running the tests on your machine and the developer details page has information on running a limited number of tests. Once your pull request is passing all automated checks, it needs to be reviewed by at least one OED team member with that privilege. The review might make suggestions and may request changes. Once that process is complete, a senior member of the team will either approve the pull request or make other comments (if not already reviewed by a senior member). Once approved, the pull request can be merged into development for inclusion into the OED code base. As always, if you have questions about this process or run into issues, you can contact the development team using the link at the bottom of this page."><meta property="og:url" content="https://openenergydashboard.org/developer/pr/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Creating Pull Requests</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Creating Pull Requests</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>While developing your code, we suggest you do the following:<ul><li>Create a branch of development branch (the main OED branch that is the default when you clone OED) and give it a name that indicates the work you intend to do. One can do this after the work is complete if not done earlier. Reusing a branch can cause unexpected updates to a pull request.<li>Write test cases for your code. We use Mocha/Chai for testing and a <a href="../testing/">description of its location and use in OED</a> is available. We need to have all code carefully tested to know it is working when created but also stays working as future changes are made to OED. Writing good test code takes real effort but it needs to be done. If not done then that should be stated as a limitation of any pull request.<li>Make sure you run OED in a web browser and it works as expected. Please check any feature that might have been impacted by your work and do a quick general check of the system so you know it works.<li>Consider if your changes impacted code or documentation that needs updating. For example, did your code change OED usage so the documentation pages needed updating? Did you add a script so the <a href="../codeOrganization/">Code Organization</a> web page needs update? Did you change database usage or a function used elsewhere in OED so other code update is needed? It is impossible to give a full list but checking this out helps the project. In some cases you can note the needed changes in your pull request to make sure they get done outside your work.<li>Run our checks. Lint is a system that verifies that your code does not have certain syntax or running issues along with making sure it follows our expectations for code style. It also verifies that each file has the needed license at the top and that TypeScript is used where expected. You will likely find it easier if you run this check early to find any issues so you don't repeat them many times (those working in VSC should see some being tested as your are coding). The checks are run in a terminal in the web/vsc Docker container:<br> <code>npm run check</code><br><li>Run our code tests. These run all the test cases to verify the code is running correctly. It is similar to running lint where you use: <br><code>npm run test</code><br> This can take several minutes. A summary will be given at the bottom. If you see any errors then they should be checked out. Let us know if you need help. You will do the same command to check any new tests you add. See <a href="../devDetails/#singleTest">other info</a> for faster running of single tests for debugging. Also note that the tests deliberately try to do invalid operations to test OED. This causes warning/errors in the OED output as well as in the PostgreSQL log that will be shown in the next install.<li>Make sure you keep your fork up to date with development on the main OED GitHub. Other people may integrate new code into OED and your work needs to be in sync with that work.</ul><p>When your fork has code that is ready to add to the OED code base, create a pull request from your branch into development on the main OED GitHub repository (<a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork" rel="noopener noreferrer">GitHub documentation</a>). The pull request template should include the following:<ul><li>An area at the top to describe this PR. It states: "Please include a summary of the change and which issue is touched on. Please also include relevant motivation and context." This is also the area to add recognition of others that worked on code. Use the @&lt;GitHub name&gt; where you put in the person's actual GitHub name (user id) without the angle brackets and GitHub will automatically link to their GitHub account.<li>Note any issues this pull request addresses. Check to see if you are addressing any open issues. If so, please note in the pull request description. If your pull request completely fixes/addresses an open issue then put the words "Fixes #XXX", where XXX is the issue number. If it only partly addresses an issue then use "Partly Addresses #XXX". If it fixes an open issue then everyone will see a note in the pull request (after opened) indicating it will close this issue when merged and there is also a related note in the issue.<li>There is a checkbox to indicate: "Note merging this changes the database configuration." This indicates that the database needs to be updated for these changes to work correctly. Normally there will be migration files to update the database. However, many developers will choose to reinitialize the database to do a clean install to be sure everything works correctly.<li>There is a checkbox to indicate: "This change requires a documentation update". This indicates that some documentation (documentation pages, developer or website) needs modification based on the changes in the pull request.<li>There is a checkbox to indicate: "I have followed the [OED pull request](../pr/) ideas"<li>There is a checkbox to indicate: "I have removed text in ( ) from the issue request". The template puts directions in ( ) and they should be removed once done to save space and make the pull request cleaner.<li>There is a checkbox to indicate: "You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section."<li>An area to list any limitations of the PR: "Describe any issues that remain or work that should still be done."<li>If your work is not yet ready and you are sharing to get early feedback, please mark the pull request as a draft.</ul><p>When your pull request is submitted, automated GitHub Actions will run including static code checks and the OED test code that will do the checks and tests. If they pass then a green check mark will be put next to them and your pull request can be considered. If they fail, you should see why and fix the issue on your branch. When you push the change to your GitHub account (with the fork of OED), your pull request will automatically be updated and recheck. Note that the tests will not automatically run if this is your first pull request to OED. In that case it will wait until the project authorizes it to run.<p>You can tell if there were any issues with the automated GitHub Actions by looking at the commit on the pull request. Toward the right side of the line with the commit there will either be a green check mark (everything is okay) or a red x (indicating issues). (It could be yellow of the checks have not finished which normally takes 1-4 minutes.) If you click on either, a popup has a link to the "details". Normally the issue is with the OED tests (and not from the automated testing setup). To see these, open up the section labeled "node tests". This will show all the checks (lint, typescript, etc.) and the automated unit tests. Normally there will be an error message (either at the end or in several places). This should indicate where the error occurred and help in tracking it down. Note that an error can cause the testing to stop so it is possible there are more errors that will show up once the earlier one is fixed. See above about running the tests on your machine and the developer details page has information on running a limited number of tests.<p>Once your pull request is passing all automated checks, it needs to be reviewed by at least one OED team member with that privilege. The review might make suggestions and may request changes. Once that process is complete, a senior member of the team will either approve the pull request or make other comments (if not already reviewed by a senior member). Once approved, the pull request can be merged into development for inclusion into the OED code base.<p>As always, if you have questions about this process or run into issues, you can contact the development team using the link at the bottom of this page.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>PRs</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. While developing your code, we suggest you do the following: Create a branch of development branch (the main OED branch that is the default when you clone OED) and give it a name that indicates the work you intend to do. One can do this after the work is complete if not done earlier. Reusing a branch can cause unexpected updates to a pull request. Write test cases for your code. We use Mocha/Chai for testing and a description of its location and use in OED is available. We need to have all code carefully tested to know it is working when created but also stays working as future changes are made to OED. Writing good test code takes real effort but it needs to be done. If not done then that should be stated as a limitation of any pull request. Make sure you run OED in a web browser and it works as expected. Please check any feature that might have been impacted by your work and do a quick general check of the system so you know it works. Consider if your changes impacted code or documentation that needs updating. For example, did your code change OED usage so the documentation pages needed updating? Did you add a script so the Code Organization web page needs update? Did you change database usage or a function used elsewhere in OED so other code update is needed? It is impossible to give a full list but checking this out helps the project. In some cases you can note the needed changes in your pull request to make sure they get done outside your work. Run our checks. Lint is a system that verifies that your code does not have certain syntax or running issues along with making sure it follows our expectations for code style. It also verifies that each file has the needed license at the top and that TypeScript is used where expected. You will likely find it easier if you run this check early to find any issues so you don&#39;t repeat them many times (those working in VSC should see some being tested as your are coding). The checks are run in a terminal in the web/vsc Docker container: npm run check Run our code tests. These run all the test cases to verify the code is running correctly. It is similar to running lint where you use: npm run test This can take several minutes. A summary will be given at the bottom. If you see any errors then they should be checked out. Let us know if you need help. You will do the same command to check any new tests you add. See other info for faster running of single tests for debugging. Also note that the tests deliberately try to do invalid operations to test OED. This causes warning/errors in the OED output as well as in the PostgreSQL log that will be shown in the next install. Make sure you keep your fork up to date with development on the main OED GitHub. Other people may integrate new code into OED and your work needs to be in sync with that work. When your fork has code that is ready to add to the OED code base, create a pull request from your branch into development on the main OED GitHub repository (GitHub documentation). The pull request template should include the following: An area at the top to describe this PR. It states: &quot;Please include a summary of the change and which issue is touched on. Please also include relevant motivation and context.&quot; This is also the area to add recognition of others that worked on code. Use the @&amp;lt;GitHub name&amp;gt; where you put in the person&#39;s actual GitHub name (user id) without the angle brackets and GitHub will automatically link to their GitHub account. Note any issues this pull request addresses. Check to see if you are addressing any open issues. If so, please note in the pull request description. If your pull request completely fixes/addresses an open issue then put the words &quot;Fixes #XXX&quot;, where XXX is the issue number. If it only partly addresses an issue then use &quot;Partly Addresses #XXX&quot;. If it fixes an open issue then everyone will see a note in the pull request (after opened) indicating it will close this issue when merged and there is also a related note in the issue. There is a checkbox to indicate: &quot;Note merging this changes the database configuration.&quot; This indicates that the database needs to be updated for these changes to work correctly. Normally there will be migration files to update the database. However, many developers will choose to reinitialize the database to do a clean install to be sure everything works correctly. There is a checkbox to indicate: &quot;This change requires a documentation update&quot;. This indicates that some documentation (documentation pages, developer or website) needs modification based on the changes in the pull request. There is a checkbox to indicate: &quot;I have followed the [OED pull request](../pr/) ideas&quot; There is a checkbox to indicate: &quot;I have removed text in ( ) from the issue request&quot;. The template puts directions in ( ) and they should be removed once done to save space and make the pull request cleaner. There is a checkbox to indicate: &quot;You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section.&quot; An area to list any limitations of the PR: &quot;Describe any issues that remain or work that should still be done.&quot; If your work is not yet ready and you are sharing to get early feedback, please mark the pull request as a draft. When your pull request is submitted, automated GitHub Actions will run including static code checks and the OED test code that will do the checks and tests. If they pass then a green check mark will be put next to them and your pull request can be considered. If they fail, you should see why and fix the issue on your branch. When you push the change to your GitHub account (with the fork of OED), your pull request will automatically be updated and recheck. Note that the tests will not automatically run if this is your first pull request to OED. In that case it will wait until the project authorizes it to run. You can tell if there were any issues with the automated GitHub Actions by looking at the commit on the pull request. Toward the right side of the line with the commit there will either be a green check mark (everything is okay) or a red x (indicating issues). (It could be yellow of the checks have not finished which normally takes 1-4 minutes.) If you click on either, a popup has a link to the &quot;details&quot;. Normally the issue is with the OED tests (and not from the automated testing setup). To see these, open up the section labeled &quot;node tests&quot;. This will show all the checks (lint, typescript, etc.) and the automated unit tests. Normally there will be an error message (either at the end or in several places). This should indicate where the error occurred and help in tracking it down. Note that an error can cause the testing to stop so it is possible there are more errors that will show up once the earlier one is fixed. See above about running the tests on your machine and the developer details page has information on running a limited number of tests. Once your pull request is passing all automated checks, it needs to be reviewed by at least one OED team member with that privilege. The review might make suggestions and may request changes. Once that process is complete, a senior member of the team will either approve the pull request or make other comments (if not already reviewed by a senior member). Once approved, the pull request can be merged into development for inclusion into the OED code base. As always, if you have questions about this process or run into issues, you can contact the development team using the link at the bottom of this page."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/pr/"><meta property="og:title" content="PRs"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. While developing your code, we suggest you do the following: Create a branch of development branch (the main OED branch that is the default when you clone OED) and give it a name that indicates the work you intend to do. One can do this after the work is complete if not done earlier. Reusing a branch can cause unexpected updates to a pull request. Write test cases for your code. We use Mocha/Chai for testing and a description of its location and use in OED is available. We need to have all code carefully tested to know it is working when created but also stays working as future changes are made to OED. Writing good test code takes real effort but it needs to be done. If not done then that should be stated as a limitation of any pull request. Make sure you run OED in a web browser and it works as expected. Please check any feature that might have been impacted by your work and do a quick general check of the system so you know it works. Consider if your changes impacted code or documentation that needs updating. For example, did your code change OED usage so the documentation pages needed updating? Did you add a script so the Code Organization web page needs update? Did you change database usage or a function used elsewhere in OED so other code update is needed? It is impossible to give a full list but checking this out helps the project. In some cases you can note the needed changes in your pull request to make sure they get done outside your work. Run our checks. Lint is a system that verifies that your code does not have certain syntax or running issues along with making sure it follows our expectations for code style. It also verifies that each file has the needed license at the top and that TypeScript is used where expected. You will likely find it easier if you run this check early to find any issues so you don&#39;t repeat them many times (those working in VSC should see some being tested as your are coding). The checks are run in a terminal in the web/vsc Docker container: npm run check Run our code tests. These run all the test cases to verify the code is running correctly. It is similar to running lint where you use: npm run test This can take several minutes. A summary will be given at the bottom. If you see any errors then they should be checked out. Let us know if you need help. You will do the same command to check any new tests you add. See other info for faster running of single tests for debugging. Also note that the tests deliberately try to do invalid operations to test OED. This causes warning/errors in the OED output as well as in the PostgreSQL log that will be shown in the next install. Make sure you keep your fork up to date with development on the main OED GitHub. Other people may integrate new code into OED and your work needs to be in sync with that work. When your fork has code that is ready to add to the OED code base, create a pull request from your branch into development on the main OED GitHub repository (GitHub documentation). The pull request template should include the following: An area at the top to describe this PR. It states: &quot;Please include a summary of the change and which issue is touched on. Please also include relevant motivation and context.&quot; This is also the area to add recognition of others that worked on code. Use the @&amp;lt;GitHub name&amp;gt; where you put in the person&#39;s actual GitHub name (user id) without the angle brackets and GitHub will automatically link to their GitHub account. Note any issues this pull request addresses. Check to see if you are addressing any open issues. If so, please note in the pull request description. If your pull request completely fixes/addresses an open issue then put the words &quot;Fixes #XXX&quot;, where XXX is the issue number. If it only partly addresses an issue then use &quot;Partly Addresses #XXX&quot;. If it fixes an open issue then everyone will see a note in the pull request (after opened) indicating it will close this issue when merged and there is also a related note in the issue. There is a checkbox to indicate: &quot;Note merging this changes the database configuration.&quot; This indicates that the database needs to be updated for these changes to work correctly. Normally there will be migration files to update the database. However, many developers will choose to reinitialize the database to do a clean install to be sure everything works correctly. There is a checkbox to indicate: &quot;This change requires a documentation update&quot;. This indicates that some documentation (documentation pages, developer or website) needs modification based on the changes in the pull request. There is a checkbox to indicate: &quot;I have followed the [OED pull request](../pr/) ideas&quot; There is a checkbox to indicate: &quot;I have removed text in ( ) from the issue request&quot;. The template puts directions in ( ) and they should be removed once done to save space and make the pull request cleaner. There is a checkbox to indicate: &quot;You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section.&quot; An area to list any limitations of the PR: &quot;Describe any issues that remain or work that should still be done.&quot; If your work is not yet ready and you are sharing to get early feedback, please mark the pull request as a draft. When your pull request is submitted, automated GitHub Actions will run including static code checks and the OED test code that will do the checks and tests. If they pass then a green check mark will be put next to them and your pull request can be considered. If they fail, you should see why and fix the issue on your branch. When you push the change to your GitHub account (with the fork of OED), your pull request will automatically be updated and recheck. Note that the tests will not automatically run if this is your first pull request to OED. In that case it will wait until the project authorizes it to run. You can tell if there were any issues with the automated GitHub Actions by looking at the commit on the pull request. Toward the right side of the line with the commit there will either be a green check mark (everything is okay) or a red x (indicating issues). (It could be yellow of the checks have not finished which normally takes 1-4 minutes.) If you click on either, a popup has a link to the &quot;details&quot;. Normally the issue is with the OED tests (and not from the automated testing setup). To see these, open up the section labeled &quot;node tests&quot;. This will show all the checks (lint, typescript, etc.) and the automated unit tests. Normally there will be an error message (either at the end or in several places). This should indicate where the error occurred and help in tracking it down. Note that an error can cause the testing to stop so it is possible there are more errors that will show up once the earlier one is fixed. See above about running the tests on your machine and the developer details page has information on running a limited number of tests. Once your pull request is passing all automated checks, it needs to be reviewed by at least one OED team member with that privilege. The review might make suggestions and may request changes. Once that process is complete, a senior member of the team will either approve the pull request or make other comments (if not already reviewed by a senior member). Once approved, the pull request can be merged into development for inclusion into the OED code base. As always, if you have questions about this process or run into issues, you can contact the development team using the link at the bottom of this page."><meta property="og:url" content="https://openenergydashboard.org/developer/pr/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Creating Pull Requests</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Creating Pull Requests</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>While developing your code, we suggest you do the following:<ul><li>Create a branch of development branch (the main OED branch that is the default when you clone OED) and give it a name that indicates the work you intend to do. One can do this after the work is complete if not done earlier. Reusing a branch can cause unexpected updates to a pull request.<li>Write test cases for your code. We use Mocha/Chai for testing and a <a href="../testing/">description of its location and use in OED</a> is available. We need to have all code carefully tested to know it is working when created but also stays working as future changes are made to OED. Writing good test code takes real effort but it needs to be done. If not done then that should be stated as a limitation of any pull request.<li>Make sure you run OED in a web browser and it works as expected. Please check any feature that might have been impacted by your work and do a quick general check of the system so you know it works.<li>Consider if your changes impacted code or documentation that needs updating. For example, did your code change OED usage so the documentation pages needed updating? Did you add a script so the <a href="../codeOrganization/">Code Organization</a> web page needs update? Did you change database usage or a function used elsewhere in OED so other code update is needed? It is impossible to give a full list but checking this out helps the project. In some cases you can note the needed changes in your pull request to make sure they get done outside your work.<li>Run our checks. Lint is a system that verifies that your code does not have certain syntax or running issues along with making sure it follows our expectations for code style. It also verifies that each file has the needed license at the top and that TypeScript is used where expected. You will likely find it easier if you run this check early to find any issues so you don't repeat them many times (those working in VSC should see some being tested as your are coding). The checks are run in a terminal in the web/vsc Docker container:<br> <code>npm run check</code><br><li>Run our code tests. These run all the test cases to verify the code is running correctly. It is similar to running lint where you use: <br><code>npm run test</code><br> This can take several minutes. A summary will be given at the bottom. If you see any errors then they should be checked out. Let us know if you need help. You will do the same command to check any new tests you add. See <a href="../devDetails/#singleTest">other info</a> for faster running of single tests for debugging. Also note that the tests deliberately try to do invalid operations to test OED. This causes warning/errors in the OED output as well as in the PostgreSQL log that will be shown in the next install.<li>Make sure you keep your fork up to date with development on the main OED GitHub. Other people may integrate new code into OED and your work needs to be in sync with that work.</ul><p>When your fork has code that is ready to add to the OED code base, create a pull request from your branch into development on the main OED GitHub repository (<a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork" rel="noopener noreferrer">GitHub documentation</a>). The pull request template should include the following:<ul><li>An area at the top to describe this PR. It states: "Please include a summary of the change and which issue is touched on. Please also include relevant motivation and context." This is also the area to add recognition of others that worked on code. Use the @&lt;GitHub name&gt; where you put in the person's actual GitHub name (user id) without the angle brackets and GitHub will automatically link to their GitHub account.<li>Note any issues this pull request addresses. Check to see if you are addressing any open issues. If so, please note in the pull request description. If your pull request completely fixes/addresses an open issue then put the words "Fixes #XXX", where XXX is the issue number. If it only partly addresses an issue then use "Partly Addresses #XXX". If it fixes an open issue then everyone will see a note in the pull request (after opened) indicating it will close this issue when merged and there is also a related note in the issue.<li>There is a checkbox to indicate: "Note merging this changes the database configuration." This indicates that the database needs to be updated for these changes to work correctly. Normally there will be migration files to update the database. However, many developers will choose to reinitialize the database to do a clean install to be sure everything works correctly.<li>There is a checkbox to indicate: "This change requires a documentation update". This indicates that some documentation (documentation pages, developer or website) needs modification based on the changes in the pull request.<li>There is a checkbox to indicate: "I have followed the [OED pull request](../pr/) ideas"<li>There is a checkbox to indicate: "I have removed text in ( ) from the issue request". The template puts directions in ( ) and they should be removed once done to save space and make the pull request cleaner.<li>There is a checkbox to indicate: "You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section."<li>An area to list any limitations of the PR: "Describe any issues that remain or work that should still be done."<li>If your work is not yet ready and you are sharing to get early feedback, please mark the pull request as a draft.</ul><p>When your pull request is submitted, automated GitHub Actions will run including static code checks and the OED test code that will do the checks and tests. If they pass then a green check mark will be put next to them and your pull request can be considered. If they fail, you should see why and fix the issue on your branch. When you push the change to your GitHub account (with the fork of OED), your pull request will automatically be updated and recheck. Note that the tests will not automatically run if this is your first pull request to OED. In that case it will wait until the project authorizes it to run.<p>You can tell if there were any issues with the automated GitHub Actions by looking at the commit on the pull request. Toward the right side of the line with the commit there will either be a green check mark (everything is okay) or a red x (indicating issues). (It could be yellow of the checks have not finished which normally takes 1-4 minutes.) If you click on either, a popup has a link to the "details". Normally the issue is with the OED tests (and not from the automated testing setup). To see these, open up the section labeled "node tests". This will show all the checks (lint, typescript, etc.) and the automated unit tests. Normally there will be an error message (either at the end or in several places). This should indicate where the error occurred and help in tracking it down. Note that an error can cause the testing to stop so it is possible there are more errors that will show up once the earlier one is fixed. See above about running the tests on your machine and the developer details page has information on running a limited number of tests.<p>Once your pull request is passing all automated checks, it needs to be reviewed by at least one OED team member with that privilege. The review might make suggestions and may request changes. Once that process is complete, a senior member of the team will either approve the pull request or make other comments (if not already reviewed by a senior member). Once approved, the pull request can be merged into development for inclusion into the OED code base.<p>As always, if you have questions about this process or run into issues, you can contact the development team using the link at the bottom of this page.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/release/index.html b/developer/release/index.html
index e102532c..c63161b5 100644
--- a/developer/release/index.html
+++ b/developer/release/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>OED Release</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. In preparing for an OED release, the following steps should be followed: Releases should correspond to a Milestone for the project. Announce to the Discord developer channel so everyone can look over the proposed release. Review the Milestone for this release to make sure all issues are complete or reassigned. See if there are any package or security issues that need to be addressed. Prepare the documentation pages for new release in the OpenEnergyDashboard.github.io repo. These steps assume you have forked this repo onto your own account and are working from that fork (probably in a local clone): Make sure all changes are done for the previous release and put in the OED repo for the main branch. Update your clone from the the main branch in OED repo. You can do this on your GitHub website or git fetch and merge of the main branch of the OED repo (generally referred to as upstream as where the fork came from) into your local main in Visual Studio. If you do it on the GitHub website then you will need to pull it down into your local clone. Create a new branch from the one you just updated for the new release. For example, if going from version 0.6.0 to 0.7.0 then branch main to create the branch v0.7.0. Commit these changes and the push them out to your fork (will probably require you to accept publishing the new branch if in Visual Studio and do it to your origin/forked copy). To allow testing of the new branch on your fork, go to the OpenEnergyDashboard.github.io repo on your GitHub account in a web browser. Click on the &quot;Settings&quot; tab and then click on the &quot;Pages&quot; choice on the left side of the page. Under &quot;Source&quot;, use the &quot;Branch&quot; dropdown menu to choose the new branch that you just pushed/published. This should cause you to see this branch when you go to https://&amp;lt;your GitHub ID&amp;gt;.github.io/OpenEnergyDashboard.github.io where you replace with your id. Duplicate the previous release&#39;s documentation directory into the new release directory. For example, copy help/v0.6.0 to help/v0.7.0. Unfortunately, you need to manually update the links to go from the previous release to the new release. In the new documentation directory (e.g., help/v0.7.0) edit each change listed below to update the version (e.g., v0.6.0 to v0.7.0) so do the following: Globally change the documentation links, e.g. help/v0.6.0 to help/v0.7.0. You can do this in the global search box in Visual Studio. Note it is important to prefix it with help/ so you don&#39;t edit other references to the version. edit _layouts/admin.html to add a line above &amp;lt;a href=&quot;../v0.6.0/{{ page.name }}&quot;&amp;gt;OED version 0.6.0 Help&amp;lt;/a&amp;gt; so it now has the line &amp;lt;a href=&quot;../v0.7.0/{{ page.name }}&quot;&amp;gt;OED version 0.7.0 Help&amp;lt;/a&amp;gt; Similarly, edit _layouts/help.html, to add a line above &amp;lt;a href=&quot;../v0.6.0/{{ page.name }}&quot;&amp;gt;OED version 0.6.0 Help&amp;lt;/a&amp;gt; so it now has the line &amp;lt;a href=&quot;../v0.7.0/{{ page.name }}&quot;&amp;gt;OED version 0.7.0 Help&amp;lt;/a&amp;gt; Edit help/v0.7.0/_version.html to update the version shown, e.g., 0.6.0 to 0.7.0. Update the help pages to reflect the new release. Be careful to do new screenshots if the look of OED has changed. Commit the changes. Push the changes to your fork. Check the changes work on your GitHub account (see above). When all is okay, create a pull request to put these changes into the OED GitHub pages. After it is merged, verify all still works okay. Note that if you find an issue with documentation included in previous releases then you will need to manually edit earlier versions to include this change, as appropriate. Do the final steps to prepare for the new version: Edit package.json to change the line &quot;&quot;version&quot;: &quot;0.6.0&quot;,&quot; to the version number you are about to release. Assuming you are going to version 0.7.0 (as in the next step for migrations) then it becomes: &quot;version&quot;: &quot;0.7.0&quot;,. You also need to edit package-lock.json to make a similar change as migrations do not update this file given changes in package.json. Assuming you have a migration of the database for this release, edit ``src/server/migrations/registerMigration.js`` to add a line that corresponds to the migration folder in ``src/server/migrations``. For example, if you are migrating from 0.6.0 to 0.7.0 and have the directory ``src/server/migrations/0.6.0-0.7.0`` then you add the line ``require(&#39;./0.6.0-0.7.0&#39;)`` remembering to put a comma at the end of line on the next-to-last (penultimate) line with a require.&quot; You should put the migration listings in order of their release number. Note if the last release did not have migrations then you need to use that as the previous version number so that the migration directories (and the next step) do not have gaps in the ranges or the migration will fail. Create the index.js file in the migration you are adding, e.g., ``src/server/migrations/0.6.0-0.7.0/sql/index.js``. You can look at one for a previous migration to see what to do. First, you need to edit the lines so the &quot;fromVersion&quot; and &quot;toVersion&quot; correspond to the version you are going from to the version you are going to. In the running example that would be &quot;fromVersion: &#39;0.6.0&#39;,&quot; and &quot;toVersion: &#39;0.7.0&#39;,&quot;. You now need to add a line inside &quot;up: async db =&gt; {&quot; for each migration file you have in this migration subdirectory. An example of a line would be:await db.none(sqlFile(&#39;../migrations/0.6.0-0.7.0/sql/meter/some_meter_change.sql&#39;)); where you need to make sure there is one line for each file that actually exists for this migration. Do extensive running and testing of OED in a web browser. When possible, test in all major web browsers. Verify the upgrade from a previous version works using the directions on the latest version of the Admin Upgrading help page. This normally means starting from the previous version on a server. If not already there see the Admin Installation help page on doing this where you will need to load in test data, add groups, etc. before upgrading to be sure the database migrates correctly. From the previous version you do the upgrade. After the upgrade make sure everything works correctly including the new features. Create the GitHub release following the steps in GitHub Managing releases in a repository. Note you can save as a draft for later release. Add info about release to an OED news items and release pages on the website. Celebrate."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/release/"><meta property="og:title" content="OED Release"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. In preparing for an OED release, the following steps should be followed: Releases should correspond to a Milestone for the project. Announce to the Discord developer channel so everyone can look over the proposed release. Review the Milestone for this release to make sure all issues are complete or reassigned. See if there are any package or security issues that need to be addressed. Prepare the documentation pages for new release in the OpenEnergyDashboard.github.io repo. These steps assume you have forked this repo onto your own account and are working from that fork (probably in a local clone): Make sure all changes are done for the previous release and put in the OED repo for the main branch. Update your clone from the the main branch in OED repo. You can do this on your GitHub website or git fetch and merge of the main branch of the OED repo (generally referred to as upstream as where the fork came from) into your local main in Visual Studio. If you do it on the GitHub website then you will need to pull it down into your local clone. Create a new branch from the one you just updated for the new release. For example, if going from version 0.6.0 to 0.7.0 then branch main to create the branch v0.7.0. Commit these changes and the push them out to your fork (will probably require you to accept publishing the new branch if in Visual Studio and do it to your origin/forked copy). To allow testing of the new branch on your fork, go to the OpenEnergyDashboard.github.io repo on your GitHub account in a web browser. Click on the &quot;Settings&quot; tab and then click on the &quot;Pages&quot; choice on the left side of the page. Under &quot;Source&quot;, use the &quot;Branch&quot; dropdown menu to choose the new branch that you just pushed/published. This should cause you to see this branch when you go to https://&amp;lt;your GitHub ID&amp;gt;.github.io/OpenEnergyDashboard.github.io where you replace with your id. Duplicate the previous release&#39;s documentation directory into the new release directory. For example, copy help/v0.6.0 to help/v0.7.0. Unfortunately, you need to manually update the links to go from the previous release to the new release. In the new documentation directory (e.g., help/v0.7.0) edit each change listed below to update the version (e.g., v0.6.0 to v0.7.0) so do the following: Globally change the documentation links, e.g. help/v0.6.0 to help/v0.7.0. You can do this in the global search box in Visual Studio. Note it is important to prefix it with help/ so you don&#39;t edit other references to the version. edit _layouts/admin.html to add a line above &amp;lt;a href=&quot;../v0.6.0/{{ page.name }}&quot;&amp;gt;OED version 0.6.0 Help&amp;lt;/a&amp;gt; so it now has the line &amp;lt;a href=&quot;../v0.7.0/{{ page.name }}&quot;&amp;gt;OED version 0.7.0 Help&amp;lt;/a&amp;gt; Similarly, edit _layouts/help.html, to add a line above &amp;lt;a href=&quot;../v0.6.0/{{ page.name }}&quot;&amp;gt;OED version 0.6.0 Help&amp;lt;/a&amp;gt; so it now has the line &amp;lt;a href=&quot;../v0.7.0/{{ page.name }}&quot;&amp;gt;OED version 0.7.0 Help&amp;lt;/a&amp;gt; Edit help/v0.7.0/_version.html to update the version shown, e.g., 0.6.0 to 0.7.0. Update the help pages to reflect the new release. Be careful to do new screenshots if the look of OED has changed. Commit the changes. Push the changes to your fork. Check the changes work on your GitHub account (see above). When all is okay, create a pull request to put these changes into the OED GitHub pages. After it is merged, verify all still works okay. Note that if you find an issue with documentation included in previous releases then you will need to manually edit earlier versions to include this change, as appropriate. Do the final steps to prepare for the new version: Edit package.json to change the line &quot;&quot;version&quot;: &quot;0.6.0&quot;,&quot; to the version number you are about to release. Assuming you are going to version 0.7.0 (as in the next step for migrations) then it becomes: &quot;version&quot;: &quot;0.7.0&quot;,. You also need to edit package-lock.json to make a similar change as migrations do not update this file given changes in package.json. Assuming you have a migration of the database for this release, edit ``src/server/migrations/registerMigration.js`` to add a line that corresponds to the migration folder in ``src/server/migrations``. For example, if you are migrating from 0.6.0 to 0.7.0 and have the directory ``src/server/migrations/0.6.0-0.7.0`` then you add the line ``require(&#39;./0.6.0-0.7.0&#39;)`` remembering to put a comma at the end of line on the next-to-last (penultimate) line with a require.&quot; You should put the migration listings in order of their release number. Note if the last release did not have migrations then you need to use that as the previous version number so that the migration directories (and the next step) do not have gaps in the ranges or the migration will fail. Create the index.js file in the migration you are adding, e.g., ``src/server/migrations/0.6.0-0.7.0/sql/index.js``. You can look at one for a previous migration to see what to do. First, you need to edit the lines so the &quot;fromVersion&quot; and &quot;toVersion&quot; correspond to the version you are going from to the version you are going to. In the running example that would be &quot;fromVersion: &#39;0.6.0&#39;,&quot; and &quot;toVersion: &#39;0.7.0&#39;,&quot;. You now need to add a line inside &quot;up: async db =&gt; {&quot; for each migration file you have in this migration subdirectory. An example of a line would be:await db.none(sqlFile(&#39;../migrations/0.6.0-0.7.0/sql/meter/some_meter_change.sql&#39;)); where you need to make sure there is one line for each file that actually exists for this migration. Do extensive running and testing of OED in a web browser. When possible, test in all major web browsers. Verify the upgrade from a previous version works using the directions on the latest version of the Admin Upgrading help page. This normally means starting from the previous version on a server. If not already there see the Admin Installation help page on doing this where you will need to load in test data, add groups, etc. before upgrading to be sure the database migrates correctly. From the previous version you do the upgrade. After the upgrade make sure everything works correctly including the new features. Create the GitHub release following the steps in GitHub Managing releases in a repository. Note you can save as a draft for later release. Add info about release to an OED news items and release pages on the website. Celebrate."><meta property="og:url" content="https://openenergydashboard.org/developer/release/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Releasing OED</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Releasing OED</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>In preparing for an OED release, the following steps should be followed:<ol><li>Releases should correspond to a Milestone for the project.<li>Announce to the Discord developer channel so everyone can look over the proposed release.<li>Review the Milestone for this release to make sure all issues are complete or reassigned.<li>See if there are any package or security issues that need to be addressed.<li>Prepare the documentation pages for new release in the OpenEnergyDashboard.github.io repo. These steps assume you have forked this repo onto your own account and are working from that fork (probably in a local clone):<ol><li>Make sure all changes are done for the previous release and put in the OED repo for the main branch.<li>Update your clone from the the main branch in OED repo. You can do this on your GitHub website or git fetch and merge of the main branch of the OED repo (generally referred to as upstream as where the fork came from) into your local main in Visual Studio. If you do it on the GitHub website then you will need to pull it down into your local clone.<li>Create a new branch from the one you just updated for the new release. For example, if going from version 0.6.0 to 0.7.0 then branch main to create the branch v0.7.0. Commit these changes and the push them out to your fork (will probably require you to accept publishing the new branch if in Visual Studio and do it to your origin/forked copy).<li>To allow testing of the new branch on your fork, go to the OpenEnergyDashboard.github.io repo on your GitHub account in a web browser. Click on the "Settings" tab and then click on the "Pages" choice on the left side of the page. Under "Source", use the "Branch" dropdown menu to choose the new branch that you just pushed/published. This should cause you to see this branch when you go to https://&lt;your GitHub ID&gt;.github.io/OpenEnergyDashboard.github.io where you replace <your GitHub ID> with your id.<li>Duplicate the previous release's documentation directory into the new release directory. For example, copy help/v0.6.0 to help/v0.7.0.<li>Unfortunately, you need to manually update the links to go from the previous release to the new release. In the new documentation directory (e.g., help/v0.7.0) edit each change listed below to update the version (e.g., v0.6.0 to v0.7.0) so do the following:<ul><li>Globally change the documentation links, e.g. help/v0.6.0 to help/v0.7.0. You can do this in the global search box in Visual Studio. Note it is important to prefix it with help/ so you don't edit other references to the version.<li>edit _layouts/admin.html to add a line above<br> &lt;a href="../v0.6.0/{{ page.name }}"&gt;OED version 0.6.0 Help&lt;/a&gt;<br> so it now has the line<br> &lt;a href="../v0.7.0/{{ page.name }}"&gt;OED version 0.7.0 Help&lt;/a&gt;<br><li>Similarly, edit _layouts/help.html, to add a line above<br> &lt;a href="../v0.6.0/{{ page.name }}"&gt;OED version 0.6.0 Help&lt;/a&gt;<br> so it now has the line<br> &lt;a href="../v0.7.0/{{ page.name }}"&gt;OED version 0.7.0 Help&lt;/a&gt;<br><li>Edit help/v0.7.0/_version.html to update the version shown, e.g., 0.6.0 to 0.7.0.</ul><li>Update the help pages to reflect the new release. Be careful to do new screenshots if the look of OED has changed.<li>Commit the changes.<li>Push the changes to your fork.<li>Check the changes work on your GitHub account (see above). When all is okay, create a pull request to put these changes into the OED GitHub pages. After it is merged, verify all still works okay.<li>Note that if you find an issue with documentation included in previous releases then you will need to manually edit earlier versions to include this change, as appropriate.</ol><li>Do the final steps to prepare for the new version:<ul><li>Edit package.json to change the line ""version": "0.6.0"," to the version number you are about to release. Assuming you are going to version 0.7.0 (as in the next step for migrations) then it becomes: "version": "0.7.0",. You also need to edit package-lock.json to make a similar change as migrations do not update this file given changes in package.json.<li>Assuming you have a migration of the database for this release, edit ``src/server/migrations/registerMigration.js`` to add a line that corresponds to the migration folder in ``src/server/migrations``. For example, if you are migrating from 0.6.0 to 0.7.0 and have the directory ``src/server/migrations/0.6.0-0.7.0`` then you add the line ``require('./0.6.0-0.7.0')`` remembering to put a comma at the end of line on the next-to-last (penultimate) line with a require." You should put the migration listings in order of their release number. Note if the last release did not have migrations then you need to use that as the previous version number so that the migration directories (and the next step) do not have gaps in the ranges or the migration will fail.<li>Create the index.js file in the migration you are adding, e.g., ``src/server/migrations/0.6.0-0.7.0/sql/index.js``. You can look at one for a previous migration to see what to do. First, you need to edit the lines so the "fromVersion" and "toVersion" correspond to the version you are going from to the version you are going to. In the running example that would be "fromVersion: '0.6.0'," and "toVersion: '0.7.0',". You now need to add a line inside "up: async db => {" for each migration file you have in this migration subdirectory. An example of a line would be:<br>await db.none(sqlFile('../migrations/0.6.0-0.7.0/sql/meter/some_meter_change.sql')); <br>where you need to make sure there is one line for each file that actually exists for this migration.</ul><li>Do extensive running and testing of OED in a web browser. When possible, test in all major web browsers.<li>Verify the upgrade from a previous version works using the directions on the latest version of the <a href="https://openenergydashboard.org/helpV1_0_0/adminUpgrading/">Admin Upgrading</a> help page. This normally means starting from the previous version on a server. If not already there see the <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">Admin Installation</a> help page on doing this where you will need to load in test data, add groups, etc. before upgrading to be sure the database migrates correctly. From the previous version you do the upgrade. After the upgrade make sure everything works correctly including the new features.<li>Create the GitHub release following the steps in <a href="https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository" rel="noopener noreferrer">GitHub Managing releases in a repository</a>. Note you can save as a draft for later release.<li>Add info about release to an OED news items and release pages on the website.<li>Celebrate.</ol></div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>OED Release</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. In preparing for an OED release, the following steps should be followed: Releases should correspond to a Milestone for the project. Announce to the Discord developer channel so everyone can look over the proposed release. Review the Milestone for this release to make sure all issues are complete or reassigned. See if there are any package or security issues that need to be addressed. Prepare the documentation pages for new release in the OpenEnergyDashboard.github.io repo. These steps assume you have forked this repo onto your own account and are working from that fork (probably in a local clone): Make sure all changes are done for the previous release and put in the OED repo for the main branch. Update your clone from the the main branch in OED repo. You can do this on your GitHub website or git fetch and merge of the main branch of the OED repo (generally referred to as upstream as where the fork came from) into your local main in Visual Studio. If you do it on the GitHub website then you will need to pull it down into your local clone. Create a new branch from the one you just updated for the new release. For example, if going from version 0.6.0 to 0.7.0 then branch main to create the branch v0.7.0. Commit these changes and the push them out to your fork (will probably require you to accept publishing the new branch if in Visual Studio and do it to your origin/forked copy). To allow testing of the new branch on your fork, go to the OpenEnergyDashboard.github.io repo on your GitHub account in a web browser. Click on the &quot;Settings&quot; tab and then click on the &quot;Pages&quot; choice on the left side of the page. Under &quot;Source&quot;, use the &quot;Branch&quot; dropdown menu to choose the new branch that you just pushed/published. This should cause you to see this branch when you go to https://&amp;lt;your GitHub ID&amp;gt;.github.io/OpenEnergyDashboard.github.io where you replace with your id. Duplicate the previous release&#39;s documentation directory into the new release directory. For example, copy help/v0.6.0 to help/v0.7.0. Unfortunately, you need to manually update the links to go from the previous release to the new release. In the new documentation directory (e.g., help/v0.7.0) edit each change listed below to update the version (e.g., v0.6.0 to v0.7.0) so do the following: Globally change the documentation links, e.g. help/v0.6.0 to help/v0.7.0. You can do this in the global search box in Visual Studio. Note it is important to prefix it with help/ so you don&#39;t edit other references to the version. edit _layouts/admin.html to add a line above &amp;lt;a href=&quot;../v0.6.0/{{ page.name }}&quot;&amp;gt;OED version 0.6.0 Help&amp;lt;/a&amp;gt; so it now has the line &amp;lt;a href=&quot;../v0.7.0/{{ page.name }}&quot;&amp;gt;OED version 0.7.0 Help&amp;lt;/a&amp;gt; Similarly, edit _layouts/help.html, to add a line above &amp;lt;a href=&quot;../v0.6.0/{{ page.name }}&quot;&amp;gt;OED version 0.6.0 Help&amp;lt;/a&amp;gt; so it now has the line &amp;lt;a href=&quot;../v0.7.0/{{ page.name }}&quot;&amp;gt;OED version 0.7.0 Help&amp;lt;/a&amp;gt; Edit help/v0.7.0/_version.html to update the version shown, e.g., 0.6.0 to 0.7.0. Update the help pages to reflect the new release. Be careful to do new screenshots if the look of OED has changed. Commit the changes. Push the changes to your fork. Check the changes work on your GitHub account (see above). When all is okay, create a pull request to put these changes into the OED GitHub pages. After it is merged, verify all still works okay. Note that if you find an issue with documentation included in previous releases then you will need to manually edit earlier versions to include this change, as appropriate. Do the final steps to prepare for the new version: Edit package.json to change the line &quot;&quot;version&quot;: &quot;0.6.0&quot;,&quot; to the version number you are about to release. Assuming you are going to version 0.7.0 (as in the next step for migrations) then it becomes: &quot;version&quot;: &quot;0.7.0&quot;,. You also need to edit package-lock.json to make a similar change as migrations do not update this file given changes in package.json. Assuming you have a migration of the database for this release, edit ``src/server/migrations/registerMigration.js`` to add a line that corresponds to the migration folder in ``src/server/migrations``. For example, if you are migrating from 0.6.0 to 0.7.0 and have the directory ``src/server/migrations/0.6.0-0.7.0`` then you add the line ``require(&#39;./0.6.0-0.7.0&#39;)`` remembering to put a comma at the end of line on the next-to-last (penultimate) line with a require.&quot; You should put the migration listings in order of their release number. Note if the last release did not have migrations then you need to use that as the previous version number so that the migration directories (and the next step) do not have gaps in the ranges or the migration will fail. Create the index.js file in the migration you are adding, e.g., ``src/server/migrations/0.6.0-0.7.0/sql/index.js``. You can look at one for a previous migration to see what to do. First, you need to edit the lines so the &quot;fromVersion&quot; and &quot;toVersion&quot; correspond to the version you are going from to the version you are going to. In the running example that would be &quot;fromVersion: &#39;0.6.0&#39;,&quot; and &quot;toVersion: &#39;0.7.0&#39;,&quot;. You now need to add a line inside &quot;up: async db =&gt; {&quot; for each migration file you have in this migration subdirectory. An example of a line would be:await db.none(sqlFile(&#39;../migrations/0.6.0-0.7.0/sql/meter/some_meter_change.sql&#39;)); where you need to make sure there is one line for each file that actually exists for this migration. Do extensive running and testing of OED in a web browser. When possible, test in all major web browsers. Verify the upgrade from a previous version works using the directions on the latest version of the Admin Upgrading help page. This normally means starting from the previous version on a server. If not already there see the Admin Installation help page on doing this where you will need to load in test data, add groups, etc. before upgrading to be sure the database migrates correctly. From the previous version you do the upgrade. After the upgrade make sure everything works correctly including the new features. Create the GitHub release following the steps in GitHub Managing releases in a repository. Note you can save as a draft for later release. Add info about release to an OED news items and release pages on the website. Celebrate."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/release/"><meta property="og:title" content="OED Release"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. In preparing for an OED release, the following steps should be followed: Releases should correspond to a Milestone for the project. Announce to the Discord developer channel so everyone can look over the proposed release. Review the Milestone for this release to make sure all issues are complete or reassigned. See if there are any package or security issues that need to be addressed. Prepare the documentation pages for new release in the OpenEnergyDashboard.github.io repo. These steps assume you have forked this repo onto your own account and are working from that fork (probably in a local clone): Make sure all changes are done for the previous release and put in the OED repo for the main branch. Update your clone from the the main branch in OED repo. You can do this on your GitHub website or git fetch and merge of the main branch of the OED repo (generally referred to as upstream as where the fork came from) into your local main in Visual Studio. If you do it on the GitHub website then you will need to pull it down into your local clone. Create a new branch from the one you just updated for the new release. For example, if going from version 0.6.0 to 0.7.0 then branch main to create the branch v0.7.0. Commit these changes and the push them out to your fork (will probably require you to accept publishing the new branch if in Visual Studio and do it to your origin/forked copy). To allow testing of the new branch on your fork, go to the OpenEnergyDashboard.github.io repo on your GitHub account in a web browser. Click on the &quot;Settings&quot; tab and then click on the &quot;Pages&quot; choice on the left side of the page. Under &quot;Source&quot;, use the &quot;Branch&quot; dropdown menu to choose the new branch that you just pushed/published. This should cause you to see this branch when you go to https://&amp;lt;your GitHub ID&amp;gt;.github.io/OpenEnergyDashboard.github.io where you replace with your id. Duplicate the previous release&#39;s documentation directory into the new release directory. For example, copy help/v0.6.0 to help/v0.7.0. Unfortunately, you need to manually update the links to go from the previous release to the new release. In the new documentation directory (e.g., help/v0.7.0) edit each change listed below to update the version (e.g., v0.6.0 to v0.7.0) so do the following: Globally change the documentation links, e.g. help/v0.6.0 to help/v0.7.0. You can do this in the global search box in Visual Studio. Note it is important to prefix it with help/ so you don&#39;t edit other references to the version. edit _layouts/admin.html to add a line above &amp;lt;a href=&quot;../v0.6.0/{{ page.name }}&quot;&amp;gt;OED version 0.6.0 Help&amp;lt;/a&amp;gt; so it now has the line &amp;lt;a href=&quot;../v0.7.0/{{ page.name }}&quot;&amp;gt;OED version 0.7.0 Help&amp;lt;/a&amp;gt; Similarly, edit _layouts/help.html, to add a line above &amp;lt;a href=&quot;../v0.6.0/{{ page.name }}&quot;&amp;gt;OED version 0.6.0 Help&amp;lt;/a&amp;gt; so it now has the line &amp;lt;a href=&quot;../v0.7.0/{{ page.name }}&quot;&amp;gt;OED version 0.7.0 Help&amp;lt;/a&amp;gt; Edit help/v0.7.0/_version.html to update the version shown, e.g., 0.6.0 to 0.7.0. Update the help pages to reflect the new release. Be careful to do new screenshots if the look of OED has changed. Commit the changes. Push the changes to your fork. Check the changes work on your GitHub account (see above). When all is okay, create a pull request to put these changes into the OED GitHub pages. After it is merged, verify all still works okay. Note that if you find an issue with documentation included in previous releases then you will need to manually edit earlier versions to include this change, as appropriate. Do the final steps to prepare for the new version: Edit package.json to change the line &quot;&quot;version&quot;: &quot;0.6.0&quot;,&quot; to the version number you are about to release. Assuming you are going to version 0.7.0 (as in the next step for migrations) then it becomes: &quot;version&quot;: &quot;0.7.0&quot;,. You also need to edit package-lock.json to make a similar change as migrations do not update this file given changes in package.json. Assuming you have a migration of the database for this release, edit ``src/server/migrations/registerMigration.js`` to add a line that corresponds to the migration folder in ``src/server/migrations``. For example, if you are migrating from 0.6.0 to 0.7.0 and have the directory ``src/server/migrations/0.6.0-0.7.0`` then you add the line ``require(&#39;./0.6.0-0.7.0&#39;)`` remembering to put a comma at the end of line on the next-to-last (penultimate) line with a require.&quot; You should put the migration listings in order of their release number. Note if the last release did not have migrations then you need to use that as the previous version number so that the migration directories (and the next step) do not have gaps in the ranges or the migration will fail. Create the index.js file in the migration you are adding, e.g., ``src/server/migrations/0.6.0-0.7.0/sql/index.js``. You can look at one for a previous migration to see what to do. First, you need to edit the lines so the &quot;fromVersion&quot; and &quot;toVersion&quot; correspond to the version you are going from to the version you are going to. In the running example that would be &quot;fromVersion: &#39;0.6.0&#39;,&quot; and &quot;toVersion: &#39;0.7.0&#39;,&quot;. You now need to add a line inside &quot;up: async db =&gt; {&quot; for each migration file you have in this migration subdirectory. An example of a line would be:await db.none(sqlFile(&#39;../migrations/0.6.0-0.7.0/sql/meter/some_meter_change.sql&#39;)); where you need to make sure there is one line for each file that actually exists for this migration. Do extensive running and testing of OED in a web browser. When possible, test in all major web browsers. Verify the upgrade from a previous version works using the directions on the latest version of the Admin Upgrading help page. This normally means starting from the previous version on a server. If not already there see the Admin Installation help page on doing this where you will need to load in test data, add groups, etc. before upgrading to be sure the database migrates correctly. From the previous version you do the upgrade. After the upgrade make sure everything works correctly including the new features. Create the GitHub release following the steps in GitHub Managing releases in a repository. Note you can save as a draft for later release. Add info about release to an OED news items and release pages on the website. Celebrate."><meta property="og:url" content="https://openenergydashboard.org/developer/release/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Releasing OED</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Releasing OED</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>In preparing for an OED release, the following steps should be followed:<ol><li>Releases should correspond to a Milestone for the project.<li>Announce to the Discord developer channel so everyone can look over the proposed release.<li>Review the Milestone for this release to make sure all issues are complete or reassigned.<li>See if there are any package or security issues that need to be addressed.<li>Prepare the documentation pages for new release in the OpenEnergyDashboard.github.io repo. These steps assume you have forked this repo onto your own account and are working from that fork (probably in a local clone):<ol><li>Make sure all changes are done for the previous release and put in the OED repo for the main branch.<li>Update your clone from the the main branch in OED repo. You can do this on your GitHub website or git fetch and merge of the main branch of the OED repo (generally referred to as upstream as where the fork came from) into your local main in Visual Studio. If you do it on the GitHub website then you will need to pull it down into your local clone.<li>Create a new branch from the one you just updated for the new release. For example, if going from version 0.6.0 to 0.7.0 then branch main to create the branch v0.7.0. Commit these changes and the push them out to your fork (will probably require you to accept publishing the new branch if in Visual Studio and do it to your origin/forked copy).<li>To allow testing of the new branch on your fork, go to the OpenEnergyDashboard.github.io repo on your GitHub account in a web browser. Click on the "Settings" tab and then click on the "Pages" choice on the left side of the page. Under "Source", use the "Branch" dropdown menu to choose the new branch that you just pushed/published. This should cause you to see this branch when you go to https://&lt;your GitHub ID&gt;.github.io/OpenEnergyDashboard.github.io where you replace <your GitHub ID> with your id.<li>Duplicate the previous release's documentation directory into the new release directory. For example, copy help/v0.6.0 to help/v0.7.0.<li>Unfortunately, you need to manually update the links to go from the previous release to the new release. In the new documentation directory (e.g., help/v0.7.0) edit each change listed below to update the version (e.g., v0.6.0 to v0.7.0) so do the following:<ul><li>Globally change the documentation links, e.g. help/v0.6.0 to help/v0.7.0. You can do this in the global search box in Visual Studio. Note it is important to prefix it with help/ so you don't edit other references to the version.<li>edit _layouts/admin.html to add a line above<br> &lt;a href="../v0.6.0/{{ page.name }}"&gt;OED version 0.6.0 Help&lt;/a&gt;<br> so it now has the line<br> &lt;a href="../v0.7.0/{{ page.name }}"&gt;OED version 0.7.0 Help&lt;/a&gt;<br><li>Similarly, edit _layouts/help.html, to add a line above<br> &lt;a href="../v0.6.0/{{ page.name }}"&gt;OED version 0.6.0 Help&lt;/a&gt;<br> so it now has the line<br> &lt;a href="../v0.7.0/{{ page.name }}"&gt;OED version 0.7.0 Help&lt;/a&gt;<br><li>Edit help/v0.7.0/_version.html to update the version shown, e.g., 0.6.0 to 0.7.0.</ul><li>Update the help pages to reflect the new release. Be careful to do new screenshots if the look of OED has changed.<li>Commit the changes.<li>Push the changes to your fork.<li>Check the changes work on your GitHub account (see above). When all is okay, create a pull request to put these changes into the OED GitHub pages. After it is merged, verify all still works okay.<li>Note that if you find an issue with documentation included in previous releases then you will need to manually edit earlier versions to include this change, as appropriate.</ol><li>Do the final steps to prepare for the new version:<ul><li>Edit package.json to change the line ""version": "0.6.0"," to the version number you are about to release. Assuming you are going to version 0.7.0 (as in the next step for migrations) then it becomes: "version": "0.7.0",. You also need to edit package-lock.json to make a similar change as migrations do not update this file given changes in package.json.<li>Assuming you have a migration of the database for this release, edit ``src/server/migrations/registerMigration.js`` to add a line that corresponds to the migration folder in ``src/server/migrations``. For example, if you are migrating from 0.6.0 to 0.7.0 and have the directory ``src/server/migrations/0.6.0-0.7.0`` then you add the line ``require('./0.6.0-0.7.0')`` remembering to put a comma at the end of line on the next-to-last (penultimate) line with a require." You should put the migration listings in order of their release number. Note if the last release did not have migrations then you need to use that as the previous version number so that the migration directories (and the next step) do not have gaps in the ranges or the migration will fail.<li>Create the index.js file in the migration you are adding, e.g., ``src/server/migrations/0.6.0-0.7.0/sql/index.js``. You can look at one for a previous migration to see what to do. First, you need to edit the lines so the "fromVersion" and "toVersion" correspond to the version you are going from to the version you are going to. In the running example that would be "fromVersion: '0.6.0'," and "toVersion: '0.7.0',". You now need to add a line inside "up: async db => {" for each migration file you have in this migration subdirectory. An example of a line would be:<br>await db.none(sqlFile('../migrations/0.6.0-0.7.0/sql/meter/some_meter_change.sql')); <br>where you need to make sure there is one line for each file that actually exists for this migration.</ul><li>Do extensive running and testing of OED in a web browser. When possible, test in all major web browsers.<li>Verify the upgrade from a previous version works using the directions on the latest version of the <a href="https://openenergydashboard.org/helpV1_0_0/adminUpgrading/">Admin Upgrading</a> help page. This normally means starting from the previous version on a server. If not already there see the <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">Admin Installation</a> help page on doing this where you will need to load in test data, add groups, etc. before upgrading to be sure the database migrates correctly. From the previous version you do the upgrade. After the upgrade make sure everything works correctly including the new features.<li>Create the GitHub release following the steps in <a href="https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository" rel="noopener noreferrer">GitHub Managing releases in a repository</a>. Note you can save as a draft for later release.<li>Add info about release to an OED news items and release pages on the website.<li>Celebrate.</ol></div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/technologies/index.html b/developer/technologies/index.html
index 882d16ba..25988fcb 100644
--- a/developer/technologies/index.html
+++ b/developer/technologies/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Technology Overview</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Frontend Technologies Some of the most complex technologies we use are those that turn the code we write - TypeScript and ES6 JavaScript - into tiny, optimized code that the browser can execute. This is known as packing, tree-shaking, and uglification. See the diagram below for a quick overview of how this works. After this process, our hundreds of source files and dependencies are converted into a single multi-megabyte file which will be transmitted to our users over HTTP. Plugins within Webpack, such as the LodashModuleReplacementPlugin, further optimize the size of this bundle. The major technology here is TypeScript, a way to provide static guarantees about code - that is, it catches your errors before the code is ever run. For instance, the following code is valid JavaScript but invalid TypeScript: let v = 0; doSomethingWithInt(v); v = &quot;Hello, world!&quot;; doSomethingWithInt(v); In JavaScript, you&#39;ll get a runtime error or weird behavior. In TypeScript, the compiler will tell you you&#39;re not allowed to do that."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/technologies/"><meta property="og:title" content="Technology Overview"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Frontend Technologies Some of the most complex technologies we use are those that turn the code we write - TypeScript and ES6 JavaScript - into tiny, optimized code that the browser can execute. This is known as packing, tree-shaking, and uglification. See the diagram below for a quick overview of how this works. After this process, our hundreds of source files and dependencies are converted into a single multi-megabyte file which will be transmitted to our users over HTTP. Plugins within Webpack, such as the LodashModuleReplacementPlugin, further optimize the size of this bundle. The major technology here is TypeScript, a way to provide static guarantees about code - that is, it catches your errors before the code is ever run. For instance, the following code is valid JavaScript but invalid TypeScript: let v = 0; doSomethingWithInt(v); v = &quot;Hello, world!&quot;; doSomethingWithInt(v); In JavaScript, you&#39;ll get a runtime error or weird behavior. In TypeScript, the compiler will tell you you&#39;re not allowed to do that."><meta property="og:url" content="https://openenergydashboard.org/developer/technologies/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Technology Overview</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Technology Overview</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><h2>Frontend Technologies</h2><p>Some of the most complex technologies we use are those that turn the code we write - TypeScript and ES6 JavaScript - into tiny, optimized code that the browser can execute. This is known as packing, tree-shaking, and uglification. See the diagram below for a quick overview of how this works.<p><img src="../images/OEDFrontEndOverview.jpg" alt="The flow of OED's source code from source JS, TS, and CSS, through various loaders, into Webpack, out into source maps, back into Webpack, and finally into the final bundle which is served to the client." data-canonical-src="https://i.imgur.com/YZFC9xZ.jpg"><p>After this process, our hundreds of source files and dependencies are converted into a single multi-megabyte file which will be transmitted to our users over HTTP. Plugins within Webpack, such as the LodashModuleReplacementPlugin, further optimize the size of this bundle.<p>The major technology here is TypeScript, a way to provide static guarantees about code - that is, it catches your errors before the code is ever run. For instance, the following code is valid JavaScript but invalid TypeScript:<pre><code>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Technology Overview</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Frontend Technologies Some of the most complex technologies we use are those that turn the code we write - TypeScript and ES6 JavaScript - into tiny, optimized code that the browser can execute. This is known as packing, tree-shaking, and uglification. See the diagram below for a quick overview of how this works. After this process, our hundreds of source files and dependencies are converted into a single multi-megabyte file which will be transmitted to our users over HTTP. Plugins within Webpack, such as the LodashModuleReplacementPlugin, further optimize the size of this bundle. The major technology here is TypeScript, a way to provide static guarantees about code - that is, it catches your errors before the code is ever run. For instance, the following code is valid JavaScript but invalid TypeScript: let v = 0; doSomethingWithInt(v); v = &quot;Hello, world!&quot;; doSomethingWithInt(v); In JavaScript, you&#39;ll get a runtime error or weird behavior. In TypeScript, the compiler will tell you you&#39;re not allowed to do that."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/technologies/"><meta property="og:title" content="Technology Overview"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Frontend Technologies Some of the most complex technologies we use are those that turn the code we write - TypeScript and ES6 JavaScript - into tiny, optimized code that the browser can execute. This is known as packing, tree-shaking, and uglification. See the diagram below for a quick overview of how this works. After this process, our hundreds of source files and dependencies are converted into a single multi-megabyte file which will be transmitted to our users over HTTP. Plugins within Webpack, such as the LodashModuleReplacementPlugin, further optimize the size of this bundle. The major technology here is TypeScript, a way to provide static guarantees about code - that is, it catches your errors before the code is ever run. For instance, the following code is valid JavaScript but invalid TypeScript: let v = 0; doSomethingWithInt(v); v = &quot;Hello, world!&quot;; doSomethingWithInt(v); In JavaScript, you&#39;ll get a runtime error or weird behavior. In TypeScript, the compiler will tell you you&#39;re not allowed to do that."><meta property="og:url" content="https://openenergydashboard.org/developer/technologies/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Technology Overview</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Technology Overview</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><h2>Frontend Technologies</h2><p>Some of the most complex technologies we use are those that turn the code we write - TypeScript and ES6 JavaScript - into tiny, optimized code that the browser can execute. This is known as packing, tree-shaking, and uglification. See the diagram below for a quick overview of how this works.<p><img src="../images/OEDFrontEndOverview.jpg" alt="The flow of OED's source code from source JS, TS, and CSS, through various loaders, into Webpack, out into source maps, back into Webpack, and finally into the final bundle which is served to the client." data-canonical-src="https://i.imgur.com/YZFC9xZ.jpg"><p>After this process, our hundreds of source files and dependencies are converted into a single multi-megabyte file which will be transmitted to our users over HTTP. Plugins within Webpack, such as the LodashModuleReplacementPlugin, further optimize the size of this bundle.<p>The major technology here is TypeScript, a way to provide static guarantees about code - that is, it catches your errors before the code is ever run. For instance, the following code is valid JavaScript but invalid TypeScript:<pre><code>
 let v = 0;
 doSomethingWithInt(v);
 v = "Hello, world!";
diff --git a/developer/testData/index.html b/developer/testData/index.html
index 5d200c85..7eb2afb4 100644
--- a/developer/testData/index.html
+++ b/developer/testData/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Test Data</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Developers want to have test meter data for OED development that is consistent, stable and does not require having access to actual meters. This describes how to get and load such meter test data along with related groups, units &amp; conversions. Prerequisites What follows assumes you have a properly installed and working OED but have not yet loaded in the reading data described here. If they have already been loaded then the loading step for that meter will be skipped. At a minimum you should be able to see the main OED page in a web browser (normally URL of localhost:3000). Normally the database is automatically created and works fine. If you get errors about the database then you need to address them before you can do this or get the test data in (if you get errors during this process). Inserting the standard OED test data The simple and mathematical test data is created in OED by doing the following (they are described later): Make sure you have OED running so it is available to do the necessary work. Open a terminal in the web/vsc Docker container by right clicking on the web container in the Docker extension of VSC and attaching a shell. (Described in the getting started directions) In the terminal, run the command npm run testData. This may take a few minutes but when it completes there should be new meters with data, new groups, the DB structures are all updated and the CSV files used will be removed unless there was an error. This generates all the standard test data except the one where readings are every minute since that is a large dataset that is less frequently used. See the next step before you can use the new OED information within the OED web page. As we update OED pages, the code is avoiding reloading Redux state every time. Thus, to see all the changes in Redux state and to get the array for graphing units, you need to reload an existing OED web page. Once done you should see all the test meters/groups and data as described below. If this does not happen then an error likely occurred so carefully look at the output in your terminal that you used above. If you only want to load some of the data (not the common usage), you can look at package.json for the individual commands to insert the mathematical data. The others are so small/fast that they are done as above. See Mathematical test data section below. Comparison data When you do a compare graph, you choose how far from current time you compare. As a result, you need current readings and ones immediately before that time to get data for the comparison graph. If you are using meter data that does not have this, you will need to create it. Here is how to do it: Get the timezone of your local machine (not the Docker container for OED) by doing this in the terminal: date +%Z. For what follows the timezone is assumed to be CDT but you should change if your timezone differs. If you want to be extra careful, check the time in Postgres. Open a Postgres terminal by attaching a shell to the database container in a similar way to how you did it above for the web container. Once inside the database shell, do: psql -U oed to access the database terminal and do the following within this terminal. Verify timezone is correct by doing: select clock_timestamp() at time zone &#39;CDT&#39;;. Make sure that it shows the same time as on the clock on your computer that you found in the previous step and replace CDT with the timezone using. You can now quit postgres by doing: \q Open a terminal by attaching a shell to the OED web container as was done earlier in this file. In the web terminal do: node -e &#39;require(&quot;./src/server/util/developer.js&quot;).shiftReadings(&quot;meter name&quot;, &quot;CDT&quot;)&#39; Where &quot;meter name&quot; is replaced with the meter you want to shift and still use the double quotes. Similarly, CDT should be the timezone found above. The console will show (the shift value will be different): shifting meter &quot;meter name&quot; to timezone &quot;CDT&quot; The readings were shifted by: 10 days refreshing all views since readings changed [INFO@2023-10-03T02:05:08.194+00:00] Refreshing All Reading Views... [INFO@2023-10-03T02:05:08.196+00:00] Refreshing Materialized Daily Reading Views [INFO@2023-10-03T02:05:08.197+00:00] Refreshing Materialized Hourly Reading Views [INFO@2023-10-03T02:05:14.231+00:00] Daily View Refreshed [INFO@2023-10-03T02:05:19.900+00:00] Materialized Hourly View Refreshed [INFO@2023-10-03T02:05:19.902+00:00] ...Views Refreshed! If you don&#39;t want to refresh the readings (then cannot graph the new data but useful if shifting lots of meters until the last one) then add a third parameter of false: node -e &#39;require(&quot;./src/server/util/developer.js&quot;).shiftReadings(&quot;meter name&quot;, &quot;CDT&quot;, false)&#39; You need to refresh the web page with OED to see the new compare values of shifted data. This process can be repeated as often as desired to keep the readings current. If you give an incorrect meter name that does not exist then an error similar to the following will appear: [ERROR@2023-10-02T22:56:40.591+00:00] Unhandled Promise Rejection: TypeError: Cannot read properties of null (reading &#39;humanize&#39;) Stacktrace: TypeError: Cannot read properties of null (reading &#39;humanize&#39;) at Object.shiftReadings (/usr/src/app/src/server/util/developer.js:36:71) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) (node:288) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1) (Use `node --trace-warnings ...` to show where the warning was created) The following figure shows the result after shifting the three amp meters to current time and then doing a comparison graphic for 1 week. There is no difference between the meters since they all have the same shape and only scaling of the readings. Map data The following assumes you have loaded the test data into your development OED system. You can use other meter data if you prefer. Please use the admin map creating documentation for information on how to load and calibrate a map. This page only describes the necessary details of the test map. You need to be logged in as an admin to complete these steps. Use the sample Happy Place map by downloading it. This is the map you upload into OED. We will call it &quot;Happy Place&quot; and you can use that name in OED or some other name. The map angle is 0.0 degrees. During the calibration step, you will use a mythical GPS coordinate system of (0-30, 0-50) which are real GPS values but not usual for a map. This large area works because we will make a perfect calibration with no error. This means the lower, left corner of the map has GPS coordinate (0, 0) and the top, right has GPS coordinate (50, 30). The Plotly grid has values of (0, 0) for lower, left and (300, 500) for the top, right. This means the coordinates are reversed for GPS (latitude, longitude) compared to the grid (x, y) and are a factor of 10 smaller. During calibration, click on three places on the map. In principle it does not matter where but three spread out places on the map is better normally. When you do that, OED will show the grid coordinate you clicked on. As just explained, you need to reverse the coordinates and divide by 10. Thus, if you are told &quot;input GPS coordinate that corresponds to the point: x: 277, y: 461 in this format -&gt; latitude,longitude&quot; then you enter &quot;46.1, 27.7&quot; for the GPS value in the box and submit. Repeat this 3 times and you should then see an error of 0% for both directions. If not, start over. If yes, then save changes to the database. The following meters and groups will automatically be placed at these locations: Sin Amp 1 kWh at Play Place Sin Amp 2 kWh at Swimming Pool Sin Amp 1 kWh at Theater Sin Amp 1 + 2 kWh (group) at Cafeteria Sin Amp 2 + 3 kWh (group) at Housing If all went well, you should now see the following on the map page. Rotated map Sometimes you want to test a rotated map. In this case use Happy Place 30 Deg map that was rotated by 30 degrees. This does not impact the GPS coordinates but means the simple correspondence between the OED grid and GPS no longer holds. During calibration, use these points: Bottom, right of Swimming Pool at coordinate 265, 342 with GPS value of 39.5, 27.7 Bottom, right of Theater at coordinate 217, 234 with GPS value of 23.7, 29.3 Bottom, right of Cafeteria at coordinate 85, 252, with GPS value of 17.0, 12.7 This will give: result: x: 3.127%, y: 0.647%. If you switch to this map then you should see the following Where items are shown at the same location but the map is rotated. Simple Test Data Meter data The simple/basic test data is not representative of real meter data nor mathematical but it is easy to use. Each meter has readings for five days and the line graphs should be a straight line. The following table gives the expected values for the line graphs for all units for these simple meters where NA indicates that unit is not allowed/not compatible. The item for each meter/row that is marked with a * indicates the default graphic unit if one is not already selected. All values are for per hour for the rate. Note kW and kWh are not impacted by a rate change. The Gallon and Gallon flow are available for testing the rate choices. The table also contains the mathematical test data in the lower part. Meter name Dates Notes kWh BTU MJ M3 Gas 100 W bulb US Dollar Euro kg Metric ton kg of CO2 Metric ton of CO2 Fahrenheit Celsius kW Gallon Liter Gallon per minute Liter per hour Electric Utility kWh 6/1-5/2021 graphs as raw meter data 1 - 5* 3412.08 - 17060.4 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh not displayable 6/1-5/2021 graphs as raw meter data; only if admin 1 - 5* 3412.08 - 17060.4 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh 2-6 6/1-5/2021 graphs as meter data 2 - 6* 6824.16 - 20472.48 7.2 - 21.6 0.186 - 0.559 2 - 6 0.23 - 0.69 0.2 - 0.6 NA NA 1.418 - 4.254 1.418e-3 - 4.254e-3 NA NA NA NA NA NA NA Electric Utility kWh in BTU 6/1-5/2021 graphs as meter data 1 - 5 3412.08 - 17060.4* 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh in MTon CO2 6/1-5/2021 graphs as meter data 1 - 5 3412.08 - 17060.4* 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3* NA NA NA NA NA NA NA Natural Gas BTU 6/1-5/2021 graphs as meter data 2.93e-4 - 1.465e-3 1 - 5* 1.06e-3 - 5.27e-3 2.73e-5 - 1.36e-4 2.93e-4 - 1.465e-3 2.95e-6 - 1.48e-5 2.6e-6 - 1.3e-5 NA NA 5.28e-5 - 2.64e-4 5.28e-8 - 2.64e-7 NA NA NA NA NA NA NA Natural Gas BTU in Dollar 6/1-5/2021 graphs as meter data 2.93e-4 - 1.465e-3 1 - 5 1.06e-3 - 5.27e-3 2.73e-5 - 1.36e-4 2.93e-4 - 1.465e-3 2.95e-6 - 1.48e-5* 2.6e-6 - 1.3e-5 NA NA 5.28e-5 - 2.64e-4 5.28e-8 - 2.64e-7 NA NA NA NA NA NA NA Natural Gas Dollar 6/1-5/2021 graphs as meter data NA NA NA NA NA 1 - 5* 0.88-4.4 NA NA NA NA NA NA NA NA NA NA NA Natural Gas Cubic Meters 6/1-5/2021 graphs as meter data 10.7 - 53.4 3.64e4 - 1.82e5 38.5 - 192.3 1 - 5* 10.7 - 53.4 0.11 - 0.55 0.97 - 4.84 NA NA NA NA NA NA NA NA NA NA NA Trash Kg 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA 1 - 5* 1e-3 - 5e-3 NA NA NA NA NA NA NA NA NA Temp Fahrenheit 0-212 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA 0 - 212* -17.78 - 100 NA NA NA NA NA Temp Fahrenheit in Celsius 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA 0 - 212 -17.78 - 100* NA NA NA NA NA Electric kW 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA 1 - 5* NA NA NA NA Electric kW 2-6 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA 2 - 6* NA NA NA NA Water Gallon 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA NA 1-5* 3.79-18.93 NA NA Water Gallon flow 1-5 per minute 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA 1-5* 227.12-1135.6 Sin 4 Day kWh 2020 graphs as 4 day/raw meter 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 4 Hour kWh 2020 graphs daily but not less than 4 hour/raw if zoomed 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 15 Min kWh 2020 graphs daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 23 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 15 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin Amp 1 kWh 2020-21 graphs as daily 0 - 1 sine* 0 - ~3402 0 - ~3.6 0 - ~0.093 0 - 1 0 - ~0.115 0 - ~0.101 NA NA 0 - ~0.708 0 - 7.08e-4 NA NA NA NA NA NA NA Sin Amp 2 kWh 2020-21 graphs as daily 0 - 2 sine* 0 - ~6804 0 - ~7.2 0 - ~0.18 0 - 2 0 - ~0.23 0 - ~0.202 NA NA 0 - ~1.42 0 - 1.42e-4 NA NA NA NA NA NA NA Sin Amp 3 kWh 2020-21 graphs as daily 0 - 3 sine* 0 - ~10206 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.345 0 - ~0.303 NA NA 0 - ~2.12 0 - 2.12-3 NA NA NA NA NA NA NA Sin Sq kWh 2020 graphs as daily 0 - 2.5 sine* 0 - ~8520 0 - ~9.0 0 - ~0.23 0 - 2.5 0 - ~0.29 0 - ~0.252 NA NA 0 - ~1.77 0 - 1.77-3 NA NA NA NA NA NA NA Cos Sq kWh 2020 graphs as daily 0 - 2.5 sine* 0 - ~8520 0 - ~9.0 0 - ~0.23 0 - 2.5 0 - ~0.29 0 - ~0.252 NA NA 0 - ~1.77 0 - 1.77-3 NA NA NA NA NA NA NA Cos 23 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA For bar graphs, you can easily check the day bars for the simple data. Wider bars will only show for data with more days as OED does not show bars with days missing at the start or end. The value can be found by taking the day value on the line graph (shown in the table above) and multiplying by 24. For example, Electric Utility kWh as kWh has line values of 1-5 and bar values of 24-120. In US Dollars it is 0.115 - 0.575 on line and 2.76-13.8 on bar. Tis is because it is 24 times larger as the sum over the 24 hours of the rate/day. This holds for both quantity and flow units. If the custom slider is used and the bar width is 2 days then you get two bars: June 2-3 and Jun 4-5. The value is 120 (48 + 72) and 216 (96 + 120). Group data The following table gives groups that are created from the meters above as well as the mathematical meter data described below. All area units are sq. meters and not set/zero if left off. Group name Default graphic unit Values for default unit area Included meters Included groups All meters included Compatible units Note Electric Utility 1-5 + 2-6 kWh kWh 3 - 11 10 Electric Utility kWh, Electric Utility kWh 2-6 none Electric Utility kWh, Electric Utility kWh 2-6 see Electric Utility kWh Electric Utility 1-5 + 2-6 Dollar US Dollar 0.345 - 1.265 10 Electric Utility kWh, Electric Utility kWh 2-6 none Electric Utility kWh, Electric Utility kWh 2-6 see Electric Utility kWh Natural Gas Dollar Euro Euro 0.88 - 4.4 Natural Gas Dollar none Natural Gas Dollar see Natural Gas Dollar Electric Utility 1-5 + Natural Gas Dollar Euro Euro 0.9812 - 4.906 Electric Utility kWh, Natural Gas Dollar none Electric Utility kWh, Natural Gas Dollar see Natural Gas Dollar Electric Utility 1-5 kWh not displayable kWh 1 - 5 Electric Utility kWh none Electric Utility kWh see Electric Utility kWh This should only been seen and graphable by an admin Electric kW + 2-6 kW kW 3 - 11 100 Electric kW, Electric kW 2-6 none Electric kW, Electric kW 2-6 see Electric Utility kWh SqSin + SqCos kWh kWh very close to 2.5 10 testSqSin kWh, testSqCos kWh none testSqSin kWh, testSqCos kWh see Electric Utility kWh SqSin + SqCos no unit none same as above testSqSin kWh, testSqCos kWh none testSqSin kWh, testSqCos kWh see Electric Utility kWh Will graph once a unit compatible with kWh is chosen Sin Amp 1 + 2 kWh kWh sine from 0-3 1000 Sin Amp 1 kWh, Sin Amp 2 kWh none Sin Amp 1 kWh, Sin Amp 2 kWh see Electric Utility kWh Sin Amp 2 + 3 kWh kWh sine from 0-5 1000 Sin Amp 2 kWh, Sin Amp 3 kWh none Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh Sin Amp 1 + (2 - 3) kWh kWh sine from 0-6 10000 Sin Amp 1 kWh Sin Amp 2 + 3 kWh Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh includes group Amp 1 + 2 + (1 + 2) + (2 -3) kWh kWh sine from 0-6 10000 Sin Amp 1 kWh, Sin Amp 2 kWh Sin Amp 1 + 2 kWh, Sin Amp 2 + 3 kWh Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh includes 2 groups and 2 duplicate meters Mathematical Test Data The OED test data generation code can generate sine and cosine based data. It has several advantages: You can create on your own machine without needing to download anything. The provided script will generate the data and load it into your OED database for use within the system. Since it has a regular pattern, it is often easy to see issues in graphed data. Different datasets can be used to focus on different types of testing. Note that the values are shifted so the minimum is 0 since most meter data is like that. It is easy to use this data by following these steps The following table gives a list of the available data and information about it. The meter name assumes you use the provided script to load the data. (If you want to generate the test data outside the usual script, the &amp;ltcommand name&amp;gt is what you use to create this dataset manually with npm run &amp;ltcommand name&amp;gt in a web/vsc Docker container terminal. You will then need to load the reading data into OED as described on the reading import page. The file will have the name indicated and is located in the src/server/test/db/data/automatedTests/ directory. It is important to properly set the reading frequency to see the expect result.) The meter name is the one if the testData script is used to create and load this data. Description Meter name # points/file size &amp;ltcommand name&amp;gt File produced Sine function with a period of 45 days and amplitude 3 for 1 year with points every 4 days Sin 4 Day kWh 92 points/5kB generateFourDayTestingData fourDayFreqTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 4 hours Sin 4 Hour kWh 2196 points/129kB generateFourHourTestingData fourHourFreqTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 23 minutes Sin 23 Min kWh 22915 points/1.4MB generateTwentyThreeMinuteTestingData twentyThreeMinuteFreqTestData.csv. Sine function with a period of 45 days and amplitude 3 for 1 year with points every 15 minutes Sin 15 Min kWh 35136 points/2.1MB generateFifteenMinuteTestingData fifteenMinuteFreqTestData.csv Cosine function with a period of 45 days and amplitude 3 for 1 year with points every 23 minutes Cos 23 Min kWh 22915 points/1.4MB generateCosineTestingData 23FreqCosineTestData.csv Sine squared function with a period of 45 days and amplitude 2.5 for 1 year with points every 1 day Sin Sq kWh 366 points/21kB generateSineSquaredTestingData 2.5AmpSineSquaredTestData.csv Cosine squared function with a period of 45 days and amplitude 2.5 for 1 year with points every 1 day Cos Sq kWh 366 points/21kB generateCosineSquaredTestingData 2.5AmpCosineSquaredTestData.csv Sine function with a period of 45 days and amplitudes 1-3 for 2 years with points every 15 minutes Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh 70176 points/4.2MB each; 12.6MB total generateVariableAmplitudeTestingData 15Freq1AmpSineTestData.csv, 15Freq2AmpSineTestData.csv, 15Freq3AmpSineTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 1 minute. This is normally used for specialized testing of a large number of readings and not automatically generated by the script. Sin 1 Min 527040 points/32MB generateOneMinuteTestingData oneMinuteFreqTestData.csv What OED should display with this test data This section gives a range of samples of what OED will display when graphing the test data described above. Simple data Quantity data The following figure shows the kWh meters and groups as a line graph: The following figure shows the kWh meters and groups as a 1 day bar graph: OED will show a blank bar graphic in this case (and all the 5 day meters) for 1 or 4 weeks because it will not display bars with incomplete meter data at the start or end. Same as the line graphic above but in kg of CO2 to show changing the unit: Same as above but as a 1 day bar graph: The following figure shows the water meter as a line graph where the rate is Day to show changing the rate and a different type of unit. Note KWh must be shown per hour. Flow data The following figure shows the kW meters and groups as a line graph: The following figure shows the kW meters and groups as a 1 day bar graph: The following figure shows the water flow meter as a line graph where the rate is Minute to show changing the rate and a different type of unit. Note kW must be shown per hour. Raw data The following figure shows a temperature meter that collects in Fahrenheit but has a default graphic unit of Celsius as a line graph: Mathematical data The following picture shows the meters Sin 4 Day kWh, Sin 4 Hour kWh, Sin 23 Min kWh, Sin 15 Min kWh. It is designed to show how the number of points impact the line quality in OED and verify that varied reading rates do not impact the OED code. What you see is that the 4 day line is shifted due to the placement of the time values. The other meters are very similar in value. This shows that the daily averaging in OED is accurate. Note that in this and all line graphics, you will see the similar values as you zoom in to see hourly or meter level points. This is because the data is kW. The only change you will see is in the quality of the graphic if you zoom in so tight that you have limited points to graph. The following picture shows the same meters as above but as a bar graph with 4 week bars. In a perfect world, all the bars would have the same value for a given date range. As can be seen, there are small differences where the value varies more as the frequency of the readings goes down. This variation is due to the inaccuracy of low frequency readings as is normal. The following picture shows a line graphic of the sin values for the 3 different amplitudes (1-3). As expected, they have the same period with a different amplitude. Plus, it looks nice! The following picture shows a line graphic of a group containing all the sine amplitudes above but with 1 &amp; 2 included twice. OED does not duplicate the values so the sum is a maximum of 6 or 1 + 2 + 3. The following picture shows a sin and cos with the same amplitude. It should be noted that normally sin and cos are phase shifted so the high of one is the low of the other. You do not see that because the values were shifted to all be positive. The following picture shows the meters Sin Sq kWh &amp; Cos Sq kWh along with a group containing both meters (Sin Sq + Cos Sq kWh). If OED is working properly then the group should have a constant value since sin^2 + cos^1 = 1 or the value of the amplitude in this case. This is a good test of whether groups work (for simple groups of only two meters). If you want to see how accurate OED is then just graph this group and you will see that the value is always very close to 2.5. The following image shows sin with readings every minute. It is a very high quality version of the first picture with points that are less frequent. It is zoomed in to less than a day to show the minute points. This data is not automatically generated and is normally only used to test OED&#39;s speed when there is lots of reading points. You would need to generate this data (placed in src/server/test/db/data/automatedTests/oneMinuteFreqTestData.csv) and then upload via CSV as described for the real-world data. Real World Test Data This data can show what happens with actual data. However, it is harder to see when things are off. It is provided as an alternative to the mathematical data but will probably be used less now that that data exists. The table below lists the types of test data we have. The first four all have 3.5 years of electric data but for different meters so the values vary. The last one is a sample file that you can edit to create your own data. Description Readings CSV Size of Readings File Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearA.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearB.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearC.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearD.csv 1.3MB Sample file to edit for your own data sampleReadings.csv 0 MB Using the provided data Choose the file you want where clicking on the link in a web browser will download that file. Note you can load as many test data files as you want into a single OED instance. The import of this data into OED uses the CSV import feature that is described in the CSV import documentation and pages linked from that page, esp. about readings. You do not need to know all those details but can get further information as needed. Loading the data into your OED You will want to have OED running during this process. Start it with Docker as you should have previously done. Log in as an admin user. Go to the CSV upload page using the &quot;CSV&quot; button in the top, right of the OED web page. You should default to the &quot;Readings&quot; tab which is what you want. Now do the following: Enter the meter name in the box where the sample graph below used the file name without the extension and spaces, e.g., &quot;Three Year A&quot; for the first file. You can use any name you like. Use the &quot;Choose File&quot; button to select the file with the reading data you are uploading. Check the &quot;Create Meter&quot; and &quot;Header row&quot; boxes. Check the &quot;Refresh Readings&quot; and &quot;Refresh Hourly Readings&quot; boxes so the readings will be available right away for graphing. You can delay doing this until the last upload if you are doing multiple readings files to make it a little faster. If you forget to do this then you must manually refresh the readings to graph them. Click the &quot;Submit CSV Data&quot; button to start the upload. This will take a little while (probably less than one minute). A popup window will appear when the upload is done telling you the status. It should be SUCCESS without any warnings if all went well. If something went wrong then address the issue. Note if there are lots of errors then you need to look at the log or console where OED is running to see them all. Reload the web page where OED is running to see the new meter(s). Go to the meter page and assign the unit and, if desired, the default graphic unit for each meter. The examples make them Electric_Utility for the unit and kWh for the default graphic unit. Also set the reading frequency to 01:00:00 or 1 hour since that is what the data represents. You should now be able to graph them. Below is a line graphic with the four 3.5 year meters. If all went well then this is what you should see. If you don&#39;t see this then something is wrong and you should not continue this process and instead ask us for help. (See link at bottom of page) Creating own data You can download the sample data from the table above. You can edit the sampleReadings.csv file by opening it in you preferred editor where a spreadsheet program is fine as long as you make sure to save it as a CSV file. Remove the two sample readings on lines 2 and 3 of the file and create new lines with the data you want. Note that normally the end time of the previous point is equal to the start time of the next point in real meter data. You can put in as many lines as you want with readings. This file has a header row so it is easier to see what goes in each column. Once you are done editing and save the file in CSV format, import it the same way as the provided data above except you need to check the &quot;Header Row&quot; box since the file has a header row. Deal with any messages to correct problems and see the readings import page for more info on dealing with issues. Note if there are lots of errors then you need to look at the log or console where OED is running to see them all. Database issue If you cannot load the data into the database or it disappears after shutting down OED, then you likely have a database issue. To test you can do the following: Log in as the admin. Change the default graph type to something else (say bar) and save the change. Make sure it gives the green popup that it saved okay. Refresh the web browser and go tho the main OED page. It should have preselected the bar choice for graphic indicating that it is the default choice. If this does not work then verify the admin preference change was actually saved without error because it seems your installation is not saving to the database. Shut OED down and bring it back up. When OED is done installing, go to the web page and refresh the page. Again, you should see the bar as the default selection. If this fails then the database changes are not being saved between runs of OED. This indicates an install issue. If you don&#39;t know what to do then contact us. Help You should now be done and have the test data in your OED development system. If something did not work then you can seek help from the project by contacting us."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/testData/"><meta property="og:title" content="Test Data"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Developers want to have test meter data for OED development that is consistent, stable and does not require having access to actual meters. This describes how to get and load such meter test data along with related groups, units &amp; conversions. Prerequisites What follows assumes you have a properly installed and working OED but have not yet loaded in the reading data described here. If they have already been loaded then the loading step for that meter will be skipped. At a minimum you should be able to see the main OED page in a web browser (normally URL of localhost:3000). Normally the database is automatically created and works fine. If you get errors about the database then you need to address them before you can do this or get the test data in (if you get errors during this process). Inserting the standard OED test data The simple and mathematical test data is created in OED by doing the following (they are described later): Make sure you have OED running so it is available to do the necessary work. Open a terminal in the web/vsc Docker container by right clicking on the web container in the Docker extension of VSC and attaching a shell. (Described in the getting started directions) In the terminal, run the command npm run testData. This may take a few minutes but when it completes there should be new meters with data, new groups, the DB structures are all updated and the CSV files used will be removed unless there was an error. This generates all the standard test data except the one where readings are every minute since that is a large dataset that is less frequently used. See the next step before you can use the new OED information within the OED web page. As we update OED pages, the code is avoiding reloading Redux state every time. Thus, to see all the changes in Redux state and to get the array for graphing units, you need to reload an existing OED web page. Once done you should see all the test meters/groups and data as described below. If this does not happen then an error likely occurred so carefully look at the output in your terminal that you used above. If you only want to load some of the data (not the common usage), you can look at package.json for the individual commands to insert the mathematical data. The others are so small/fast that they are done as above. See Mathematical test data section below. Comparison data When you do a compare graph, you choose how far from current time you compare. As a result, you need current readings and ones immediately before that time to get data for the comparison graph. If you are using meter data that does not have this, you will need to create it. Here is how to do it: Get the timezone of your local machine (not the Docker container for OED) by doing this in the terminal: date +%Z. For what follows the timezone is assumed to be CDT but you should change if your timezone differs. If you want to be extra careful, check the time in Postgres. Open a Postgres terminal by attaching a shell to the database container in a similar way to how you did it above for the web container. Once inside the database shell, do: psql -U oed to access the database terminal and do the following within this terminal. Verify timezone is correct by doing: select clock_timestamp() at time zone &#39;CDT&#39;;. Make sure that it shows the same time as on the clock on your computer that you found in the previous step and replace CDT with the timezone using. You can now quit postgres by doing: \q Open a terminal by attaching a shell to the OED web container as was done earlier in this file. In the web terminal do: node -e &#39;require(&quot;./src/server/util/developer.js&quot;).shiftReadings(&quot;meter name&quot;, &quot;CDT&quot;)&#39; Where &quot;meter name&quot; is replaced with the meter you want to shift and still use the double quotes. Similarly, CDT should be the timezone found above. The console will show (the shift value will be different): shifting meter &quot;meter name&quot; to timezone &quot;CDT&quot; The readings were shifted by: 10 days refreshing all views since readings changed [INFO@2023-10-03T02:05:08.194+00:00] Refreshing All Reading Views... [INFO@2023-10-03T02:05:08.196+00:00] Refreshing Materialized Daily Reading Views [INFO@2023-10-03T02:05:08.197+00:00] Refreshing Materialized Hourly Reading Views [INFO@2023-10-03T02:05:14.231+00:00] Daily View Refreshed [INFO@2023-10-03T02:05:19.900+00:00] Materialized Hourly View Refreshed [INFO@2023-10-03T02:05:19.902+00:00] ...Views Refreshed! If you don&#39;t want to refresh the readings (then cannot graph the new data but useful if shifting lots of meters until the last one) then add a third parameter of false: node -e &#39;require(&quot;./src/server/util/developer.js&quot;).shiftReadings(&quot;meter name&quot;, &quot;CDT&quot;, false)&#39; You need to refresh the web page with OED to see the new compare values of shifted data. This process can be repeated as often as desired to keep the readings current. If you give an incorrect meter name that does not exist then an error similar to the following will appear: [ERROR@2023-10-02T22:56:40.591+00:00] Unhandled Promise Rejection: TypeError: Cannot read properties of null (reading &#39;humanize&#39;) Stacktrace: TypeError: Cannot read properties of null (reading &#39;humanize&#39;) at Object.shiftReadings (/usr/src/app/src/server/util/developer.js:36:71) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) (node:288) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1) (Use `node --trace-warnings ...` to show where the warning was created) The following figure shows the result after shifting the three amp meters to current time and then doing a comparison graphic for 1 week. There is no difference between the meters since they all have the same shape and only scaling of the readings. Map data The following assumes you have loaded the test data into your development OED system. You can use other meter data if you prefer. Please use the admin map creating documentation for information on how to load and calibrate a map. This page only describes the necessary details of the test map. You need to be logged in as an admin to complete these steps. Use the sample Happy Place map by downloading it. This is the map you upload into OED. We will call it &quot;Happy Place&quot; and you can use that name in OED or some other name. The map angle is 0.0 degrees. During the calibration step, you will use a mythical GPS coordinate system of (0-30, 0-50) which are real GPS values but not usual for a map. This large area works because we will make a perfect calibration with no error. This means the lower, left corner of the map has GPS coordinate (0, 0) and the top, right has GPS coordinate (50, 30). The Plotly grid has values of (0, 0) for lower, left and (300, 500) for the top, right. This means the coordinates are reversed for GPS (latitude, longitude) compared to the grid (x, y) and are a factor of 10 smaller. During calibration, click on three places on the map. In principle it does not matter where but three spread out places on the map is better normally. When you do that, OED will show the grid coordinate you clicked on. As just explained, you need to reverse the coordinates and divide by 10. Thus, if you are told &quot;input GPS coordinate that corresponds to the point: x: 277, y: 461 in this format -&gt; latitude,longitude&quot; then you enter &quot;46.1, 27.7&quot; for the GPS value in the box and submit. Repeat this 3 times and you should then see an error of 0% for both directions. If not, start over. If yes, then save changes to the database. The following meters and groups will automatically be placed at these locations: Sin Amp 1 kWh at Play Place Sin Amp 2 kWh at Swimming Pool Sin Amp 1 kWh at Theater Sin Amp 1 + 2 kWh (group) at Cafeteria Sin Amp 2 + 3 kWh (group) at Housing If all went well, you should now see the following on the map page. Rotated map Sometimes you want to test a rotated map. In this case use Happy Place 30 Deg map that was rotated by 30 degrees. This does not impact the GPS coordinates but means the simple correspondence between the OED grid and GPS no longer holds. During calibration, use these points: Bottom, right of Swimming Pool at coordinate 265, 342 with GPS value of 39.5, 27.7 Bottom, right of Theater at coordinate 217, 234 with GPS value of 23.7, 29.3 Bottom, right of Cafeteria at coordinate 85, 252, with GPS value of 17.0, 12.7 This will give: result: x: 3.127%, y: 0.647%. If you switch to this map then you should see the following Where items are shown at the same location but the map is rotated. Simple Test Data Meter data The simple/basic test data is not representative of real meter data nor mathematical but it is easy to use. Each meter has readings for five days and the line graphs should be a straight line. The following table gives the expected values for the line graphs for all units for these simple meters where NA indicates that unit is not allowed/not compatible. The item for each meter/row that is marked with a * indicates the default graphic unit if one is not already selected. All values are for per hour for the rate. Note kW and kWh are not impacted by a rate change. The Gallon and Gallon flow are available for testing the rate choices. The table also contains the mathematical test data in the lower part. Meter name Dates Notes kWh BTU MJ M3 Gas 100 W bulb US Dollar Euro kg Metric ton kg of CO2 Metric ton of CO2 Fahrenheit Celsius kW Gallon Liter Gallon per minute Liter per hour Electric Utility kWh 6/1-5/2021 graphs as raw meter data 1 - 5* 3412.08 - 17060.4 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh not displayable 6/1-5/2021 graphs as raw meter data; only if admin 1 - 5* 3412.08 - 17060.4 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh 2-6 6/1-5/2021 graphs as meter data 2 - 6* 6824.16 - 20472.48 7.2 - 21.6 0.186 - 0.559 2 - 6 0.23 - 0.69 0.2 - 0.6 NA NA 1.418 - 4.254 1.418e-3 - 4.254e-3 NA NA NA NA NA NA NA Electric Utility kWh in BTU 6/1-5/2021 graphs as meter data 1 - 5 3412.08 - 17060.4* 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh in MTon CO2 6/1-5/2021 graphs as meter data 1 - 5 3412.08 - 17060.4* 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3* NA NA NA NA NA NA NA Natural Gas BTU 6/1-5/2021 graphs as meter data 2.93e-4 - 1.465e-3 1 - 5* 1.06e-3 - 5.27e-3 2.73e-5 - 1.36e-4 2.93e-4 - 1.465e-3 2.95e-6 - 1.48e-5 2.6e-6 - 1.3e-5 NA NA 5.28e-5 - 2.64e-4 5.28e-8 - 2.64e-7 NA NA NA NA NA NA NA Natural Gas BTU in Dollar 6/1-5/2021 graphs as meter data 2.93e-4 - 1.465e-3 1 - 5 1.06e-3 - 5.27e-3 2.73e-5 - 1.36e-4 2.93e-4 - 1.465e-3 2.95e-6 - 1.48e-5* 2.6e-6 - 1.3e-5 NA NA 5.28e-5 - 2.64e-4 5.28e-8 - 2.64e-7 NA NA NA NA NA NA NA Natural Gas Dollar 6/1-5/2021 graphs as meter data NA NA NA NA NA 1 - 5* 0.88-4.4 NA NA NA NA NA NA NA NA NA NA NA Natural Gas Cubic Meters 6/1-5/2021 graphs as meter data 10.7 - 53.4 3.64e4 - 1.82e5 38.5 - 192.3 1 - 5* 10.7 - 53.4 0.11 - 0.55 0.97 - 4.84 NA NA NA NA NA NA NA NA NA NA NA Trash Kg 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA 1 - 5* 1e-3 - 5e-3 NA NA NA NA NA NA NA NA NA Temp Fahrenheit 0-212 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA 0 - 212* -17.78 - 100 NA NA NA NA NA Temp Fahrenheit in Celsius 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA 0 - 212 -17.78 - 100* NA NA NA NA NA Electric kW 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA 1 - 5* NA NA NA NA Electric kW 2-6 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA 2 - 6* NA NA NA NA Water Gallon 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA NA 1-5* 3.79-18.93 NA NA Water Gallon flow 1-5 per minute 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA 1-5* 227.12-1135.6 Sin 4 Day kWh 2020 graphs as 4 day/raw meter 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 4 Hour kWh 2020 graphs daily but not less than 4 hour/raw if zoomed 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 15 Min kWh 2020 graphs daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 23 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 15 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin Amp 1 kWh 2020-21 graphs as daily 0 - 1 sine* 0 - ~3402 0 - ~3.6 0 - ~0.093 0 - 1 0 - ~0.115 0 - ~0.101 NA NA 0 - ~0.708 0 - 7.08e-4 NA NA NA NA NA NA NA Sin Amp 2 kWh 2020-21 graphs as daily 0 - 2 sine* 0 - ~6804 0 - ~7.2 0 - ~0.18 0 - 2 0 - ~0.23 0 - ~0.202 NA NA 0 - ~1.42 0 - 1.42e-4 NA NA NA NA NA NA NA Sin Amp 3 kWh 2020-21 graphs as daily 0 - 3 sine* 0 - ~10206 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.345 0 - ~0.303 NA NA 0 - ~2.12 0 - 2.12-3 NA NA NA NA NA NA NA Sin Sq kWh 2020 graphs as daily 0 - 2.5 sine* 0 - ~8520 0 - ~9.0 0 - ~0.23 0 - 2.5 0 - ~0.29 0 - ~0.252 NA NA 0 - ~1.77 0 - 1.77-3 NA NA NA NA NA NA NA Cos Sq kWh 2020 graphs as daily 0 - 2.5 sine* 0 - ~8520 0 - ~9.0 0 - ~0.23 0 - 2.5 0 - ~0.29 0 - ~0.252 NA NA 0 - ~1.77 0 - 1.77-3 NA NA NA NA NA NA NA Cos 23 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA For bar graphs, you can easily check the day bars for the simple data. Wider bars will only show for data with more days as OED does not show bars with days missing at the start or end. The value can be found by taking the day value on the line graph (shown in the table above) and multiplying by 24. For example, Electric Utility kWh as kWh has line values of 1-5 and bar values of 24-120. In US Dollars it is 0.115 - 0.575 on line and 2.76-13.8 on bar. Tis is because it is 24 times larger as the sum over the 24 hours of the rate/day. This holds for both quantity and flow units. If the custom slider is used and the bar width is 2 days then you get two bars: June 2-3 and Jun 4-5. The value is 120 (48 + 72) and 216 (96 + 120). Group data The following table gives groups that are created from the meters above as well as the mathematical meter data described below. All area units are sq. meters and not set/zero if left off. Group name Default graphic unit Values for default unit area Included meters Included groups All meters included Compatible units Note Electric Utility 1-5 + 2-6 kWh kWh 3 - 11 10 Electric Utility kWh, Electric Utility kWh 2-6 none Electric Utility kWh, Electric Utility kWh 2-6 see Electric Utility kWh Electric Utility 1-5 + 2-6 Dollar US Dollar 0.345 - 1.265 10 Electric Utility kWh, Electric Utility kWh 2-6 none Electric Utility kWh, Electric Utility kWh 2-6 see Electric Utility kWh Natural Gas Dollar Euro Euro 0.88 - 4.4 Natural Gas Dollar none Natural Gas Dollar see Natural Gas Dollar Electric Utility 1-5 + Natural Gas Dollar Euro Euro 0.9812 - 4.906 Electric Utility kWh, Natural Gas Dollar none Electric Utility kWh, Natural Gas Dollar see Natural Gas Dollar Electric Utility 1-5 kWh not displayable kWh 1 - 5 Electric Utility kWh none Electric Utility kWh see Electric Utility kWh This should only been seen and graphable by an admin Electric kW + 2-6 kW kW 3 - 11 100 Electric kW, Electric kW 2-6 none Electric kW, Electric kW 2-6 see Electric Utility kWh SqSin + SqCos kWh kWh very close to 2.5 10 testSqSin kWh, testSqCos kWh none testSqSin kWh, testSqCos kWh see Electric Utility kWh SqSin + SqCos no unit none same as above testSqSin kWh, testSqCos kWh none testSqSin kWh, testSqCos kWh see Electric Utility kWh Will graph once a unit compatible with kWh is chosen Sin Amp 1 + 2 kWh kWh sine from 0-3 1000 Sin Amp 1 kWh, Sin Amp 2 kWh none Sin Amp 1 kWh, Sin Amp 2 kWh see Electric Utility kWh Sin Amp 2 + 3 kWh kWh sine from 0-5 1000 Sin Amp 2 kWh, Sin Amp 3 kWh none Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh Sin Amp 1 + (2 - 3) kWh kWh sine from 0-6 10000 Sin Amp 1 kWh Sin Amp 2 + 3 kWh Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh includes group Amp 1 + 2 + (1 + 2) + (2 -3) kWh kWh sine from 0-6 10000 Sin Amp 1 kWh, Sin Amp 2 kWh Sin Amp 1 + 2 kWh, Sin Amp 2 + 3 kWh Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh includes 2 groups and 2 duplicate meters Mathematical Test Data The OED test data generation code can generate sine and cosine based data. It has several advantages: You can create on your own machine without needing to download anything. The provided script will generate the data and load it into your OED database for use within the system. Since it has a regular pattern, it is often easy to see issues in graphed data. Different datasets can be used to focus on different types of testing. Note that the values are shifted so the minimum is 0 since most meter data is like that. It is easy to use this data by following these steps The following table gives a list of the available data and information about it. The meter name assumes you use the provided script to load the data. (If you want to generate the test data outside the usual script, the &amp;ltcommand name&amp;gt is what you use to create this dataset manually with npm run &amp;ltcommand name&amp;gt in a web/vsc Docker container terminal. You will then need to load the reading data into OED as described on the reading import page. The file will have the name indicated and is located in the src/server/test/db/data/automatedTests/ directory. It is important to properly set the reading frequency to see the expect result.) The meter name is the one if the testData script is used to create and load this data. Description Meter name # points/file size &amp;ltcommand name&amp;gt File produced Sine function with a period of 45 days and amplitude 3 for 1 year with points every 4 days Sin 4 Day kWh 92 points/5kB generateFourDayTestingData fourDayFreqTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 4 hours Sin 4 Hour kWh 2196 points/129kB generateFourHourTestingData fourHourFreqTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 23 minutes Sin 23 Min kWh 22915 points/1.4MB generateTwentyThreeMinuteTestingData twentyThreeMinuteFreqTestData.csv. Sine function with a period of 45 days and amplitude 3 for 1 year with points every 15 minutes Sin 15 Min kWh 35136 points/2.1MB generateFifteenMinuteTestingData fifteenMinuteFreqTestData.csv Cosine function with a period of 45 days and amplitude 3 for 1 year with points every 23 minutes Cos 23 Min kWh 22915 points/1.4MB generateCosineTestingData 23FreqCosineTestData.csv Sine squared function with a period of 45 days and amplitude 2.5 for 1 year with points every 1 day Sin Sq kWh 366 points/21kB generateSineSquaredTestingData 2.5AmpSineSquaredTestData.csv Cosine squared function with a period of 45 days and amplitude 2.5 for 1 year with points every 1 day Cos Sq kWh 366 points/21kB generateCosineSquaredTestingData 2.5AmpCosineSquaredTestData.csv Sine function with a period of 45 days and amplitudes 1-3 for 2 years with points every 15 minutes Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh 70176 points/4.2MB each; 12.6MB total generateVariableAmplitudeTestingData 15Freq1AmpSineTestData.csv, 15Freq2AmpSineTestData.csv, 15Freq3AmpSineTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 1 minute. This is normally used for specialized testing of a large number of readings and not automatically generated by the script. Sin 1 Min 527040 points/32MB generateOneMinuteTestingData oneMinuteFreqTestData.csv What OED should display with this test data This section gives a range of samples of what OED will display when graphing the test data described above. Simple data Quantity data The following figure shows the kWh meters and groups as a line graph: The following figure shows the kWh meters and groups as a 1 day bar graph: OED will show a blank bar graphic in this case (and all the 5 day meters) for 1 or 4 weeks because it will not display bars with incomplete meter data at the start or end. Same as the line graphic above but in kg of CO2 to show changing the unit: Same as above but as a 1 day bar graph: The following figure shows the water meter as a line graph where the rate is Day to show changing the rate and a different type of unit. Note KWh must be shown per hour. Flow data The following figure shows the kW meters and groups as a line graph: The following figure shows the kW meters and groups as a 1 day bar graph: The following figure shows the water flow meter as a line graph where the rate is Minute to show changing the rate and a different type of unit. Note kW must be shown per hour. Raw data The following figure shows a temperature meter that collects in Fahrenheit but has a default graphic unit of Celsius as a line graph: Mathematical data The following picture shows the meters Sin 4 Day kWh, Sin 4 Hour kWh, Sin 23 Min kWh, Sin 15 Min kWh. It is designed to show how the number of points impact the line quality in OED and verify that varied reading rates do not impact the OED code. What you see is that the 4 day line is shifted due to the placement of the time values. The other meters are very similar in value. This shows that the daily averaging in OED is accurate. Note that in this and all line graphics, you will see the similar values as you zoom in to see hourly or meter level points. This is because the data is kW. The only change you will see is in the quality of the graphic if you zoom in so tight that you have limited points to graph. The following picture shows the same meters as above but as a bar graph with 4 week bars. In a perfect world, all the bars would have the same value for a given date range. As can be seen, there are small differences where the value varies more as the frequency of the readings goes down. This variation is due to the inaccuracy of low frequency readings as is normal. The following picture shows a line graphic of the sin values for the 3 different amplitudes (1-3). As expected, they have the same period with a different amplitude. Plus, it looks nice! The following picture shows a line graphic of a group containing all the sine amplitudes above but with 1 &amp; 2 included twice. OED does not duplicate the values so the sum is a maximum of 6 or 1 + 2 + 3. The following picture shows a sin and cos with the same amplitude. It should be noted that normally sin and cos are phase shifted so the high of one is the low of the other. You do not see that because the values were shifted to all be positive. The following picture shows the meters Sin Sq kWh &amp; Cos Sq kWh along with a group containing both meters (Sin Sq + Cos Sq kWh). If OED is working properly then the group should have a constant value since sin^2 + cos^1 = 1 or the value of the amplitude in this case. This is a good test of whether groups work (for simple groups of only two meters). If you want to see how accurate OED is then just graph this group and you will see that the value is always very close to 2.5. The following image shows sin with readings every minute. It is a very high quality version of the first picture with points that are less frequent. It is zoomed in to less than a day to show the minute points. This data is not automatically generated and is normally only used to test OED&#39;s speed when there is lots of reading points. You would need to generate this data (placed in src/server/test/db/data/automatedTests/oneMinuteFreqTestData.csv) and then upload via CSV as described for the real-world data. Real World Test Data This data can show what happens with actual data. However, it is harder to see when things are off. It is provided as an alternative to the mathematical data but will probably be used less now that that data exists. The table below lists the types of test data we have. The first four all have 3.5 years of electric data but for different meters so the values vary. The last one is a sample file that you can edit to create your own data. Description Readings CSV Size of Readings File Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearA.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearB.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearC.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearD.csv 1.3MB Sample file to edit for your own data sampleReadings.csv 0 MB Using the provided data Choose the file you want where clicking on the link in a web browser will download that file. Note you can load as many test data files as you want into a single OED instance. The import of this data into OED uses the CSV import feature that is described in the CSV import documentation and pages linked from that page, esp. about readings. You do not need to know all those details but can get further information as needed. Loading the data into your OED You will want to have OED running during this process. Start it with Docker as you should have previously done. Log in as an admin user. Go to the CSV upload page using the &quot;CSV&quot; button in the top, right of the OED web page. You should default to the &quot;Readings&quot; tab which is what you want. Now do the following: Enter the meter name in the box where the sample graph below used the file name without the extension and spaces, e.g., &quot;Three Year A&quot; for the first file. You can use any name you like. Use the &quot;Choose File&quot; button to select the file with the reading data you are uploading. Check the &quot;Create Meter&quot; and &quot;Header row&quot; boxes. Check the &quot;Refresh Readings&quot; and &quot;Refresh Hourly Readings&quot; boxes so the readings will be available right away for graphing. You can delay doing this until the last upload if you are doing multiple readings files to make it a little faster. If you forget to do this then you must manually refresh the readings to graph them. Click the &quot;Submit CSV Data&quot; button to start the upload. This will take a little while (probably less than one minute). A popup window will appear when the upload is done telling you the status. It should be SUCCESS without any warnings if all went well. If something went wrong then address the issue. Note if there are lots of errors then you need to look at the log or console where OED is running to see them all. Reload the web page where OED is running to see the new meter(s). Go to the meter page and assign the unit and, if desired, the default graphic unit for each meter. The examples make them Electric_Utility for the unit and kWh for the default graphic unit. Also set the reading frequency to 01:00:00 or 1 hour since that is what the data represents. You should now be able to graph them. Below is a line graphic with the four 3.5 year meters. If all went well then this is what you should see. If you don&#39;t see this then something is wrong and you should not continue this process and instead ask us for help. (See link at bottom of page) Creating own data You can download the sample data from the table above. You can edit the sampleReadings.csv file by opening it in you preferred editor where a spreadsheet program is fine as long as you make sure to save it as a CSV file. Remove the two sample readings on lines 2 and 3 of the file and create new lines with the data you want. Note that normally the end time of the previous point is equal to the start time of the next point in real meter data. You can put in as many lines as you want with readings. This file has a header row so it is easier to see what goes in each column. Once you are done editing and save the file in CSV format, import it the same way as the provided data above except you need to check the &quot;Header Row&quot; box since the file has a header row. Deal with any messages to correct problems and see the readings import page for more info on dealing with issues. Note if there are lots of errors then you need to look at the log or console where OED is running to see them all. Database issue If you cannot load the data into the database or it disappears after shutting down OED, then you likely have a database issue. To test you can do the following: Log in as the admin. Change the default graph type to something else (say bar) and save the change. Make sure it gives the green popup that it saved okay. Refresh the web browser and go tho the main OED page. It should have preselected the bar choice for graphic indicating that it is the default choice. If this does not work then verify the admin preference change was actually saved without error because it seems your installation is not saving to the database. Shut OED down and bring it back up. When OED is done installing, go to the web page and refresh the page. Again, you should see the bar as the default selection. If this fails then the database changes are not being saved between runs of OED. This indicates an install issue. If you don&#39;t know what to do then contact us. Help You should now be done and have the test data in your OED development system. If something did not work then you can seek help from the project by contacting us."><meta property="og:url" content="https://openenergydashboard.org/developer/testData/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Test Data</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Test Data</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>Developers want to have test meter data for OED development that is consistent, stable and does not require having access to actual meters. This describes how to get and load such meter test data along with related groups, units & conversions.<h2>Prerequisites</h2><p>What follows assumes you have a properly installed and working OED but have not yet loaded in the reading data described here. If they have already been loaded then the loading step for that meter will be skipped. At a minimum you should be able to see the main OED page in a web browser (normally URL of localhost:3000). Normally the database is automatically created and works fine. If you get errors about the database then you need to address them before you can do this or get the test data in (if you get errors during this process).<h2>Inserting the standard OED test data</h2><p>The simple and mathematical test data is created in OED by doing the following (they are described later):<ol><li>Make sure you have OED running so it is available to do the necessary work.<li>Open a terminal in the web/vsc Docker container by right clicking on the web container in the Docker extension of VSC and attaching a shell. (Described in the <a href="../gettingStarted/">getting started directions)</a><li>In the terminal, run the command <code>npm run testData</code>. This may take a few minutes but when it completes there should be new meters with data, new groups, the DB structures are all updated and the CSV files used will be removed unless there was an error. This generates all the standard test data except the one where readings are every minute since that is a large dataset that is less frequently used. See the next step before you can use the new OED information within the OED web page.<li>As we update OED pages, the code is avoiding reloading Redux state every time. Thus, to see all the changes in Redux state and to get the array for graphing units, you need to reload an existing OED web page. Once done you should see all the test meters/groups and data as described below. If this does not happen then an error likely occurred so carefully look at the output in your terminal that you used above.</ol><p>If you only want to load some of the data (not the common usage), you can look at package.json for the individual commands to insert the mathematical data. The others are so small/fast that they are done as above. See Mathematical test data section below.<h2>Comparison data</h2><p>When you do a compare graph, you choose how far from current time you compare. As a result, you need current readings and ones immediately before that time to get data for the comparison graph. If you are using meter data that does not have this, you will need to create it. Here is how to do it:<ol><li>Get the timezone of your local machine (not the Docker container for OED) by doing this in the terminal: <code>date +%Z</code>. For what follows the timezone is assumed to be CDT but you should change if your timezone differs.<li>If you want to be extra careful, check the time in Postgres. Open a Postgres terminal by attaching a shell to the database container in a similar way to how you did it above for the web container. Once inside the database shell, do: <code>psql -U oed</code> to access the database terminal and do the following within this terminal. Verify timezone is correct by doing: <code>select clock_timestamp() at time zone 'CDT';</code>. Make sure that it shows the same time as on the clock on your computer that you found in the previous step and replace CDT with the timezone using. You can now quit postgres by doing: <code>\q</code><li>Open a terminal by attaching a shell to the OED web container as was done earlier in this file.<li>In the web terminal do:<br> <code>node -e 'require("./src/server/util/developer.js").shiftReadings("meter name", "CDT")'</code><br> Where "meter name" is replaced with the meter you want to shift and still use the double quotes. Similarly, CDT should be the timezone found above. The console will show (the shift value will be different):<pre>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Test Data</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Developers want to have test meter data for OED development that is consistent, stable and does not require having access to actual meters. This describes how to get and load such meter test data along with related groups, units &amp; conversions. Prerequisites What follows assumes you have a properly installed and working OED but have not yet loaded in the reading data described here. If they have already been loaded then the loading step for that meter will be skipped. At a minimum you should be able to see the main OED page in a web browser (normally URL of localhost:3000). Normally the database is automatically created and works fine. If you get errors about the database then you need to address them before you can do this or get the test data in (if you get errors during this process). Inserting the standard OED test data The simple and mathematical test data is created in OED by doing the following (they are described later): Make sure you have OED running so it is available to do the necessary work. Open a terminal in the web/vsc Docker container by right clicking on the web container in the Docker extension of VSC and attaching a shell. (Described in the getting started directions) In the terminal, run the command npm run testData. This may take a few minutes but when it completes there should be new meters with data, new groups, the DB structures are all updated and the CSV files used will be removed unless there was an error. This generates all the standard test data except the one where readings are every minute since that is a large dataset that is less frequently used. See the next step before you can use the new OED information within the OED web page. As we update OED pages, the code is avoiding reloading Redux state every time. Thus, to see all the changes in Redux state and to get the array for graphing units, you need to reload an existing OED web page. Once done you should see all the test meters/groups and data as described below. If this does not happen then an error likely occurred so carefully look at the output in your terminal that you used above. If you only want to load some of the data (not the common usage), you can look at package.json for the individual commands to insert the mathematical data. The others are so small/fast that they are done as above. See Mathematical test data section below. Comparison data When you do a compare graph, you choose how far from current time you compare. As a result, you need current readings and ones immediately before that time to get data for the comparison graph. If you are using meter data that does not have this, you will need to create it. Here is how to do it: Get the timezone of your local machine (not the Docker container for OED) by doing this in the terminal: date +%Z. For what follows the timezone is assumed to be CDT but you should change if your timezone differs. If you want to be extra careful, check the time in Postgres. Open a Postgres terminal by attaching a shell to the database container in a similar way to how you did it above for the web container. Once inside the database shell, do: psql -U oed to access the database terminal and do the following within this terminal. Verify timezone is correct by doing: select clock_timestamp() at time zone &#39;CDT&#39;;. Make sure that it shows the same time as on the clock on your computer that you found in the previous step and replace CDT with the timezone using. You can now quit postgres by doing: \q Open a terminal by attaching a shell to the OED web container as was done earlier in this file. In the web terminal do: node -e &#39;require(&quot;./src/server/util/developer.js&quot;).shiftReadings(&quot;meter name&quot;, &quot;CDT&quot;)&#39; Where &quot;meter name&quot; is replaced with the meter you want to shift and still use the double quotes. Similarly, CDT should be the timezone found above. The console will show (the shift value will be different): shifting meter &quot;meter name&quot; to timezone &quot;CDT&quot; The readings were shifted by: 10 days refreshing all views since readings changed [INFO@2023-10-03T02:05:08.194+00:00] Refreshing All Reading Views... [INFO@2023-10-03T02:05:08.196+00:00] Refreshing Materialized Daily Reading Views [INFO@2023-10-03T02:05:08.197+00:00] Refreshing Materialized Hourly Reading Views [INFO@2023-10-03T02:05:14.231+00:00] Daily View Refreshed [INFO@2023-10-03T02:05:19.900+00:00] Materialized Hourly View Refreshed [INFO@2023-10-03T02:05:19.902+00:00] ...Views Refreshed! If you don&#39;t want to refresh the readings (then cannot graph the new data but useful if shifting lots of meters until the last one) then add a third parameter of false: node -e &#39;require(&quot;./src/server/util/developer.js&quot;).shiftReadings(&quot;meter name&quot;, &quot;CDT&quot;, false)&#39; You need to refresh the web page with OED to see the new compare values of shifted data. This process can be repeated as often as desired to keep the readings current. If you give an incorrect meter name that does not exist then an error similar to the following will appear: [ERROR@2023-10-02T22:56:40.591+00:00] Unhandled Promise Rejection: TypeError: Cannot read properties of null (reading &#39;humanize&#39;) Stacktrace: TypeError: Cannot read properties of null (reading &#39;humanize&#39;) at Object.shiftReadings (/usr/src/app/src/server/util/developer.js:36:71) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) (node:288) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1) (Use `node --trace-warnings ...` to show where the warning was created) The following figure shows the result after shifting the three amp meters to current time and then doing a comparison graphic for 1 week. There is no difference between the meters since they all have the same shape and only scaling of the readings. Map data The following assumes you have loaded the test data into your development OED system. You can use other meter data if you prefer. Please use the admin map creating documentation for information on how to load and calibrate a map. This page only describes the necessary details of the test map. You need to be logged in as an admin to complete these steps. Use the sample Happy Place map by downloading it. This is the map you upload into OED. We will call it &quot;Happy Place&quot; and you can use that name in OED or some other name. The map angle is 0.0 degrees. During the calibration step, you will use a mythical GPS coordinate system of (0-30, 0-50) which are real GPS values but not usual for a map. This large area works because we will make a perfect calibration with no error. This means the lower, left corner of the map has GPS coordinate (0, 0) and the top, right has GPS coordinate (50, 30). The Plotly grid has values of (0, 0) for lower, left and (300, 500) for the top, right. This means the coordinates are reversed for GPS (latitude, longitude) compared to the grid (x, y) and are a factor of 10 smaller. During calibration, click on three places on the map. In principle it does not matter where but three spread out places on the map is better normally. When you do that, OED will show the grid coordinate you clicked on. As just explained, you need to reverse the coordinates and divide by 10. Thus, if you are told &quot;input GPS coordinate that corresponds to the point: x: 277, y: 461 in this format -&gt; latitude,longitude&quot; then you enter &quot;46.1, 27.7&quot; for the GPS value in the box and submit. Repeat this 3 times and you should then see an error of 0% for both directions. If not, start over. If yes, then save changes to the database. The following meters and groups will automatically be placed at these locations: Sin Amp 1 kWh at Play Place Sin Amp 2 kWh at Swimming Pool Sin Amp 1 kWh at Theater Sin Amp 1 + 2 kWh (group) at Cafeteria Sin Amp 2 + 3 kWh (group) at Housing If all went well, you should now see the following on the map page. Rotated map Sometimes you want to test a rotated map. In this case use Happy Place 30 Deg map that was rotated by 30 degrees. This does not impact the GPS coordinates but means the simple correspondence between the OED grid and GPS no longer holds. During calibration, use these points: Bottom, right of Swimming Pool at coordinate 265, 342 with GPS value of 39.5, 27.7 Bottom, right of Theater at coordinate 217, 234 with GPS value of 23.7, 29.3 Bottom, right of Cafeteria at coordinate 85, 252, with GPS value of 17.0, 12.7 This will give: result: x: 3.127%, y: 0.647%. If you switch to this map then you should see the following Where items are shown at the same location but the map is rotated. Simple Test Data Meter data The simple/basic test data is not representative of real meter data nor mathematical but it is easy to use. Each meter has readings for five days and the line graphs should be a straight line. The following table gives the expected values for the line graphs for all units for these simple meters where NA indicates that unit is not allowed/not compatible. The item for each meter/row that is marked with a * indicates the default graphic unit if one is not already selected. All values are for per hour for the rate. Note kW and kWh are not impacted by a rate change. The Gallon and Gallon flow are available for testing the rate choices. The table also contains the mathematical test data in the lower part. Meter name Dates Notes kWh BTU MJ M3 Gas 100 W bulb US Dollar Euro kg Metric ton kg of CO2 Metric ton of CO2 Fahrenheit Celsius kW Gallon Liter Gallon per minute Liter per hour Electric Utility kWh 6/1-5/2021 graphs as raw meter data 1 - 5* 3412.08 - 17060.4 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh not displayable 6/1-5/2021 graphs as raw meter data; only if admin 1 - 5* 3412.08 - 17060.4 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh 2-6 6/1-5/2021 graphs as meter data 2 - 6* 6824.16 - 20472.48 7.2 - 21.6 0.186 - 0.559 2 - 6 0.23 - 0.69 0.2 - 0.6 NA NA 1.418 - 4.254 1.418e-3 - 4.254e-3 NA NA NA NA NA NA NA Electric Utility kWh in BTU 6/1-5/2021 graphs as meter data 1 - 5 3412.08 - 17060.4* 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh in MTon CO2 6/1-5/2021 graphs as meter data 1 - 5 3412.08 - 17060.4* 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3* NA NA NA NA NA NA NA Natural Gas BTU 6/1-5/2021 graphs as meter data 2.93e-4 - 1.465e-3 1 - 5* 1.06e-3 - 5.27e-3 2.73e-5 - 1.36e-4 2.93e-4 - 1.465e-3 2.95e-6 - 1.48e-5 2.6e-6 - 1.3e-5 NA NA 5.28e-5 - 2.64e-4 5.28e-8 - 2.64e-7 NA NA NA NA NA NA NA Natural Gas BTU in Dollar 6/1-5/2021 graphs as meter data 2.93e-4 - 1.465e-3 1 - 5 1.06e-3 - 5.27e-3 2.73e-5 - 1.36e-4 2.93e-4 - 1.465e-3 2.95e-6 - 1.48e-5* 2.6e-6 - 1.3e-5 NA NA 5.28e-5 - 2.64e-4 5.28e-8 - 2.64e-7 NA NA NA NA NA NA NA Natural Gas Dollar 6/1-5/2021 graphs as meter data NA NA NA NA NA 1 - 5* 0.88-4.4 NA NA NA NA NA NA NA NA NA NA NA Natural Gas Cubic Meters 6/1-5/2021 graphs as meter data 10.7 - 53.4 3.64e4 - 1.82e5 38.5 - 192.3 1 - 5* 10.7 - 53.4 0.11 - 0.55 0.97 - 4.84 NA NA NA NA NA NA NA NA NA NA NA Trash Kg 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA 1 - 5* 1e-3 - 5e-3 NA NA NA NA NA NA NA NA NA Temp Fahrenheit 0-212 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA 0 - 212* -17.78 - 100 NA NA NA NA NA Temp Fahrenheit in Celsius 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA 0 - 212 -17.78 - 100* NA NA NA NA NA Electric kW 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA 1 - 5* NA NA NA NA Electric kW 2-6 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA 2 - 6* NA NA NA NA Water Gallon 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA NA 1-5* 3.79-18.93 NA NA Water Gallon flow 1-5 per minute 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA 1-5* 227.12-1135.6 Sin 4 Day kWh 2020 graphs as 4 day/raw meter 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 4 Hour kWh 2020 graphs daily but not less than 4 hour/raw if zoomed 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 15 Min kWh 2020 graphs daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 23 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 15 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin Amp 1 kWh 2020-21 graphs as daily 0 - 1 sine* 0 - ~3402 0 - ~3.6 0 - ~0.093 0 - 1 0 - ~0.115 0 - ~0.101 NA NA 0 - ~0.708 0 - 7.08e-4 NA NA NA NA NA NA NA Sin Amp 2 kWh 2020-21 graphs as daily 0 - 2 sine* 0 - ~6804 0 - ~7.2 0 - ~0.18 0 - 2 0 - ~0.23 0 - ~0.202 NA NA 0 - ~1.42 0 - 1.42e-4 NA NA NA NA NA NA NA Sin Amp 3 kWh 2020-21 graphs as daily 0 - 3 sine* 0 - ~10206 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.345 0 - ~0.303 NA NA 0 - ~2.12 0 - 2.12-3 NA NA NA NA NA NA NA Sin Sq kWh 2020 graphs as daily 0 - 2.5 sine* 0 - ~8520 0 - ~9.0 0 - ~0.23 0 - 2.5 0 - ~0.29 0 - ~0.252 NA NA 0 - ~1.77 0 - 1.77-3 NA NA NA NA NA NA NA Cos Sq kWh 2020 graphs as daily 0 - 2.5 sine* 0 - ~8520 0 - ~9.0 0 - ~0.23 0 - 2.5 0 - ~0.29 0 - ~0.252 NA NA 0 - ~1.77 0 - 1.77-3 NA NA NA NA NA NA NA Cos 23 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA For bar graphs, you can easily check the day bars for the simple data. Wider bars will only show for data with more days as OED does not show bars with days missing at the start or end. The value can be found by taking the day value on the line graph (shown in the table above) and multiplying by 24. For example, Electric Utility kWh as kWh has line values of 1-5 and bar values of 24-120. In US Dollars it is 0.115 - 0.575 on line and 2.76-13.8 on bar. Tis is because it is 24 times larger as the sum over the 24 hours of the rate/day. This holds for both quantity and flow units. If the custom slider is used and the bar width is 2 days then you get two bars: June 2-3 and Jun 4-5. The value is 120 (48 + 72) and 216 (96 + 120). Group data The following table gives groups that are created from the meters above as well as the mathematical meter data described below. All area units are sq. meters and not set/zero if left off. Group name Default graphic unit Values for default unit area Included meters Included groups All meters included Compatible units Note Electric Utility 1-5 + 2-6 kWh kWh 3 - 11 10 Electric Utility kWh, Electric Utility kWh 2-6 none Electric Utility kWh, Electric Utility kWh 2-6 see Electric Utility kWh Electric Utility 1-5 + 2-6 Dollar US Dollar 0.345 - 1.265 10 Electric Utility kWh, Electric Utility kWh 2-6 none Electric Utility kWh, Electric Utility kWh 2-6 see Electric Utility kWh Natural Gas Dollar Euro Euro 0.88 - 4.4 Natural Gas Dollar none Natural Gas Dollar see Natural Gas Dollar Electric Utility 1-5 + Natural Gas Dollar Euro Euro 0.9812 - 4.906 Electric Utility kWh, Natural Gas Dollar none Electric Utility kWh, Natural Gas Dollar see Natural Gas Dollar Electric Utility 1-5 kWh not displayable kWh 1 - 5 Electric Utility kWh none Electric Utility kWh see Electric Utility kWh This should only been seen and graphable by an admin Electric kW + 2-6 kW kW 3 - 11 100 Electric kW, Electric kW 2-6 none Electric kW, Electric kW 2-6 see Electric Utility kWh SqSin + SqCos kWh kWh very close to 2.5 10 testSqSin kWh, testSqCos kWh none testSqSin kWh, testSqCos kWh see Electric Utility kWh SqSin + SqCos no unit none same as above testSqSin kWh, testSqCos kWh none testSqSin kWh, testSqCos kWh see Electric Utility kWh Will graph once a unit compatible with kWh is chosen Sin Amp 1 + 2 kWh kWh sine from 0-3 1000 Sin Amp 1 kWh, Sin Amp 2 kWh none Sin Amp 1 kWh, Sin Amp 2 kWh see Electric Utility kWh Sin Amp 2 + 3 kWh kWh sine from 0-5 1000 Sin Amp 2 kWh, Sin Amp 3 kWh none Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh Sin Amp 1 + (2 - 3) kWh kWh sine from 0-6 10000 Sin Amp 1 kWh Sin Amp 2 + 3 kWh Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh includes group Amp 1 + 2 + (1 + 2) + (2 -3) kWh kWh sine from 0-6 10000 Sin Amp 1 kWh, Sin Amp 2 kWh Sin Amp 1 + 2 kWh, Sin Amp 2 + 3 kWh Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh includes 2 groups and 2 duplicate meters Mathematical Test Data The OED test data generation code can generate sine and cosine based data. It has several advantages: You can create on your own machine without needing to download anything. The provided script will generate the data and load it into your OED database for use within the system. Since it has a regular pattern, it is often easy to see issues in graphed data. Different datasets can be used to focus on different types of testing. Note that the values are shifted so the minimum is 0 since most meter data is like that. It is easy to use this data by following these steps The following table gives a list of the available data and information about it. The meter name assumes you use the provided script to load the data. (If you want to generate the test data outside the usual script, the &amp;ltcommand name&amp;gt is what you use to create this dataset manually with npm run &amp;ltcommand name&amp;gt in a web/vsc Docker container terminal. You will then need to load the reading data into OED as described on the reading import page. The file will have the name indicated and is located in the src/server/test/db/data/automatedTests/ directory. It is important to properly set the reading frequency to see the expect result.) The meter name is the one if the testData script is used to create and load this data. Description Meter name # points/file size &amp;ltcommand name&amp;gt File produced Sine function with a period of 45 days and amplitude 3 for 1 year with points every 4 days Sin 4 Day kWh 92 points/5kB generateFourDayTestingData fourDayFreqTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 4 hours Sin 4 Hour kWh 2196 points/129kB generateFourHourTestingData fourHourFreqTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 23 minutes Sin 23 Min kWh 22915 points/1.4MB generateTwentyThreeMinuteTestingData twentyThreeMinuteFreqTestData.csv. Sine function with a period of 45 days and amplitude 3 for 1 year with points every 15 minutes Sin 15 Min kWh 35136 points/2.1MB generateFifteenMinuteTestingData fifteenMinuteFreqTestData.csv Cosine function with a period of 45 days and amplitude 3 for 1 year with points every 23 minutes Cos 23 Min kWh 22915 points/1.4MB generateCosineTestingData 23FreqCosineTestData.csv Sine squared function with a period of 45 days and amplitude 2.5 for 1 year with points every 1 day Sin Sq kWh 366 points/21kB generateSineSquaredTestingData 2.5AmpSineSquaredTestData.csv Cosine squared function with a period of 45 days and amplitude 2.5 for 1 year with points every 1 day Cos Sq kWh 366 points/21kB generateCosineSquaredTestingData 2.5AmpCosineSquaredTestData.csv Sine function with a period of 45 days and amplitudes 1-3 for 2 years with points every 15 minutes Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh 70176 points/4.2MB each; 12.6MB total generateVariableAmplitudeTestingData 15Freq1AmpSineTestData.csv, 15Freq2AmpSineTestData.csv, 15Freq3AmpSineTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 1 minute. This is normally used for specialized testing of a large number of readings and not automatically generated by the script. Sin 1 Min 527040 points/32MB generateOneMinuteTestingData oneMinuteFreqTestData.csv What OED should display with this test data This section gives a range of samples of what OED will display when graphing the test data described above. Simple data Quantity data The following figure shows the kWh meters and groups as a line graph: The following figure shows the kWh meters and groups as a 1 day bar graph: OED will show a blank bar graphic in this case (and all the 5 day meters) for 1 or 4 weeks because it will not display bars with incomplete meter data at the start or end. Same as the line graphic above but in kg of CO2 to show changing the unit: Same as above but as a 1 day bar graph: The following figure shows the water meter as a line graph where the rate is Day to show changing the rate and a different type of unit. Note KWh must be shown per hour. Flow data The following figure shows the kW meters and groups as a line graph: The following figure shows the kW meters and groups as a 1 day bar graph: The following figure shows the water flow meter as a line graph where the rate is Minute to show changing the rate and a different type of unit. Note kW must be shown per hour. Raw data The following figure shows a temperature meter that collects in Fahrenheit but has a default graphic unit of Celsius as a line graph: Mathematical data The following picture shows the meters Sin 4 Day kWh, Sin 4 Hour kWh, Sin 23 Min kWh, Sin 15 Min kWh. It is designed to show how the number of points impact the line quality in OED and verify that varied reading rates do not impact the OED code. What you see is that the 4 day line is shifted due to the placement of the time values. The other meters are very similar in value. This shows that the daily averaging in OED is accurate. Note that in this and all line graphics, you will see the similar values as you zoom in to see hourly or meter level points. This is because the data is kW. The only change you will see is in the quality of the graphic if you zoom in so tight that you have limited points to graph. The following picture shows the same meters as above but as a bar graph with 4 week bars. In a perfect world, all the bars would have the same value for a given date range. As can be seen, there are small differences where the value varies more as the frequency of the readings goes down. This variation is due to the inaccuracy of low frequency readings as is normal. The following picture shows a line graphic of the sin values for the 3 different amplitudes (1-3). As expected, they have the same period with a different amplitude. Plus, it looks nice! The following picture shows a line graphic of a group containing all the sine amplitudes above but with 1 &amp; 2 included twice. OED does not duplicate the values so the sum is a maximum of 6 or 1 + 2 + 3. The following picture shows a sin and cos with the same amplitude. It should be noted that normally sin and cos are phase shifted so the high of one is the low of the other. You do not see that because the values were shifted to all be positive. The following picture shows the meters Sin Sq kWh &amp; Cos Sq kWh along with a group containing both meters (Sin Sq + Cos Sq kWh). If OED is working properly then the group should have a constant value since sin^2 + cos^1 = 1 or the value of the amplitude in this case. This is a good test of whether groups work (for simple groups of only two meters). If you want to see how accurate OED is then just graph this group and you will see that the value is always very close to 2.5. The following image shows sin with readings every minute. It is a very high quality version of the first picture with points that are less frequent. It is zoomed in to less than a day to show the minute points. This data is not automatically generated and is normally only used to test OED&#39;s speed when there is lots of reading points. You would need to generate this data (placed in src/server/test/db/data/automatedTests/oneMinuteFreqTestData.csv) and then upload via CSV as described for the real-world data. Real World Test Data This data can show what happens with actual data. However, it is harder to see when things are off. It is provided as an alternative to the mathematical data but will probably be used less now that that data exists. The table below lists the types of test data we have. The first four all have 3.5 years of electric data but for different meters so the values vary. The last one is a sample file that you can edit to create your own data. Description Readings CSV Size of Readings File Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearA.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearB.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearC.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearD.csv 1.3MB Sample file to edit for your own data sampleReadings.csv 0 MB Using the provided data Choose the file you want where clicking on the link in a web browser will download that file. Note you can load as many test data files as you want into a single OED instance. The import of this data into OED uses the CSV import feature that is described in the CSV import documentation and pages linked from that page, esp. about readings. You do not need to know all those details but can get further information as needed. Loading the data into your OED You will want to have OED running during this process. Start it with Docker as you should have previously done. Log in as an admin user. Go to the CSV upload page using the &quot;CSV&quot; button in the top, right of the OED web page. You should default to the &quot;Readings&quot; tab which is what you want. Now do the following: Enter the meter name in the box where the sample graph below used the file name without the extension and spaces, e.g., &quot;Three Year A&quot; for the first file. You can use any name you like. Use the &quot;Choose File&quot; button to select the file with the reading data you are uploading. Check the &quot;Create Meter&quot; and &quot;Header row&quot; boxes. Check the &quot;Refresh Readings&quot; and &quot;Refresh Hourly Readings&quot; boxes so the readings will be available right away for graphing. You can delay doing this until the last upload if you are doing multiple readings files to make it a little faster. If you forget to do this then you must manually refresh the readings to graph them. Click the &quot;Submit CSV Data&quot; button to start the upload. This will take a little while (probably less than one minute). A popup window will appear when the upload is done telling you the status. It should be SUCCESS without any warnings if all went well. If something went wrong then address the issue. Note if there are lots of errors then you need to look at the log or console where OED is running to see them all. Reload the web page where OED is running to see the new meter(s). Go to the meter page and assign the unit and, if desired, the default graphic unit for each meter. The examples make them Electric_Utility for the unit and kWh for the default graphic unit. Also set the reading frequency to 01:00:00 or 1 hour since that is what the data represents. You should now be able to graph them. Below is a line graphic with the four 3.5 year meters. If all went well then this is what you should see. If you don&#39;t see this then something is wrong and you should not continue this process and instead ask us for help. (See link at bottom of page) Creating own data You can download the sample data from the table above. You can edit the sampleReadings.csv file by opening it in you preferred editor where a spreadsheet program is fine as long as you make sure to save it as a CSV file. Remove the two sample readings on lines 2 and 3 of the file and create new lines with the data you want. Note that normally the end time of the previous point is equal to the start time of the next point in real meter data. You can put in as many lines as you want with readings. This file has a header row so it is easier to see what goes in each column. Once you are done editing and save the file in CSV format, import it the same way as the provided data above except you need to check the &quot;Header Row&quot; box since the file has a header row. Deal with any messages to correct problems and see the readings import page for more info on dealing with issues. Note if there are lots of errors then you need to look at the log or console where OED is running to see them all. Database issue If you cannot load the data into the database or it disappears after shutting down OED, then you likely have a database issue. To test you can do the following: Log in as the admin. Change the default graph type to something else (say bar) and save the change. Make sure it gives the green popup that it saved okay. Refresh the web browser and go tho the main OED page. It should have preselected the bar choice for graphic indicating that it is the default choice. If this does not work then verify the admin preference change was actually saved without error because it seems your installation is not saving to the database. Shut OED down and bring it back up. When OED is done installing, go to the web page and refresh the page. Again, you should see the bar as the default selection. If this fails then the database changes are not being saved between runs of OED. This indicates an install issue. If you don&#39;t know what to do then contact us. Help You should now be done and have the test data in your OED development system. If something did not work then you can seek help from the project by contacting us."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/testData/"><meta property="og:title" content="Test Data"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Developers want to have test meter data for OED development that is consistent, stable and does not require having access to actual meters. This describes how to get and load such meter test data along with related groups, units &amp; conversions. Prerequisites What follows assumes you have a properly installed and working OED but have not yet loaded in the reading data described here. If they have already been loaded then the loading step for that meter will be skipped. At a minimum you should be able to see the main OED page in a web browser (normally URL of localhost:3000). Normally the database is automatically created and works fine. If you get errors about the database then you need to address them before you can do this or get the test data in (if you get errors during this process). Inserting the standard OED test data The simple and mathematical test data is created in OED by doing the following (they are described later): Make sure you have OED running so it is available to do the necessary work. Open a terminal in the web/vsc Docker container by right clicking on the web container in the Docker extension of VSC and attaching a shell. (Described in the getting started directions) In the terminal, run the command npm run testData. This may take a few minutes but when it completes there should be new meters with data, new groups, the DB structures are all updated and the CSV files used will be removed unless there was an error. This generates all the standard test data except the one where readings are every minute since that is a large dataset that is less frequently used. See the next step before you can use the new OED information within the OED web page. As we update OED pages, the code is avoiding reloading Redux state every time. Thus, to see all the changes in Redux state and to get the array for graphing units, you need to reload an existing OED web page. Once done you should see all the test meters/groups and data as described below. If this does not happen then an error likely occurred so carefully look at the output in your terminal that you used above. If you only want to load some of the data (not the common usage), you can look at package.json for the individual commands to insert the mathematical data. The others are so small/fast that they are done as above. See Mathematical test data section below. Comparison data When you do a compare graph, you choose how far from current time you compare. As a result, you need current readings and ones immediately before that time to get data for the comparison graph. If you are using meter data that does not have this, you will need to create it. Here is how to do it: Get the timezone of your local machine (not the Docker container for OED) by doing this in the terminal: date +%Z. For what follows the timezone is assumed to be CDT but you should change if your timezone differs. If you want to be extra careful, check the time in Postgres. Open a Postgres terminal by attaching a shell to the database container in a similar way to how you did it above for the web container. Once inside the database shell, do: psql -U oed to access the database terminal and do the following within this terminal. Verify timezone is correct by doing: select clock_timestamp() at time zone &#39;CDT&#39;;. Make sure that it shows the same time as on the clock on your computer that you found in the previous step and replace CDT with the timezone using. You can now quit postgres by doing: \q Open a terminal by attaching a shell to the OED web container as was done earlier in this file. In the web terminal do: node -e &#39;require(&quot;./src/server/util/developer.js&quot;).shiftReadings(&quot;meter name&quot;, &quot;CDT&quot;)&#39; Where &quot;meter name&quot; is replaced with the meter you want to shift and still use the double quotes. Similarly, CDT should be the timezone found above. The console will show (the shift value will be different): shifting meter &quot;meter name&quot; to timezone &quot;CDT&quot; The readings were shifted by: 10 days refreshing all views since readings changed [INFO@2023-10-03T02:05:08.194+00:00] Refreshing All Reading Views... [INFO@2023-10-03T02:05:08.196+00:00] Refreshing Materialized Daily Reading Views [INFO@2023-10-03T02:05:08.197+00:00] Refreshing Materialized Hourly Reading Views [INFO@2023-10-03T02:05:14.231+00:00] Daily View Refreshed [INFO@2023-10-03T02:05:19.900+00:00] Materialized Hourly View Refreshed [INFO@2023-10-03T02:05:19.902+00:00] ...Views Refreshed! If you don&#39;t want to refresh the readings (then cannot graph the new data but useful if shifting lots of meters until the last one) then add a third parameter of false: node -e &#39;require(&quot;./src/server/util/developer.js&quot;).shiftReadings(&quot;meter name&quot;, &quot;CDT&quot;, false)&#39; You need to refresh the web page with OED to see the new compare values of shifted data. This process can be repeated as often as desired to keep the readings current. If you give an incorrect meter name that does not exist then an error similar to the following will appear: [ERROR@2023-10-02T22:56:40.591+00:00] Unhandled Promise Rejection: TypeError: Cannot read properties of null (reading &#39;humanize&#39;) Stacktrace: TypeError: Cannot read properties of null (reading &#39;humanize&#39;) at Object.shiftReadings (/usr/src/app/src/server/util/developer.js:36:71) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) (node:288) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1) (Use `node --trace-warnings ...` to show where the warning was created) The following figure shows the result after shifting the three amp meters to current time and then doing a comparison graphic for 1 week. There is no difference between the meters since they all have the same shape and only scaling of the readings. Map data The following assumes you have loaded the test data into your development OED system. You can use other meter data if you prefer. Please use the admin map creating documentation for information on how to load and calibrate a map. This page only describes the necessary details of the test map. You need to be logged in as an admin to complete these steps. Use the sample Happy Place map by downloading it. This is the map you upload into OED. We will call it &quot;Happy Place&quot; and you can use that name in OED or some other name. The map angle is 0.0 degrees. During the calibration step, you will use a mythical GPS coordinate system of (0-30, 0-50) which are real GPS values but not usual for a map. This large area works because we will make a perfect calibration with no error. This means the lower, left corner of the map has GPS coordinate (0, 0) and the top, right has GPS coordinate (50, 30). The Plotly grid has values of (0, 0) for lower, left and (300, 500) for the top, right. This means the coordinates are reversed for GPS (latitude, longitude) compared to the grid (x, y) and are a factor of 10 smaller. During calibration, click on three places on the map. In principle it does not matter where but three spread out places on the map is better normally. When you do that, OED will show the grid coordinate you clicked on. As just explained, you need to reverse the coordinates and divide by 10. Thus, if you are told &quot;input GPS coordinate that corresponds to the point: x: 277, y: 461 in this format -&gt; latitude,longitude&quot; then you enter &quot;46.1, 27.7&quot; for the GPS value in the box and submit. Repeat this 3 times and you should then see an error of 0% for both directions. If not, start over. If yes, then save changes to the database. The following meters and groups will automatically be placed at these locations: Sin Amp 1 kWh at Play Place Sin Amp 2 kWh at Swimming Pool Sin Amp 1 kWh at Theater Sin Amp 1 + 2 kWh (group) at Cafeteria Sin Amp 2 + 3 kWh (group) at Housing If all went well, you should now see the following on the map page. Rotated map Sometimes you want to test a rotated map. In this case use Happy Place 30 Deg map that was rotated by 30 degrees. This does not impact the GPS coordinates but means the simple correspondence between the OED grid and GPS no longer holds. During calibration, use these points: Bottom, right of Swimming Pool at coordinate 265, 342 with GPS value of 39.5, 27.7 Bottom, right of Theater at coordinate 217, 234 with GPS value of 23.7, 29.3 Bottom, right of Cafeteria at coordinate 85, 252, with GPS value of 17.0, 12.7 This will give: result: x: 3.127%, y: 0.647%. If you switch to this map then you should see the following Where items are shown at the same location but the map is rotated. Simple Test Data Meter data The simple/basic test data is not representative of real meter data nor mathematical but it is easy to use. Each meter has readings for five days and the line graphs should be a straight line. The following table gives the expected values for the line graphs for all units for these simple meters where NA indicates that unit is not allowed/not compatible. The item for each meter/row that is marked with a * indicates the default graphic unit if one is not already selected. All values are for per hour for the rate. Note kW and kWh are not impacted by a rate change. The Gallon and Gallon flow are available for testing the rate choices. The table also contains the mathematical test data in the lower part. Meter name Dates Notes kWh BTU MJ M3 Gas 100 W bulb US Dollar Euro kg Metric ton kg of CO2 Metric ton of CO2 Fahrenheit Celsius kW Gallon Liter Gallon per minute Liter per hour Electric Utility kWh 6/1-5/2021 graphs as raw meter data 1 - 5* 3412.08 - 17060.4 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh not displayable 6/1-5/2021 graphs as raw meter data; only if admin 1 - 5* 3412.08 - 17060.4 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh 2-6 6/1-5/2021 graphs as meter data 2 - 6* 6824.16 - 20472.48 7.2 - 21.6 0.186 - 0.559 2 - 6 0.23 - 0.69 0.2 - 0.6 NA NA 1.418 - 4.254 1.418e-3 - 4.254e-3 NA NA NA NA NA NA NA Electric Utility kWh in BTU 6/1-5/2021 graphs as meter data 1 - 5 3412.08 - 17060.4* 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3 NA NA NA NA NA NA NA Electric Utility kWh in MTon CO2 6/1-5/2021 graphs as meter data 1 - 5 3412.08 - 17060.4* 3.6 - 18 9.32e-2 - 0.466 1-5 0.115 - 0.575 0.1012 - 0.506 NA NA 0.709 - 3.545 7.09e-4 - 3.545e-3* NA NA NA NA NA NA NA Natural Gas BTU 6/1-5/2021 graphs as meter data 2.93e-4 - 1.465e-3 1 - 5* 1.06e-3 - 5.27e-3 2.73e-5 - 1.36e-4 2.93e-4 - 1.465e-3 2.95e-6 - 1.48e-5 2.6e-6 - 1.3e-5 NA NA 5.28e-5 - 2.64e-4 5.28e-8 - 2.64e-7 NA NA NA NA NA NA NA Natural Gas BTU in Dollar 6/1-5/2021 graphs as meter data 2.93e-4 - 1.465e-3 1 - 5 1.06e-3 - 5.27e-3 2.73e-5 - 1.36e-4 2.93e-4 - 1.465e-3 2.95e-6 - 1.48e-5* 2.6e-6 - 1.3e-5 NA NA 5.28e-5 - 2.64e-4 5.28e-8 - 2.64e-7 NA NA NA NA NA NA NA Natural Gas Dollar 6/1-5/2021 graphs as meter data NA NA NA NA NA 1 - 5* 0.88-4.4 NA NA NA NA NA NA NA NA NA NA NA Natural Gas Cubic Meters 6/1-5/2021 graphs as meter data 10.7 - 53.4 3.64e4 - 1.82e5 38.5 - 192.3 1 - 5* 10.7 - 53.4 0.11 - 0.55 0.97 - 4.84 NA NA NA NA NA NA NA NA NA NA NA Trash Kg 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA 1 - 5* 1e-3 - 5e-3 NA NA NA NA NA NA NA NA NA Temp Fahrenheit 0-212 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA 0 - 212* -17.78 - 100 NA NA NA NA NA Temp Fahrenheit in Celsius 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA 0 - 212 -17.78 - 100* NA NA NA NA NA Electric kW 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA 1 - 5* NA NA NA NA Electric kW 2-6 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA 2 - 6* NA NA NA NA Water Gallon 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA NA 1-5* 3.79-18.93 NA NA Water Gallon flow 1-5 per minute 6/1-5/2021 graphs as meter data NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA 1-5* 227.12-1135.6 Sin 4 Day kWh 2020 graphs as 4 day/raw meter 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 4 Hour kWh 2020 graphs daily but not less than 4 hour/raw if zoomed 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 15 Min kWh 2020 graphs daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 23 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin 15 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA Sin Amp 1 kWh 2020-21 graphs as daily 0 - 1 sine* 0 - ~3402 0 - ~3.6 0 - ~0.093 0 - 1 0 - ~0.115 0 - ~0.101 NA NA 0 - ~0.708 0 - 7.08e-4 NA NA NA NA NA NA NA Sin Amp 2 kWh 2020-21 graphs as daily 0 - 2 sine* 0 - ~6804 0 - ~7.2 0 - ~0.18 0 - 2 0 - ~0.23 0 - ~0.202 NA NA 0 - ~1.42 0 - 1.42e-4 NA NA NA NA NA NA NA Sin Amp 3 kWh 2020-21 graphs as daily 0 - 3 sine* 0 - ~10206 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.345 0 - ~0.303 NA NA 0 - ~2.12 0 - 2.12-3 NA NA NA NA NA NA NA Sin Sq kWh 2020 graphs as daily 0 - 2.5 sine* 0 - ~8520 0 - ~9.0 0 - ~0.23 0 - 2.5 0 - ~0.29 0 - ~0.252 NA NA 0 - ~1.77 0 - 1.77-3 NA NA NA NA NA NA NA Cos Sq kWh 2020 graphs as daily 0 - 2.5 sine* 0 - ~8520 0 - ~9.0 0 - ~0.23 0 - 2.5 0 - ~0.29 0 - ~0.252 NA NA 0 - ~1.77 0 - 1.77-3 NA NA NA NA NA NA NA Cos 23 Min kWh 2020 graphs as daily 0 - 3 sine* 0 - ~10233 0 - ~10.8 0 - ~0.28 0 - 3 0 - ~0.35 0 - ~0.303 NA NA 0 - ~2.13 0 - 2.13e-3 NA NA NA NA NA NA NA For bar graphs, you can easily check the day bars for the simple data. Wider bars will only show for data with more days as OED does not show bars with days missing at the start or end. The value can be found by taking the day value on the line graph (shown in the table above) and multiplying by 24. For example, Electric Utility kWh as kWh has line values of 1-5 and bar values of 24-120. In US Dollars it is 0.115 - 0.575 on line and 2.76-13.8 on bar. Tis is because it is 24 times larger as the sum over the 24 hours of the rate/day. This holds for both quantity and flow units. If the custom slider is used and the bar width is 2 days then you get two bars: June 2-3 and Jun 4-5. The value is 120 (48 + 72) and 216 (96 + 120). Group data The following table gives groups that are created from the meters above as well as the mathematical meter data described below. All area units are sq. meters and not set/zero if left off. Group name Default graphic unit Values for default unit area Included meters Included groups All meters included Compatible units Note Electric Utility 1-5 + 2-6 kWh kWh 3 - 11 10 Electric Utility kWh, Electric Utility kWh 2-6 none Electric Utility kWh, Electric Utility kWh 2-6 see Electric Utility kWh Electric Utility 1-5 + 2-6 Dollar US Dollar 0.345 - 1.265 10 Electric Utility kWh, Electric Utility kWh 2-6 none Electric Utility kWh, Electric Utility kWh 2-6 see Electric Utility kWh Natural Gas Dollar Euro Euro 0.88 - 4.4 Natural Gas Dollar none Natural Gas Dollar see Natural Gas Dollar Electric Utility 1-5 + Natural Gas Dollar Euro Euro 0.9812 - 4.906 Electric Utility kWh, Natural Gas Dollar none Electric Utility kWh, Natural Gas Dollar see Natural Gas Dollar Electric Utility 1-5 kWh not displayable kWh 1 - 5 Electric Utility kWh none Electric Utility kWh see Electric Utility kWh This should only been seen and graphable by an admin Electric kW + 2-6 kW kW 3 - 11 100 Electric kW, Electric kW 2-6 none Electric kW, Electric kW 2-6 see Electric Utility kWh SqSin + SqCos kWh kWh very close to 2.5 10 testSqSin kWh, testSqCos kWh none testSqSin kWh, testSqCos kWh see Electric Utility kWh SqSin + SqCos no unit none same as above testSqSin kWh, testSqCos kWh none testSqSin kWh, testSqCos kWh see Electric Utility kWh Will graph once a unit compatible with kWh is chosen Sin Amp 1 + 2 kWh kWh sine from 0-3 1000 Sin Amp 1 kWh, Sin Amp 2 kWh none Sin Amp 1 kWh, Sin Amp 2 kWh see Electric Utility kWh Sin Amp 2 + 3 kWh kWh sine from 0-5 1000 Sin Amp 2 kWh, Sin Amp 3 kWh none Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh Sin Amp 1 + (2 - 3) kWh kWh sine from 0-6 10000 Sin Amp 1 kWh Sin Amp 2 + 3 kWh Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh includes group Amp 1 + 2 + (1 + 2) + (2 -3) kWh kWh sine from 0-6 10000 Sin Amp 1 kWh, Sin Amp 2 kWh Sin Amp 1 + 2 kWh, Sin Amp 2 + 3 kWh Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh see Electric Utility kWh includes 2 groups and 2 duplicate meters Mathematical Test Data The OED test data generation code can generate sine and cosine based data. It has several advantages: You can create on your own machine without needing to download anything. The provided script will generate the data and load it into your OED database for use within the system. Since it has a regular pattern, it is often easy to see issues in graphed data. Different datasets can be used to focus on different types of testing. Note that the values are shifted so the minimum is 0 since most meter data is like that. It is easy to use this data by following these steps The following table gives a list of the available data and information about it. The meter name assumes you use the provided script to load the data. (If you want to generate the test data outside the usual script, the &amp;ltcommand name&amp;gt is what you use to create this dataset manually with npm run &amp;ltcommand name&amp;gt in a web/vsc Docker container terminal. You will then need to load the reading data into OED as described on the reading import page. The file will have the name indicated and is located in the src/server/test/db/data/automatedTests/ directory. It is important to properly set the reading frequency to see the expect result.) The meter name is the one if the testData script is used to create and load this data. Description Meter name # points/file size &amp;ltcommand name&amp;gt File produced Sine function with a period of 45 days and amplitude 3 for 1 year with points every 4 days Sin 4 Day kWh 92 points/5kB generateFourDayTestingData fourDayFreqTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 4 hours Sin 4 Hour kWh 2196 points/129kB generateFourHourTestingData fourHourFreqTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 23 minutes Sin 23 Min kWh 22915 points/1.4MB generateTwentyThreeMinuteTestingData twentyThreeMinuteFreqTestData.csv. Sine function with a period of 45 days and amplitude 3 for 1 year with points every 15 minutes Sin 15 Min kWh 35136 points/2.1MB generateFifteenMinuteTestingData fifteenMinuteFreqTestData.csv Cosine function with a period of 45 days and amplitude 3 for 1 year with points every 23 minutes Cos 23 Min kWh 22915 points/1.4MB generateCosineTestingData 23FreqCosineTestData.csv Sine squared function with a period of 45 days and amplitude 2.5 for 1 year with points every 1 day Sin Sq kWh 366 points/21kB generateSineSquaredTestingData 2.5AmpSineSquaredTestData.csv Cosine squared function with a period of 45 days and amplitude 2.5 for 1 year with points every 1 day Cos Sq kWh 366 points/21kB generateCosineSquaredTestingData 2.5AmpCosineSquaredTestData.csv Sine function with a period of 45 days and amplitudes 1-3 for 2 years with points every 15 minutes Sin Amp 1 kWh, Sin Amp 2 kWh, Sin Amp 3 kWh 70176 points/4.2MB each; 12.6MB total generateVariableAmplitudeTestingData 15Freq1AmpSineTestData.csv, 15Freq2AmpSineTestData.csv, 15Freq3AmpSineTestData.csv Sine function with a period of 45 days and amplitude 3 for 1 year with points every 1 minute. This is normally used for specialized testing of a large number of readings and not automatically generated by the script. Sin 1 Min 527040 points/32MB generateOneMinuteTestingData oneMinuteFreqTestData.csv What OED should display with this test data This section gives a range of samples of what OED will display when graphing the test data described above. Simple data Quantity data The following figure shows the kWh meters and groups as a line graph: The following figure shows the kWh meters and groups as a 1 day bar graph: OED will show a blank bar graphic in this case (and all the 5 day meters) for 1 or 4 weeks because it will not display bars with incomplete meter data at the start or end. Same as the line graphic above but in kg of CO2 to show changing the unit: Same as above but as a 1 day bar graph: The following figure shows the water meter as a line graph where the rate is Day to show changing the rate and a different type of unit. Note KWh must be shown per hour. Flow data The following figure shows the kW meters and groups as a line graph: The following figure shows the kW meters and groups as a 1 day bar graph: The following figure shows the water flow meter as a line graph where the rate is Minute to show changing the rate and a different type of unit. Note kW must be shown per hour. Raw data The following figure shows a temperature meter that collects in Fahrenheit but has a default graphic unit of Celsius as a line graph: Mathematical data The following picture shows the meters Sin 4 Day kWh, Sin 4 Hour kWh, Sin 23 Min kWh, Sin 15 Min kWh. It is designed to show how the number of points impact the line quality in OED and verify that varied reading rates do not impact the OED code. What you see is that the 4 day line is shifted due to the placement of the time values. The other meters are very similar in value. This shows that the daily averaging in OED is accurate. Note that in this and all line graphics, you will see the similar values as you zoom in to see hourly or meter level points. This is because the data is kW. The only change you will see is in the quality of the graphic if you zoom in so tight that you have limited points to graph. The following picture shows the same meters as above but as a bar graph with 4 week bars. In a perfect world, all the bars would have the same value for a given date range. As can be seen, there are small differences where the value varies more as the frequency of the readings goes down. This variation is due to the inaccuracy of low frequency readings as is normal. The following picture shows a line graphic of the sin values for the 3 different amplitudes (1-3). As expected, they have the same period with a different amplitude. Plus, it looks nice! The following picture shows a line graphic of a group containing all the sine amplitudes above but with 1 &amp; 2 included twice. OED does not duplicate the values so the sum is a maximum of 6 or 1 + 2 + 3. The following picture shows a sin and cos with the same amplitude. It should be noted that normally sin and cos are phase shifted so the high of one is the low of the other. You do not see that because the values were shifted to all be positive. The following picture shows the meters Sin Sq kWh &amp; Cos Sq kWh along with a group containing both meters (Sin Sq + Cos Sq kWh). If OED is working properly then the group should have a constant value since sin^2 + cos^1 = 1 or the value of the amplitude in this case. This is a good test of whether groups work (for simple groups of only two meters). If you want to see how accurate OED is then just graph this group and you will see that the value is always very close to 2.5. The following image shows sin with readings every minute. It is a very high quality version of the first picture with points that are less frequent. It is zoomed in to less than a day to show the minute points. This data is not automatically generated and is normally only used to test OED&#39;s speed when there is lots of reading points. You would need to generate this data (placed in src/server/test/db/data/automatedTests/oneMinuteFreqTestData.csv) and then upload via CSV as described for the real-world data. Real World Test Data This data can show what happens with actual data. However, it is harder to see when things are off. It is provided as an alternative to the mathematical data but will probably be used less now that that data exists. The table below lists the types of test data we have. The first four all have 3.5 years of electric data but for different meters so the values vary. The last one is a sample file that you can edit to create your own data. Description Readings CSV Size of Readings File Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearA.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearB.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearC.csv 1.3MB Contains actual electric data on an hourly basis for about 3.5 years (Oct. 2016-Apr. 2020) threeYearD.csv 1.3MB Sample file to edit for your own data sampleReadings.csv 0 MB Using the provided data Choose the file you want where clicking on the link in a web browser will download that file. Note you can load as many test data files as you want into a single OED instance. The import of this data into OED uses the CSV import feature that is described in the CSV import documentation and pages linked from that page, esp. about readings. You do not need to know all those details but can get further information as needed. Loading the data into your OED You will want to have OED running during this process. Start it with Docker as you should have previously done. Log in as an admin user. Go to the CSV upload page using the &quot;CSV&quot; button in the top, right of the OED web page. You should default to the &quot;Readings&quot; tab which is what you want. Now do the following: Enter the meter name in the box where the sample graph below used the file name without the extension and spaces, e.g., &quot;Three Year A&quot; for the first file. You can use any name you like. Use the &quot;Choose File&quot; button to select the file with the reading data you are uploading. Check the &quot;Create Meter&quot; and &quot;Header row&quot; boxes. Check the &quot;Refresh Readings&quot; and &quot;Refresh Hourly Readings&quot; boxes so the readings will be available right away for graphing. You can delay doing this until the last upload if you are doing multiple readings files to make it a little faster. If you forget to do this then you must manually refresh the readings to graph them. Click the &quot;Submit CSV Data&quot; button to start the upload. This will take a little while (probably less than one minute). A popup window will appear when the upload is done telling you the status. It should be SUCCESS without any warnings if all went well. If something went wrong then address the issue. Note if there are lots of errors then you need to look at the log or console where OED is running to see them all. Reload the web page where OED is running to see the new meter(s). Go to the meter page and assign the unit and, if desired, the default graphic unit for each meter. The examples make them Electric_Utility for the unit and kWh for the default graphic unit. Also set the reading frequency to 01:00:00 or 1 hour since that is what the data represents. You should now be able to graph them. Below is a line graphic with the four 3.5 year meters. If all went well then this is what you should see. If you don&#39;t see this then something is wrong and you should not continue this process and instead ask us for help. (See link at bottom of page) Creating own data You can download the sample data from the table above. You can edit the sampleReadings.csv file by opening it in you preferred editor where a spreadsheet program is fine as long as you make sure to save it as a CSV file. Remove the two sample readings on lines 2 and 3 of the file and create new lines with the data you want. Note that normally the end time of the previous point is equal to the start time of the next point in real meter data. You can put in as many lines as you want with readings. This file has a header row so it is easier to see what goes in each column. Once you are done editing and save the file in CSV format, import it the same way as the provided data above except you need to check the &quot;Header Row&quot; box since the file has a header row. Deal with any messages to correct problems and see the readings import page for more info on dealing with issues. Note if there are lots of errors then you need to look at the log or console where OED is running to see them all. Database issue If you cannot load the data into the database or it disappears after shutting down OED, then you likely have a database issue. To test you can do the following: Log in as the admin. Change the default graph type to something else (say bar) and save the change. Make sure it gives the green popup that it saved okay. Refresh the web browser and go tho the main OED page. It should have preselected the bar choice for graphic indicating that it is the default choice. If this does not work then verify the admin preference change was actually saved without error because it seems your installation is not saving to the database. Shut OED down and bring it back up. When OED is done installing, go to the web page and refresh the page. Again, you should see the bar as the default selection. If this fails then the database changes are not being saved between runs of OED. This indicates an install issue. If you don&#39;t know what to do then contact us. Help You should now be done and have the test data in your OED development system. If something did not work then you can seek help from the project by contacting us."><meta property="og:url" content="https://openenergydashboard.org/developer/testData/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Test Data</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Test Data</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>Developers want to have test meter data for OED development that is consistent, stable and does not require having access to actual meters. This describes how to get and load such meter test data along with related groups, units & conversions.<h2>Prerequisites</h2><p>What follows assumes you have a properly installed and working OED but have not yet loaded in the reading data described here. If they have already been loaded then the loading step for that meter will be skipped. At a minimum you should be able to see the main OED page in a web browser (normally URL of localhost:3000). Normally the database is automatically created and works fine. If you get errors about the database then you need to address them before you can do this or get the test data in (if you get errors during this process).<h2>Inserting the standard OED test data</h2><p>The simple and mathematical test data is created in OED by doing the following (they are described later):<ol><li>Make sure you have OED running so it is available to do the necessary work.<li>Open a terminal in the web/vsc Docker container by right clicking on the web container in the Docker extension of VSC and attaching a shell. (Described in the <a href="../gettingStarted/">getting started directions)</a><li>In the terminal, run the command <code>npm run testData</code>. This may take a few minutes but when it completes there should be new meters with data, new groups, the DB structures are all updated and the CSV files used will be removed unless there was an error. This generates all the standard test data except the one where readings are every minute since that is a large dataset that is less frequently used. See the next step before you can use the new OED information within the OED web page.<li>As we update OED pages, the code is avoiding reloading Redux state every time. Thus, to see all the changes in Redux state and to get the array for graphing units, you need to reload an existing OED web page. Once done you should see all the test meters/groups and data as described below. If this does not happen then an error likely occurred so carefully look at the output in your terminal that you used above.</ol><p>If you only want to load some of the data (not the common usage), you can look at package.json for the individual commands to insert the mathematical data. The others are so small/fast that they are done as above. See Mathematical test data section below.<h2>Comparison data</h2><p>When you do a compare graph, you choose how far from current time you compare. As a result, you need current readings and ones immediately before that time to get data for the comparison graph. If you are using meter data that does not have this, you will need to create it. Here is how to do it:<ol><li>Get the timezone of your local machine (not the Docker container for OED) by doing this in the terminal: <code>date +%Z</code>. For what follows the timezone is assumed to be CDT but you should change if your timezone differs.<li>If you want to be extra careful, check the time in Postgres. Open a Postgres terminal by attaching a shell to the database container in a similar way to how you did it above for the web container. Once inside the database shell, do: <code>psql -U oed</code> to access the database terminal and do the following within this terminal. Verify timezone is correct by doing: <code>select clock_timestamp() at time zone 'CDT';</code>. Make sure that it shows the same time as on the clock on your computer that you found in the previous step and replace CDT with the timezone using. You can now quit postgres by doing: <code>\q</code><li>Open a terminal by attaching a shell to the OED web container as was done earlier in this file.<li>In the web terminal do:<br> <code>node -e 'require("./src/server/util/developer.js").shiftReadings("meter name", "CDT")'</code><br> Where "meter name" is replaced with the meter you want to shift and still use the double quotes. Similarly, CDT should be the timezone found above. The console will show (the shift value will be different):<pre>
 	shifting meter "meter name" to timezone "CDT"
 	The readings were shifted by:  10 days
 	refreshing all views since readings changed
diff --git a/developer/testing/index.html b/developer/testing/index.html
index a048528b..e5af5a6d 100644
--- a/developer/testing/index.html
+++ b/developer/testing/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Test Code</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED strives to have test code for all aspects of the project. At the current time we do not test the actual web pages. Thus, we don&#39;t automatically check that buttons click as expected or graphics show as expected. These tests are done manually. OED uses automated testing for functions, database query results, routes, etc. The automated testing mostly uses the Chai and Mocha frameworks. The test code is located in the src/server/test/ directory. Tests are grouped by functionality in database (db/ directory), routes (routes/ directory), etc. The main directory has common.js that is used across many tests. It has functions to set up the test database environment, reset the database and Mocha actions to take before/after tests and before each test is run. In general, the database is reset before any test that uses the database to guarantee a clean environment for each test. OED only uses a subset of the testing frameworks. Possibly the easiest way to learn how to add tests is to go to existing tests in OED that are similar to the one(s) you want to add. You can then either edit/add to an existing file (if you changed or added to an already existing feature) or create a new file (for new functionality) where you use an existing file as the template. Please make sure to run your test(s) to make sure they work. The developer details has information on running single tests. Some newer tests are outlined in the testing design document that describes how they are created, implemented and other details."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/testing/"><meta property="og:title" content="Test Code"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED strives to have test code for all aspects of the project. At the current time we do not test the actual web pages. Thus, we don&#39;t automatically check that buttons click as expected or graphics show as expected. These tests are done manually. OED uses automated testing for functions, database query results, routes, etc. The automated testing mostly uses the Chai and Mocha frameworks. The test code is located in the src/server/test/ directory. Tests are grouped by functionality in database (db/ directory), routes (routes/ directory), etc. The main directory has common.js that is used across many tests. It has functions to set up the test database environment, reset the database and Mocha actions to take before/after tests and before each test is run. In general, the database is reset before any test that uses the database to guarantee a clean environment for each test. OED only uses a subset of the testing frameworks. Possibly the easiest way to learn how to add tests is to go to existing tests in OED that are similar to the one(s) you want to add. You can then either edit/add to an existing file (if you changed or added to an already existing feature) or create a new file (for new functionality) where you use an existing file as the template. Please make sure to run your test(s) to make sure they work. The developer details has information on running single tests. Some newer tests are outlined in the testing design document that describes how they are created, implemented and other details."><meta property="og:url" content="https://openenergydashboard.org/developer/testing/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Test Code</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Test Code</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>OED strives to have test code for all aspects of the project. At the current time we do not test the actual web pages. Thus, we don't automatically check that buttons click as expected or graphics show as expected. These tests are done manually. OED uses automated testing for functions, database query results, routes, etc. The automated testing mostly uses the Chai and Mocha frameworks.<p>The test code is located in the <code>src/server/test/</code> directory. Tests are grouped by functionality in database (<code>db/</code> directory), routes (<code>routes/</code> directory), etc. The main directory has common.js that is used across many tests. It has functions to set up the test database environment, reset the database and Mocha actions to take before/after tests and before each test is run. In general, the database is reset before any test that uses the database to guarantee a clean environment for each test.<p>OED only uses a subset of the testing frameworks. Possibly the easiest way to learn how to add tests is to go to existing tests in OED that are similar to the one(s) you want to add. You can then either edit/add to an existing file (if you changed or added to an already existing feature) or create a new file (for new functionality) where you use an existing file as the template. Please make sure to run your test(s) to make sure they work. The <a href="../devDetails/#singleTest">developer details</a> has information on running single tests.<p>Some newer tests are outlined in the <a href="https://github.com/OpenEnergyDashboard/DesignDocs/blob/main/testing/testing.md">testing design document</a> that describes how they are created, implemented and other details.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Test Code</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED strives to have test code for all aspects of the project. At the current time we do not test the actual web pages. Thus, we don&#39;t automatically check that buttons click as expected or graphics show as expected. These tests are done manually. OED uses automated testing for functions, database query results, routes, etc. The automated testing mostly uses the Chai and Mocha frameworks. The test code is located in the src/server/test/ directory. Tests are grouped by functionality in database (db/ directory), routes (routes/ directory), etc. The main directory has common.js that is used across many tests. It has functions to set up the test database environment, reset the database and Mocha actions to take before/after tests and before each test is run. In general, the database is reset before any test that uses the database to guarantee a clean environment for each test. OED only uses a subset of the testing frameworks. Possibly the easiest way to learn how to add tests is to go to existing tests in OED that are similar to the one(s) you want to add. You can then either edit/add to an existing file (if you changed or added to an already existing feature) or create a new file (for new functionality) where you use an existing file as the template. Please make sure to run your test(s) to make sure they work. The developer details has information on running single tests. Some newer tests are outlined in the testing design document that describes how they are created, implemented and other details."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/testing/"><meta property="og:title" content="Test Code"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. OED strives to have test code for all aspects of the project. At the current time we do not test the actual web pages. Thus, we don&#39;t automatically check that buttons click as expected or graphics show as expected. These tests are done manually. OED uses automated testing for functions, database query results, routes, etc. The automated testing mostly uses the Chai and Mocha frameworks. The test code is located in the src/server/test/ directory. Tests are grouped by functionality in database (db/ directory), routes (routes/ directory), etc. The main directory has common.js that is used across many tests. It has functions to set up the test database environment, reset the database and Mocha actions to take before/after tests and before each test is run. In general, the database is reset before any test that uses the database to guarantee a clean environment for each test. OED only uses a subset of the testing frameworks. Possibly the easiest way to learn how to add tests is to go to existing tests in OED that are similar to the one(s) you want to add. You can then either edit/add to an existing file (if you changed or added to an already existing feature) or create a new file (for new functionality) where you use an existing file as the template. Please make sure to run your test(s) to make sure they work. The developer details has information on running single tests. Some newer tests are outlined in the testing design document that describes how they are created, implemented and other details."><meta property="og:url" content="https://openenergydashboard.org/developer/testing/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Test Code</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Test Code</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>OED strives to have test code for all aspects of the project. At the current time we do not test the actual web pages. Thus, we don't automatically check that buttons click as expected or graphics show as expected. These tests are done manually. OED uses automated testing for functions, database query results, routes, etc. The automated testing mostly uses the Chai and Mocha frameworks.<p>The test code is located in the <code>src/server/test/</code> directory. Tests are grouped by functionality in database (<code>db/</code> directory), routes (<code>routes/</code> directory), etc. The main directory has common.js that is used across many tests. It has functions to set up the test database environment, reset the database and Mocha actions to take before/after tests and before each test is run. In general, the database is reset before any test that uses the database to guarantee a clean environment for each test.<p>OED only uses a subset of the testing frameworks. Possibly the easiest way to learn how to add tests is to go to existing tests in OED that are similar to the one(s) you want to add. You can then either edit/add to an existing file (if you changed or added to an already existing feature) or create a new file (for new functionality) where you use an existing file as the template. Please make sure to run your test(s) to make sure they work. The <a href="../devDetails/#singleTest">developer details</a> has information on running single tests.<p>Some newer tests are outlined in the <a href="https://github.com/OpenEnergyDashboard/DesignDocs/blob/main/testing/testing.md">testing design document</a> that describes how they are created, implemented and other details.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/work/index.html b/developer/work/index.html
index 1eef34f4..4950dd5f 100644
--- a/developer/work/index.html
+++ b/developer/work/index.html
@@ -1 +1 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Work Selection</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. We understand that when you join OED it can be tricky to figure out what to work on. This can also be the case as you wind down some work and are looking for more. The best way is to reach out to our contact us using the developer topic or your OED mentor (if you have one) so we can be of assistance. We will help you find tasks that help the project and are aligned with your interests. What you should work on depends on your background and interests, knowledge of the project and our needs so there is no single answer for what is best that suits everyone. One useful place to look is the GitHub issues for OED. There you will find issues in many areas that are labeled in ways that may help you identify which to work on. If you are new to the project and want to start with easier tasks then ones labeled &quot;i-good-first-issue&quot; are good ones to consider. The priority (&quot;low&quot;, &quot;medium&quot; and &quot;high&quot;) also gives some idea of how important an item is to the project. Others indicate what area of the project an issue relates to. It is a good idea to see if a task is assigned to any developers. If it is, then it may be under active development or that person knows the status. You should reach out to that person or the project for more information before working on that task. For related reasons, you should make sure you are assigned a task you are working on so others are aware you are working on it. The project board (see below) should also be updated as needed. If you cannot do these due to permission issues then contact us using the developer topic to get the changes made. You can also look at OED GitHub milestones to see what items are associated with which release of OED. This is an indication of the time frame that the item needs to be completed. Note that a task that does not show up in the issues, etc. is documenting the code. There are parts that have insufficient comments and it is very valuable to the project to rectify that situation. It is also a way to engage with the code without having to make changes that impact how it runs. The design documents (and previously the projects boards) have an overview of major initiatives. It lets you know what work is in progress and what we hope to do next. This generally overlaps the issues but gives a broader picture and is more visual. The OED Discord channel for developers (and previously the discussion board) . Here you can see the status of development and thought that have come up on issues relating to OED. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group. If you see an item that refers to a developer document and you do not have access then please just request it."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/work/"><meta property="og:title" content="Work Selection"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. We understand that when you join OED it can be tricky to figure out what to work on. This can also be the case as you wind down some work and are looking for more. The best way is to reach out to our contact us using the developer topic or your OED mentor (if you have one) so we can be of assistance. We will help you find tasks that help the project and are aligned with your interests. What you should work on depends on your background and interests, knowledge of the project and our needs so there is no single answer for what is best that suits everyone. One useful place to look is the GitHub issues for OED. There you will find issues in many areas that are labeled in ways that may help you identify which to work on. If you are new to the project and want to start with easier tasks then ones labeled &quot;i-good-first-issue&quot; are good ones to consider. The priority (&quot;low&quot;, &quot;medium&quot; and &quot;high&quot;) also gives some idea of how important an item is to the project. Others indicate what area of the project an issue relates to. It is a good idea to see if a task is assigned to any developers. If it is, then it may be under active development or that person knows the status. You should reach out to that person or the project for more information before working on that task. For related reasons, you should make sure you are assigned a task you are working on so others are aware you are working on it. The project board (see below) should also be updated as needed. If you cannot do these due to permission issues then contact us using the developer topic to get the changes made. You can also look at OED GitHub milestones to see what items are associated with which release of OED. This is an indication of the time frame that the item needs to be completed. Note that a task that does not show up in the issues, etc. is documenting the code. There are parts that have insufficient comments and it is very valuable to the project to rectify that situation. It is also a way to engage with the code without having to make changes that impact how it runs. The design documents (and previously the projects boards) have an overview of major initiatives. It lets you know what work is in progress and what we hope to do next. This generally overlaps the issues but gives a broader picture and is more visual. The OED Discord channel for developers (and previously the discussion board) . Here you can see the status of development and thought that have come up on issues relating to OED. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group. If you see an item that refers to a developer document and you do not have access then please just request it."><meta property="og:url" content="https://openenergydashboard.org/developer/work/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Work Selection</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Work Selection</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>We understand that when you join OED it can be tricky to figure out what to work on. This can also be the case as you wind down some work and are looking for more. The best way is to reach out to our <a href="https://openenergydashboard.org/contact/">contact us using the developer topic</a> or your OED mentor (if you have one) so we can be of assistance. We will help you find tasks that help the project and are aligned with your interests.<p>What you should work on depends on your background and interests, knowledge of the project and our needs so there is no single answer for what is best that suits everyone. One useful place to look is the <a href="https://github.com/OpenEnergyDashboard/OED/issues" rel="noopener noreferrer">GitHub issues</a> for OED. There you will find issues in many areas that are labeled in ways that may help you identify which to work on. If you are new to the project and want to start with easier tasks then ones labeled "i-good-first-issue" are good ones to consider. The priority ("low", "medium" and "high") also gives some idea of how important an item is to the project. Others indicate what area of the project an issue relates to. It is a good idea to see if a task is assigned to any developers. If it is, then it may be under active development or that person knows the status. You should reach out to that person or the project for more information before working on that task. For related reasons, you should make sure you are assigned a task you are working on so others are aware you are working on it. The project board (see below) should also be updated as needed. If you cannot do these due to permission issues then <a href="https://openenergydashboard.org/contact/">contact us using the developer topic</a> to get the changes made. You can also look at <a href="https://github.com/OpenEnergyDashboard/OED/milestones" rel="noopener noreferrer">OED GitHub milestones</a> to see what items are associated with which release of OED. This is an indication of the time frame that the item needs to be completed. Note that a task that does not show up in the issues, etc. is documenting the code. There are parts that have insufficient comments and it is very valuable to the project to rectify that situation. It is also a way to engage with the code without having to make changes that impact how it runs.<p>The <a href="https://github.com/OpenEnergyDashboard/DesignDocs">design documents</a> (and previously the <a href="https://github.com/OpenEnergyDashboard/OED/projects?type=beta" rel="noopener noreferrer">projects boards</a>) have an overview of major initiatives. It lets you know what work is in progress and what we hope to do next. This generally overlaps the issues but gives a broader picture and is more visual.<p>The <a href="https://openenergydashboard.org/contact/">OED Discord channel</a> for developers (and previously the <a href="https://github.com/OpenEnergyDashboard/OED/discussions" rel="noopener noreferrer">discussion board</a>) . Here you can see the status of development and thought that have come up on issues relating to OED. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group.<p>If you see an item that refers to a developer document and you do not have access then please just request it.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Work Selection</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. We understand that when you join OED it can be tricky to figure out what to work on. This can also be the case as you wind down some work and are looking for more. The best way is to reach out to our contact us using the developer topic or your OED mentor (if you have one) so we can be of assistance. We will help you find tasks that help the project and are aligned with your interests. What you should work on depends on your background and interests, knowledge of the project and our needs so there is no single answer for what is best that suits everyone. One useful place to look is the GitHub issues for OED. There you will find issues in many areas that are labeled in ways that may help you identify which to work on. If you are new to the project and want to start with easier tasks then ones labeled &quot;i-good-first-issue&quot; are good ones to consider. The priority (&quot;low&quot;, &quot;medium&quot; and &quot;high&quot;) also gives some idea of how important an item is to the project. Others indicate what area of the project an issue relates to. It is a good idea to see if a task is assigned to any developers. If it is, then it may be under active development or that person knows the status. You should reach out to that person or the project for more information before working on that task. For related reasons, you should make sure you are assigned a task you are working on so others are aware you are working on it. The project board (see below) should also be updated as needed. If you cannot do these due to permission issues then contact us using the developer topic to get the changes made. You can also look at OED GitHub milestones to see what items are associated with which release of OED. This is an indication of the time frame that the item needs to be completed. Note that a task that does not show up in the issues, etc. is documenting the code. There are parts that have insufficient comments and it is very valuable to the project to rectify that situation. It is also a way to engage with the code without having to make changes that impact how it runs. The design documents (and previously the projects boards) have an overview of major initiatives. It lets you know what work is in progress and what we hope to do next. This generally overlaps the issues but gives a broader picture and is more visual. The OED Discord channel for developers (and previously the discussion board) . Here you can see the status of development and thought that have come up on issues relating to OED. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group. If you see an item that refers to a developer document and you do not have access then please just request it."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/work/"><meta property="og:title" content="Work Selection"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. We understand that when you join OED it can be tricky to figure out what to work on. This can also be the case as you wind down some work and are looking for more. The best way is to reach out to our contact us using the developer topic or your OED mentor (if you have one) so we can be of assistance. We will help you find tasks that help the project and are aligned with your interests. What you should work on depends on your background and interests, knowledge of the project and our needs so there is no single answer for what is best that suits everyone. One useful place to look is the GitHub issues for OED. There you will find issues in many areas that are labeled in ways that may help you identify which to work on. If you are new to the project and want to start with easier tasks then ones labeled &quot;i-good-first-issue&quot; are good ones to consider. The priority (&quot;low&quot;, &quot;medium&quot; and &quot;high&quot;) also gives some idea of how important an item is to the project. Others indicate what area of the project an issue relates to. It is a good idea to see if a task is assigned to any developers. If it is, then it may be under active development or that person knows the status. You should reach out to that person or the project for more information before working on that task. For related reasons, you should make sure you are assigned a task you are working on so others are aware you are working on it. The project board (see below) should also be updated as needed. If you cannot do these due to permission issues then contact us using the developer topic to get the changes made. You can also look at OED GitHub milestones to see what items are associated with which release of OED. This is an indication of the time frame that the item needs to be completed. Note that a task that does not show up in the issues, etc. is documenting the code. There are parts that have insufficient comments and it is very valuable to the project to rectify that situation. It is also a way to engage with the code without having to make changes that impact how it runs. The design documents (and previously the projects boards) have an overview of major initiatives. It lets you know what work is in progress and what we hope to do next. This generally overlaps the issues but gives a broader picture and is more visual. The OED Discord channel for developers (and previously the discussion board) . Here you can see the status of development and thought that have come up on issues relating to OED. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group. If you see an item that refers to a developer document and you do not have access then please just request it."><meta property="og:url" content="https://openenergydashboard.org/developer/work/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Work Selection</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Work Selection</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><p>We understand that when you join OED it can be tricky to figure out what to work on. This can also be the case as you wind down some work and are looking for more. The best way is to reach out to our <a href="https://openenergydashboard.org/contact/">contact us using the developer topic</a> or your OED mentor (if you have one) so we can be of assistance. We will help you find tasks that help the project and are aligned with your interests.<p>What you should work on depends on your background and interests, knowledge of the project and our needs so there is no single answer for what is best that suits everyone. One useful place to look is the <a href="https://github.com/OpenEnergyDashboard/OED/issues" rel="noopener noreferrer">GitHub issues</a> for OED. There you will find issues in many areas that are labeled in ways that may help you identify which to work on. If you are new to the project and want to start with easier tasks then ones labeled "i-good-first-issue" are good ones to consider. The priority ("low", "medium" and "high") also gives some idea of how important an item is to the project. Others indicate what area of the project an issue relates to. It is a good idea to see if a task is assigned to any developers. If it is, then it may be under active development or that person knows the status. You should reach out to that person or the project for more information before working on that task. For related reasons, you should make sure you are assigned a task you are working on so others are aware you are working on it. The project board (see below) should also be updated as needed. If you cannot do these due to permission issues then <a href="https://openenergydashboard.org/contact/">contact us using the developer topic</a> to get the changes made. You can also look at <a href="https://github.com/OpenEnergyDashboard/OED/milestones" rel="noopener noreferrer">OED GitHub milestones</a> to see what items are associated with which release of OED. This is an indication of the time frame that the item needs to be completed. Note that a task that does not show up in the issues, etc. is documenting the code. There are parts that have insufficient comments and it is very valuable to the project to rectify that situation. It is also a way to engage with the code without having to make changes that impact how it runs.<p>The <a href="https://github.com/OpenEnergyDashboard/DesignDocs">design documents</a> (and previously the <a href="https://github.com/OpenEnergyDashboard/OED/projects?type=beta" rel="noopener noreferrer">projects boards</a>) have an overview of major initiatives. It lets you know what work is in progress and what we hope to do next. This generally overlaps the issues but gives a broader picture and is more visual.<p>The <a href="https://openenergydashboard.org/contact/">OED Discord channel</a> for developers (and previously the <a href="https://github.com/OpenEnergyDashboard/OED/discussions" rel="noopener noreferrer">discussion board</a>) . Here you can see the status of development and thought that have come up on issues relating to OED. You are encouraged to subscribe to this discussion by clicking the button on the right side of the page with this discussion group.<p>If you see an item that refers to a developer document and you do not have access then please just request it.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/developer/wslSteps/index.html b/developer/wslSteps/index.html
deleted file mode 100644
index 257a132d..00000000
--- a/developer/wslSteps/index.html
+++ /dev/null
@@ -1 +0,0 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Steps for WSL</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Make sure your WSL is fully installed correctly, following these steps. You should not use WSL-1. Make sure Docker is correctly configured to work with WSL, following these steps. According to the best practices given in the Docker WSL information (at least when this was written), it is best to work in the Linux container rather than the Windows file system. This means you should clone OED into the Linux file system and run your code environment (such as Visual Studio Code) there as well. The information below assumes you have done this and the commands given are run in a Linux shell. Specifically, this means: You do the git clone &amp;lt;OED GitHub address&amp;gt; in the Linux filesystem. Normally this is done by opening the Linux terminal. You do not want the OED clone on your machine to be on the Windows partition. To use Visual Studio Code, you will start it from the Linux terminal by doing the following: Open your Linux terminal. This is commonly the Ubuntu terminal for WSL. Go to the Linux directory with OED in a Linux terminal by doing: cd &amp;lt;path to OED main code directory&amp;gt; Start Visual Studio Code by doing: code . (This will start VSC and make the current directory be the code you will work on.) Note the first time you may need to install VSC; This normally happens automatically on Ubuntu. After the first time you can normally click the VSC icon on Windows to start it. It will reopen with the WSL project if that was the last one. If not, you can open the project folder from recent ones or via the command &quot;WSL: Open Folder in WSL...&quot;. If you ever have a folder open outside WSL but it is actually on WSL then you can use the command to reopen in WSL (sometimes VSC will suggest you do that). All the other steps should be the same as on the getting started directions. Errors running docker compose up might throw: FileNotFoundError: [Errno 2] No such file or directory Ensure that docker is installed correctly and running - the Docker system tray icon&#39;s tooltip should specify that Docker Desktop is running. When you first install OED, you get some sort of error message (often about not being able to write the pg_wal file). This leads to the database going into a panic stop and the database container exiting. When this has been seen, the web container continues to run and the npm install continues/completes. Note it can take a while for the npm install to finish but wait and hopefully this will happen. You will likely then get a message about trying to start to database but nothing after that one line. At this point, stop the install. If in the VSC container then rebuild the container. If OED was started in a terminal then do a single ^c (control and letter c) or docker compose down in a second terminal where it is in the same OED directory as the install is happening. You should now be back at the command line. Do another docker compose up to restart OED. Normally this will complete the installation fairly quickly without further issues. For now, we encourage you to do these exact steps since deviations have been known to cause it to fail. If have issues then please contact us. Script errors If you have the OED files stored on the Windows file system, then issues will likely occur. It can happen on install, when you run checks (linting) and for other OED scripts. This is because the file format is a little different. The best solution is to keep all files on the Linux file system (as suggested above). It is possible to modify the scripts with but this is not the recommended solution."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/developer/wslSteps/"><meta property="og:title" content="Steps for WSL"><meta property="og:description" content="Documentation overview Developer documentation Information Overview Starting Developer First Steps Steps for WSL Contributor License Agreement Creating Pull Requests Test Data Work Selection Codebase Info Learn OED Technology npm scripts Technology Overview Further Details Code Organization Developer Details Documentation Expectations Environment Variables Full Install Output No npm/DB Install Output Test Code Version Release Releasing OED This information is for developers of the OED software so this information is not usually of interest to a general user. The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date. Make sure your WSL is fully installed correctly, following these steps. You should not use WSL-1. Make sure Docker is correctly configured to work with WSL, following these steps. According to the best practices given in the Docker WSL information (at least when this was written), it is best to work in the Linux container rather than the Windows file system. This means you should clone OED into the Linux file system and run your code environment (such as Visual Studio Code) there as well. The information below assumes you have done this and the commands given are run in a Linux shell. Specifically, this means: You do the git clone &amp;lt;OED GitHub address&amp;gt; in the Linux filesystem. Normally this is done by opening the Linux terminal. You do not want the OED clone on your machine to be on the Windows partition. To use Visual Studio Code, you will start it from the Linux terminal by doing the following: Open your Linux terminal. This is commonly the Ubuntu terminal for WSL. Go to the Linux directory with OED in a Linux terminal by doing: cd &amp;lt;path to OED main code directory&amp;gt; Start Visual Studio Code by doing: code . (This will start VSC and make the current directory be the code you will work on.) Note the first time you may need to install VSC; This normally happens automatically on Ubuntu. After the first time you can normally click the VSC icon on Windows to start it. It will reopen with the WSL project if that was the last one. If not, you can open the project folder from recent ones or via the command &quot;WSL: Open Folder in WSL...&quot;. If you ever have a folder open outside WSL but it is actually on WSL then you can use the command to reopen in WSL (sometimes VSC will suggest you do that). All the other steps should be the same as on the getting started directions. Errors running docker compose up might throw: FileNotFoundError: [Errno 2] No such file or directory Ensure that docker is installed correctly and running - the Docker system tray icon&#39;s tooltip should specify that Docker Desktop is running. When you first install OED, you get some sort of error message (often about not being able to write the pg_wal file). This leads to the database going into a panic stop and the database container exiting. When this has been seen, the web container continues to run and the npm install continues/completes. Note it can take a while for the npm install to finish but wait and hopefully this will happen. You will likely then get a message about trying to start to database but nothing after that one line. At this point, stop the install. If in the VSC container then rebuild the container. If OED was started in a terminal then do a single ^c (control and letter c) or docker compose down in a second terminal where it is in the same OED directory as the install is happening. You should now be back at the command line. Do another docker compose up to restart OED. Normally this will complete the installation fairly quickly without further issues. For now, we encourage you to do these exact steps since deviations have been known to cause it to fail. If have issues then please contact us. Script errors If you have the OED files stored on the Windows file system, then issues will likely occur. It can happen on install, when you run checks (linting) and for other OED scripts. This is because the file format is a little different. The best solution is to keep all files on the Linux file system (as suggested above). It is possible to modify the scripts with but this is not the recommended solution."><meta property="og:url" content="https://openenergydashboard.org/developer/wslSteps/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoDeveloper.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/developer/">developer</a> <a class="current">Steps for WSL</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Developer Documentation<h1>Steps for WSL</h1></header><div class="row"><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../developer/'>Documentation overview</a></h4><div><h5>Developer documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/developer/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Starting</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/gettingStarted/">Developer First Steps</a></br> <a href="https://openenergydashboard.org/developer/wslSteps/">Steps for WSL</a></br> <a href="https://openenergydashboard.org/developer/cla/">Contributor License Agreement</a></br> <a href="https://openenergydashboard.org/developer/pr/">Creating Pull Requests</a></br> <a href="https://openenergydashboard.org/developer/testData/">Test Data</a></br> <a href="https://openenergydashboard.org/developer/work/">Work Selection</a></br></div></div><div style="padding-left: 1em;"><h6>Codebase Info</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/learningTechnologies/">Learn OED Technology</a></br> <a href="https://openenergydashboard.org/developer/npm/">npm scripts</a></br> <a href="https://openenergydashboard.org/developer/technologies/">Technology Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Further Details</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/codeOrganization/">Code Organization</a></br> <a href="https://openenergydashboard.org/developer/devDetails/">Developer Details</a></br> <a href="https://openenergydashboard.org/developer/codeGuidelines/">Documentation Expectations</a></br> <a href="https://openenergydashboard.org/developer/environment/">Environment Variables</a></br> <a href="https://openenergydashboard.org/developer/fullInstallOutput/">Full Install Output</a></br> <a href="https://openenergydashboard.org/developer/noNPMInstallOutput/">No npm/DB Install Output</a></br> <a href="https://openenergydashboard.org/developer/testing/">Test Code</a></br></div></div><div style="padding-left: 1em;"><h6>Version Release</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/developer/release/">Releasing OED</a></br></div></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>This information is for developers of the OED software so this information is not usually of interest to a general user.</div><div class="alert-box warning "><p>The update to the Redux Toolkit (RTK) is not yet reflected in the documentation. As a result, some information may be out of date.</div><ol><li>Make sure your WSL is fully installed correctly, following <a href="https://learn.microsoft.com/en-us/windows/wsl/install" rel="noopener noreferrer">these steps</a>. You should <strong>not</strong> use WSL-1.<li>Make sure Docker is correctly configured to work with WSL, following <a href="https://docs.docker.com/desktop/wsl/" rel="noopener noreferrer">these steps</a>.</ol><p> According to the best practices given in the <a href="https://docs.docker.com/desktop/wsl/best-practices/" rel="noopener noreferrer">Docker WSL information</a> (at least when this was written), it is best to work in the Linux container rather than the Windows file system. This means you should clone OED into the Linux file system and run your code environment (such as Visual Studio Code) there as well. The information below assumes you have done this and the commands given are run in a Linux shell. Specifically, this means:<ol><li>You do the <code>git clone &lt;OED GitHub address&gt;</code> in the Linux filesystem. Normally this is done by opening the Linux terminal. You do not want the OED clone on your machine to be on the Windows partition.<li>To use Visual Studio Code, you will start it from the Linux terminal by doing the following:<ol><li>Open your Linux terminal. This is commonly the Ubuntu terminal for WSL.<li>Go to the Linux directory with OED in a Linux terminal by doing: <code>cd &lt;path to OED main code directory&gt;</code><li>Start Visual Studio Code by doing: <code>code .</code> (This will start VSC and make the current directory be the code you will work on.) Note the first time you may need to install VSC; This normally happens automatically on Ubuntu. After the first time you can normally click the VSC icon on Windows to start it. It will reopen with the WSL project if that was the last one. If not, you can open the project folder from recent ones or via the command "WSL: Open Folder in WSL...". If you ever have a folder open outside WSL but it is actually on WSL then you can use the command to reopen in WSL (sometimes VSC will suggest you do that).<li>All the other steps should be the same as on the getting started directions.</ol></ol></strong><h3>Errors running <code>docker compose up</code> might throw:</h3><ol><li><h3><code>FileNotFoundError: [Errno 2] No such file or directory</code></h3><br> Ensure that docker is installed correctly and running - the Docker system tray icon's tooltip should specify that Docker Desktop is running.<li> When you first install OED, you get some sort of error message (often about not being able to write the pg_wal file). This leads to the database going into a panic stop and the database container exiting. When this has been seen, the web container continues to run and the npm install continues/completes. Note it can take a while for the npm install to finish but wait and hopefully this will happen. You will likely then get a message about trying to start to database but nothing after that one line. At this point, stop the install.<ul><li>If in the VSC container then rebuild the container.<li>If OED was started in a terminal then do a <strong>single ^c</strong> (control and letter c) or <code>docker compose down</code> in a second terminal where it is in the same OED directory as the install is happening. You should now be back at the command line. Do another <code>docker compose up</code> to restart OED.</ul><p>Normally this will complete the installation fairly quickly without further issues. For now, we encourage you to do these exact steps since deviations have been known to cause it to fail. If have issues then please contact us.</ol><h3>Script errors</h3><p>If you have the OED files stored on the Windows file system, then issues will likely occur. It can happen on install, when you run checks (linting) and for other OED scripts. This is because the file format is a little different. The best solution is to keep all files on the Linux file system (as suggested above). It is possible to modify the scripts with but this is not the recommended solution.</div></div></article></div></div><div id="up-to-top" class="row"><div class="small-12 columns" style="text-align: right;"> <a class="iconfont" href="#top-of-page">&#xf108;</a></div></div><footer id="footer-content" class="bg-grau"><div id="footer"><div class="row"> <noscript><div class="alert-box warning "><p>Some aspect of this site will not work and others will work better if you enable JavaScript.</div></noscript></div><div class="row"><div class="medium-6 large-5 columns"><h5 class="shadow-black">About This Site</h5><p class="shadow-black"> The OED dashboard allows organization to acquire, archive, analyze and display energy/resource usage. <a href="https://openenergydashboard.org/features/">More ›</a></div><div class="small-6 medium-3 large-3 large-offset-1 columns"><h5 class="shadow-black">Services</h5><ul class="no-bullet shadow-black"><li > <a href="https://openenergydashboard.org/" title=""></a><li > <a href="https://openenergydashboard.org/contact/" title="Contact">Contact</a><li > <a href="https://openenergydashboard.org/sitemap.xml" title="Sitemap for Google Webmaster Tools">sitemap.xml</a></ul></div><div class="small-6 medium-3 large-3 columns"><ul class="no-bullet shadow-black"></ul></div></div></div><div id="subfooter"><nav class="row"><section id="subfooter-left" class="small-12 medium-6 columns credits"><p>Created by the OED team using <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> based on <a href="https://phlow.github.io/feeling-responsive/">Feeling Responsive</a>. This page is part of the Open Energy Dashboard and is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, you can obtain one at <a href="https://www.mozilla.org/en-US/MPL/2.0/" rel="nofollow">https://www.mozilla.org/en-US/MPL/2.0/</a>.</section><section id="subfooter-right" class="small-12 medium-6 columns"><ul class="inline-list social-icons"><li><a href="https://github.com/OpenEnergyDashboard/OED" target="_blank" class="icon-github" title="Code other repos..."></a></ul></section></nav></div></footer><script src="https://openenergydashboard.org/assets/js/javascript.min.js"></script>
diff --git a/helpV0_7_0/adminInstallation/index.html b/helpV0_7_0/adminInstallation/index.html
index 8a90ff39..50c8f354 100644
--- a/helpV0_7_0/adminInstallation/index.html
+++ b/helpV0_7_0/adminInstallation/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Installation Directions Doc</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Version V0.7.0 The latest version of this page is V1.0.0. Documentation overview Admin documentation Information Overview Site Management Group Map Management Map Viewing Meter Viewing Site Settings User Data Acquisition CSV Import Data Acquisition MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades User documentation User help Documentation versions for this page V1.0.0 V0.8.0 V0.7.0 (current page) These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The beginning of the WSL page has details on WSL and Docker installation on Windows 10 Home. OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. (Note more recent versions of Docker have the docker compose command so you no longer need docker-compose. If your Docker does not support this (likely see an error with docker compose of &quot;docker: &#39;compose&#39; is not a docker command.&quot;) then you need to install docker-compose and replace all the docker compose commands with docker-compose.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization. This guide requires that you enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in your application menu. Installation Follow these steps to install a production (OED site for you institution) site: Clone the desired OED code from Github. Note if you leave off directory in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use &quot;.&quot; for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone. If you want a specific released version of OED (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. You can find the officially released and tagged versions at the OED GitHub release page. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git. After this you should see the directory OED where you did the clone. If you want the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone). Edit docker-compose.yml. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; datebase: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but you should never need to know this value. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) to a mapping from host to container; e.g., to host on your computer&#39;s port 80, set it to 80:3000. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before you edit it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If you want to have standard web requests (port 80) serve up OED then edit to look like (you comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if you leave the line - &quot;3000:3000&quot; uncommented and comment out - &quot;9229:9229&quot; then OED will server up on port 3000 (where you leave the - &quot;80:3000&quot; line commented out). Later in these directions, it is suggested you set up a cron job to send an email to someone each day with any issues the OED installation encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. To do this you need to set these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP) As the comment says this can be gmail if using Google Mail, mailgun if you are using that locally or none if you aren&#39;t going to use the mail sending. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this may become OED_MAIL_METHOD=gmail or OED_MAIL_METHOD=mailgun. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with your user name email. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA). OED_MAIL_FROM give the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where you use the desired email address. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name you want. If you are going to be accepting data from Obvius, you should set the password that Obvius sends with each request. If not, then set to some random value to secure this service. Thus, set the OED_OBVIUS_PASSWORD (under services: -&amp;gt; web: -&amp;gt; environment:) to what will be used so you replace pleaseChange with what you want. For the remaining steps you need to be the superuser/root to have sufficient permission to modify system files. On some OS setups you can do the install step (next) without being the superuser but it is generally safer to not to try. Make sure you are in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of your server. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while normally happening right after the &quot; database system is ready to accept connections&quot; output line) and starting up the web system. When you see the lines: web_1 | + 1836 hidden modules web_1 | OED install finished web_1 | Starting OED in production mode web_1 | web_1 | &gt; Open-Energy-Dashboard@0.7.0 start web_1 | &gt; node ./src/bin/www web_1 | web_1 | [INFO@2021-09-23T20:52:14.190Z] Listening on port 3000 then OED should be ready to accept web requests, where the actual number of hidden modules will likely be different. Note is says is is listening on port 3000 since that is what OED listens on but the ports: changes you made above mean the web requests to port 80 (or whatever you chose) will be sent on to port 3000 for OED. If there was an error in the output then OED might not be running properly. Please contact the OED project if you have questions where sending the terminal text is generally very helpful. If you quickly get the error Invalid interpolation format for &quot;command&quot; option in service &quot;web&quot;: &quot;${install_args:-}&quot; then it is likely you are running an older version of docker-compose (less than version 2). You can fix this error by editing the docker-compose.yml file (as you did above). At the end of the file you will see (Note OED v0.7.0 and earlier does not have the last three lines to deal with older versions of docker compose so you will need to add them during your edits. It also has the reverse proxy line comment that has since been removed.): # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] Edit this to be: # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] If you redo the docker compose up then you should now get the expected output described above. The typical output of the install is available. You can now use a web browser to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where you replace oed.myinstition.org with the name of the server where you installed OED. If all is working properly you will see the main OED page (see Graph Type help page for an image of what it will look like). You won&#39;t be able to graph any data until you have OED acquire meter data. If you did not do the mapping of 80:3000 above, then OED would be reachable at oed.myinstition.org:3000. You now need to create an admin user so you can log into OED on the website. To do this you will need a second terminal where you go to the root OED directory and are a superuser/root (as you have been). This is done so you don&#39;t have to shut down OED to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt you to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password you want to use with this email to login to OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password so you have access to OED admin features on the web pages. You can run the command docker compose run web npm run editUser to change the password if you forget it or you can create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what you type so this information will be in the terminal. You shouldn&#39;t need this terminal any more so you can close it to hide the information or usually type clear to remove it from what is shown in the terminal. You should now log in to make sure this account works. Logging in directions are available but basically you click the &quot;Log in&quot; button in the top, right of the OED website and then enter the information. Shut down OED. You will soon setting up OED to run as a service so you want to stop the one running in the terminal. In the terminal where you started OED (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. In the following steps you need to know the root directory of OED. In the terminal where you are in the OED root directory do: pwd and the output will tell you the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. You are not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on your system. There is a chance that your version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; you need to set below is the one assigned to OED, the one you logged in as before becoming superuser/root or (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming you want to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless you disable this service with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart when you start the service again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If you want to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes you want to see the output of OED when it is running as a service. This can be useful during the install if you want to see why OED did not come up. You do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where you replace &amp;lt;CONTAINER ID&amp;gt; with the one you want from the previous step. You will want to get meter data into OED so the site can display data. See the data acquisition page for more information on doing this. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, you will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If you see a newer version that you want to upgrade to then consult the directions on the OED Upgrading page. Other information Though less likely, you may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is a node_modules directory in the root OED directory) and skips doing it again to save time. However you can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before you do this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/helpV0_7_0/adminInstallation/"><meta property="og:title" content="Installation Directions Doc"><meta property="og:description" content="Version V0.7.0 The latest version of this page is V1.0.0. Documentation overview Admin documentation Information Overview Site Management Group Map Management Map Viewing Meter Viewing Site Settings User Data Acquisition CSV Import Data Acquisition MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades User documentation User help Documentation versions for this page V1.0.0 V0.8.0 V0.7.0 (current page) These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The beginning of the WSL page has details on WSL and Docker installation on Windows 10 Home. OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. (Note more recent versions of Docker have the docker compose command so you no longer need docker-compose. If your Docker does not support this (likely see an error with docker compose of &quot;docker: &#39;compose&#39; is not a docker command.&quot;) then you need to install docker-compose and replace all the docker compose commands with docker-compose.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization. This guide requires that you enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in your application menu. Installation Follow these steps to install a production (OED site for you institution) site: Clone the desired OED code from Github. Note if you leave off directory in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use &quot;.&quot; for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone. If you want a specific released version of OED (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. You can find the officially released and tagged versions at the OED GitHub release page. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git. After this you should see the directory OED where you did the clone. If you want the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone). Edit docker-compose.yml. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; datebase: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but you should never need to know this value. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) to a mapping from host to container; e.g., to host on your computer&#39;s port 80, set it to 80:3000. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before you edit it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If you want to have standard web requests (port 80) serve up OED then edit to look like (you comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if you leave the line - &quot;3000:3000&quot; uncommented and comment out - &quot;9229:9229&quot; then OED will server up on port 3000 (where you leave the - &quot;80:3000&quot; line commented out). Later in these directions, it is suggested you set up a cron job to send an email to someone each day with any issues the OED installation encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. To do this you need to set these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP) As the comment says this can be gmail if using Google Mail, mailgun if you are using that locally or none if you aren&#39;t going to use the mail sending. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this may become OED_MAIL_METHOD=gmail or OED_MAIL_METHOD=mailgun. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with your user name email. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA). OED_MAIL_FROM give the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where you use the desired email address. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name you want. If you are going to be accepting data from Obvius, you should set the password that Obvius sends with each request. If not, then set to some random value to secure this service. Thus, set the OED_OBVIUS_PASSWORD (under services: -&amp;gt; web: -&amp;gt; environment:) to what will be used so you replace pleaseChange with what you want. For the remaining steps you need to be the superuser/root to have sufficient permission to modify system files. On some OS setups you can do the install step (next) without being the superuser but it is generally safer to not to try. Make sure you are in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of your server. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while normally happening right after the &quot; database system is ready to accept connections&quot; output line) and starting up the web system. When you see the lines: web_1 | + 1836 hidden modules web_1 | OED install finished web_1 | Starting OED in production mode web_1 | web_1 | &gt; Open-Energy-Dashboard@0.7.0 start web_1 | &gt; node ./src/bin/www web_1 | web_1 | [INFO@2021-09-23T20:52:14.190Z] Listening on port 3000 then OED should be ready to accept web requests, where the actual number of hidden modules will likely be different. Note is says is is listening on port 3000 since that is what OED listens on but the ports: changes you made above mean the web requests to port 80 (or whatever you chose) will be sent on to port 3000 for OED. If there was an error in the output then OED might not be running properly. Please contact the OED project if you have questions where sending the terminal text is generally very helpful. If you quickly get the error Invalid interpolation format for &quot;command&quot; option in service &quot;web&quot;: &quot;${install_args:-}&quot; then it is likely you are running an older version of docker-compose (less than version 2). You can fix this error by editing the docker-compose.yml file (as you did above). At the end of the file you will see (Note OED v0.7.0 and earlier does not have the last three lines to deal with older versions of docker compose so you will need to add them during your edits. It also has the reverse proxy line comment that has since been removed.): # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] Edit this to be: # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] If you redo the docker compose up then you should now get the expected output described above. The typical output of the install is available. You can now use a web browser to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where you replace oed.myinstition.org with the name of the server where you installed OED. If all is working properly you will see the main OED page (see Graph Type help page for an image of what it will look like). You won&#39;t be able to graph any data until you have OED acquire meter data. If you did not do the mapping of 80:3000 above, then OED would be reachable at oed.myinstition.org:3000. You now need to create an admin user so you can log into OED on the website. To do this you will need a second terminal where you go to the root OED directory and are a superuser/root (as you have been). This is done so you don&#39;t have to shut down OED to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt you to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password you want to use with this email to login to OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password so you have access to OED admin features on the web pages. You can run the command docker compose run web npm run editUser to change the password if you forget it or you can create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what you type so this information will be in the terminal. You shouldn&#39;t need this terminal any more so you can close it to hide the information or usually type clear to remove it from what is shown in the terminal. You should now log in to make sure this account works. Logging in directions are available but basically you click the &quot;Log in&quot; button in the top, right of the OED website and then enter the information. Shut down OED. You will soon setting up OED to run as a service so you want to stop the one running in the terminal. In the terminal where you started OED (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. In the following steps you need to know the root directory of OED. In the terminal where you are in the OED root directory do: pwd and the output will tell you the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. You are not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on your system. There is a chance that your version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; you need to set below is the one assigned to OED, the one you logged in as before becoming superuser/root or (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming you want to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless you disable this service with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart when you start the service again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If you want to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes you want to see the output of OED when it is running as a service. This can be useful during the install if you want to see why OED did not come up. You do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where you replace &amp;lt;CONTAINER ID&amp;gt; with the one you want from the previous step. You will want to get meter data into OED so the site can display data. See the data acquisition page for more information on doing this. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, you will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If you see a newer version that you want to upgrade to then consult the directions on the OED Upgrading page. Other information Though less likely, you may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is a node_modules directory in the root OED directory) and skips doing it again to save time. However you can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before you do this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta property="og:url" content="https://openenergydashboard.org/helpV0_7_0/adminInstallation/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoHelp.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/helpV0_7_0/">helpV0_7_0</a> <a class="current">Installation Directions</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Documentation<h1>Installation Directions</h1></header><div class="row"><p>Version V0.7.0<div class="alert-box info "><p>The latest version of this page is <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">V1.0.0</a>.</div><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../admin/'>Documentation overview</a></h4><div><h5>Admin documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/admin/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Site Management</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/adminGroupViewing/">Group</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMap/">Map Management</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMapViewing/">Map Viewing</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMeterViewing/">Meter Viewing</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminPreferences/">Site Settings</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminUser/">User</a></br></div></div><div style="padding-left: 1em;"><h6>Data Acquisition</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/adminCsvImport/">CSV Import</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminDataAcquisition/">Data Acquisition</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMamac/">MAMAC</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMetersImport/">Meter Import</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminReadingsImport/">Reading Import</a></br></div></div><div style="padding-left: 1em;"><h6>Site Installation</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/adminInstallOutput/">Production Install Output</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminInstallation/">Installation Directions</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminUpgrading/">Upgrades</a></br></div></div><h5>User documentation</h5><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/adminInstallation/../user/">User help</a></br></div><h5>Documentation versions for this page</h5><div style="padding-left: 1em;"> <a href="../../helpV1_0_0/adminInstallation/">V1.0.0</a></br> <a href="../../helpV0_8_0/adminInstallation/">V0.8.0</a></br> V0.7.0 (current page)</br></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user.</div><p>This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the <a href="https://openenergydashboard.org/developer/gettingStarted/">getting started</a> page.<h2>Requirements</h2><p>OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The beginning of the <a href="https://openenergydashboard.org/developer/wslSteps/">WSL page</a> has details on WSL and Docker installation on Windows 10 Home.<p>OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the <code>docker compose</code> command. (Note more recent versions of Docker have the <code>docker compose</code> command so you no longer need <code>docker-compose</code>. If your Docker does not support this (likely see an error with <code>docker compose</code> of "docker: 'compose' is not a docker command.") then you need to install docker-compose and replace all the <code>docker compose</code> commands with <code>docker-compose</code>.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from <a href="https://docs.docker.com/engine/install/" rel="nofollow">Docker</a>.<p>It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation.<p>These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization.<p>This guide requires that you enter some commands into an operating system shell, or terminal.<ul><li>On Windows, this is the terminal that connects to the Linux running under WSL.<li>On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program.<li>On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for "Terminal" in your application menu.</ul><h2>Installation</h2><p>Follow these steps to install a production (OED site for you institution) site:<ol><li><p>Clone the desired OED code from Github. Note if you leave off <code>directory</code> in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use "." for the <code>directory</code> (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone.<ul><li>If you want a specific released version of OED (this is most common) then do: <code>git clone --branch &lt;tag_name&gt; https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. You can find the officially released and tagged versions at the <a href="https://github.com/OpenEnergyDashboard/OED/releases" rel="noopener noreferrer">OED GitHub release page</a>. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: <code>git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git</code>. After this you should see the directory OED where you did the clone.<li>If you want the latest version from development then do: <code>git clone https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base.</ul><li>cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone).<li><p>Edit <code>docker-compose.yml</code>. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are:<ol><li>POSTGRES_PASSWORD (under <code>services: -&gt; datebase: -&gt; environment:</code>) to a site specific password instead of the <code>pleaseChange</code> that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: <code>- POSTGRES_PASSWORD=whateverPasswordYouChoose</code><li>OED_PRODUCTION (under <code>services: -&gt; web: -&gt; environment:</code>) to <code>yes</code> so it becomes: <code>- OED_PRODUCTION=yes</code>.<li>OED_TOKEN_SECRET (under <code>services: -&gt; web: -&gt; environment:</code>) to a random value instead of the <code>?</code> that is provided. Keep it secret but you should never need to know this value. It will be: <code>- OED_TOKEN_SECRET=whateverTokenYouChoose</code><li>The port (in <code>services: -&gt; web: -&gt; ports:</code>) to a mapping from host to container; e.g., to host on your computer's port 80, set it to <code>80:3000</code>. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with <code>#</code>). Before you edit it should look like:<pre><code>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Installation Directions Doc</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Version V0.7.0 The latest version of this page is V1.0.0. Documentation overview Admin documentation Information Overview Site Management Group Map Management Map Viewing Meter Viewing Site Settings User Data Acquisition CSV Import Data Acquisition MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades User documentation User help Documentation versions for this page V1.0.0 V0.8.0 V0.7.0 (current page) These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows OS Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The developer getting started page has details on WSL and Docker installation. OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. (Note more recent versions of Docker have the docker compose command so you no longer need docker-compose. If your Docker does not support this (likely see an error with docker compose of &quot;docker: &#39;compose&#39; is not a docker command.&quot;) then you need to install docker-compose and replace all the docker compose commands with docker-compose.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization. This guide requires that you enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in your application menu. Installation Follow these steps to install a production (OED site for you institution) site: Clone the desired OED code from Github. Note if you leave off directory in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use &quot;.&quot; for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone. If you want a specific released version of OED (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. You can find the officially released and tagged versions at the OED GitHub release page. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git. After this you should see the directory OED where you did the clone. If you want the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone). Edit docker-compose.yml. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; datebase: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but you should never need to know this value. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) to a mapping from host to container; e.g., to host on your computer&#39;s port 80, set it to 80:3000. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before you edit it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If you want to have standard web requests (port 80) serve up OED then edit to look like (you comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if you leave the line - &quot;3000:3000&quot; uncommented and comment out - &quot;9229:9229&quot; then OED will server up on port 3000 (where you leave the - &quot;80:3000&quot; line commented out). Later in these directions, it is suggested you set up a cron job to send an email to someone each day with any issues the OED installation encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. To do this you need to set these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP) As the comment says this can be gmail if using Google Mail, mailgun if you are using that locally or none if you aren&#39;t going to use the mail sending. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this may become OED_MAIL_METHOD=gmail or OED_MAIL_METHOD=mailgun. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with your user name email. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA). OED_MAIL_FROM give the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where you use the desired email address. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name you want. If you are going to be accepting data from Obvius, you should set the password that Obvius sends with each request. If not, then set to some random value to secure this service. Thus, set the OED_OBVIUS_PASSWORD (under services: -&amp;gt; web: -&amp;gt; environment:) to what will be used so you replace pleaseChange with what you want. For the remaining steps you need to be the superuser/root to have sufficient permission to modify system files. On some OS setups you can do the install step (next) without being the superuser but it is generally safer to not to try. Make sure you are in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of your server. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while normally happening right after the &quot; database system is ready to accept connections&quot; output line) and starting up the web system. When you see the lines: web_1 | + 1836 hidden modules web_1 | OED install finished web_1 | Starting OED in production mode web_1 | web_1 | &gt; Open-Energy-Dashboard@0.7.0 start web_1 | &gt; node ./src/bin/www web_1 | web_1 | [INFO@2021-09-23T20:52:14.190Z] Listening on port 3000 then OED should be ready to accept web requests, where the actual number of hidden modules will likely be different. Note is says is is listening on port 3000 since that is what OED listens on but the ports: changes you made above mean the web requests to port 80 (or whatever you chose) will be sent on to port 3000 for OED. If there was an error in the output then OED might not be running properly. Please contact the OED project if you have questions where sending the terminal text is generally very helpful. If you quickly get the error Invalid interpolation format for &quot;command&quot; option in service &quot;web&quot;: &quot;${install_args:-}&quot; then it is likely you are running an older version of docker-compose (less than version 2). You can fix this error by editing the docker-compose.yml file (as you did above). At the end of the file you will see (Note OED v0.7.0 and earlier does not have the last three lines to deal with older versions of docker compose so you will need to add them during your edits. It also has the reverse proxy line comment that has since been removed.): # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] Edit this to be: # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] If you redo the docker compose up then you should now get the expected output described above. The typical output of the install is available. You can now use a web browser to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where you replace oed.myinstition.org with the name of the server where you installed OED. If all is working properly you will see the main OED page (see Graph Type help page for an image of what it will look like). You won&#39;t be able to graph any data until you have OED acquire meter data. If you did not do the mapping of 80:3000 above, then OED would be reachable at oed.myinstition.org:3000. You now need to create an admin user so you can log into OED on the website. To do this you will need a second terminal where you go to the root OED directory and are a superuser/root (as you have been). This is done so you don&#39;t have to shut down OED to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt you to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password you want to use with this email to login to OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password so you have access to OED admin features on the web pages. You can run the command docker compose run web npm run editUser to change the password if you forget it or you can create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what you type so this information will be in the terminal. You shouldn&#39;t need this terminal any more so you can close it to hide the information or usually type clear to remove it from what is shown in the terminal. You should now log in to make sure this account works. Logging in directions are available but basically you click the &quot;Log in&quot; button in the top, right of the OED website and then enter the information. Shut down OED. You will soon setting up OED to run as a service so you want to stop the one running in the terminal. In the terminal where you started OED (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. In the following steps you need to know the root directory of OED. In the terminal where you are in the OED root directory do: pwd and the output will tell you the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. You are not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on your system. There is a chance that your version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; you need to set below is the one assigned to OED, the one you logged in as before becoming superuser/root or (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming you want to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless you disable this service with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart when you start the service again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If you want to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes you want to see the output of OED when it is running as a service. This can be useful during the install if you want to see why OED did not come up. You do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where you replace &amp;lt;CONTAINER ID&amp;gt; with the one you want from the previous step. You will want to get meter data into OED so the site can display data. See the data acquisition page for more information on doing this. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, you will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If you see a newer version that you want to upgrade to then consult the directions on the OED Upgrading page. Other information Though less likely, you may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is a node_modules directory in the root OED directory) and skips doing it again to save time. However you can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before you do this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/helpV0_7_0/adminInstallation/"><meta property="og:title" content="Installation Directions Doc"><meta property="og:description" content="Version V0.7.0 The latest version of this page is V1.0.0. Documentation overview Admin documentation Information Overview Site Management Group Map Management Map Viewing Meter Viewing Site Settings User Data Acquisition CSV Import Data Acquisition MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades User documentation User help Documentation versions for this page V1.0.0 V0.8.0 V0.7.0 (current page) These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows OS Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The developer getting started page has details on WSL and Docker installation. OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. (Note more recent versions of Docker have the docker compose command so you no longer need docker-compose. If your Docker does not support this (likely see an error with docker compose of &quot;docker: &#39;compose&#39; is not a docker command.&quot;) then you need to install docker-compose and replace all the docker compose commands with docker-compose.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization. This guide requires that you enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in your application menu. Installation Follow these steps to install a production (OED site for you institution) site: Clone the desired OED code from Github. Note if you leave off directory in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use &quot;.&quot; for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone. If you want a specific released version of OED (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. You can find the officially released and tagged versions at the OED GitHub release page. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git. After this you should see the directory OED where you did the clone. If you want the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone). Edit docker-compose.yml. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; datebase: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but you should never need to know this value. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) to a mapping from host to container; e.g., to host on your computer&#39;s port 80, set it to 80:3000. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before you edit it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If you want to have standard web requests (port 80) serve up OED then edit to look like (you comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if you leave the line - &quot;3000:3000&quot; uncommented and comment out - &quot;9229:9229&quot; then OED will server up on port 3000 (where you leave the - &quot;80:3000&quot; line commented out). Later in these directions, it is suggested you set up a cron job to send an email to someone each day with any issues the OED installation encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. To do this you need to set these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP) As the comment says this can be gmail if using Google Mail, mailgun if you are using that locally or none if you aren&#39;t going to use the mail sending. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this may become OED_MAIL_METHOD=gmail or OED_MAIL_METHOD=mailgun. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with your user name email. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA). OED_MAIL_FROM give the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where you use the desired email address. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name you want. If you are going to be accepting data from Obvius, you should set the password that Obvius sends with each request. If not, then set to some random value to secure this service. Thus, set the OED_OBVIUS_PASSWORD (under services: -&amp;gt; web: -&amp;gt; environment:) to what will be used so you replace pleaseChange with what you want. For the remaining steps you need to be the superuser/root to have sufficient permission to modify system files. On some OS setups you can do the install step (next) without being the superuser but it is generally safer to not to try. Make sure you are in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of your server. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while normally happening right after the &quot; database system is ready to accept connections&quot; output line) and starting up the web system. When you see the lines: web_1 | + 1836 hidden modules web_1 | OED install finished web_1 | Starting OED in production mode web_1 | web_1 | &gt; Open-Energy-Dashboard@0.7.0 start web_1 | &gt; node ./src/bin/www web_1 | web_1 | [INFO@2021-09-23T20:52:14.190Z] Listening on port 3000 then OED should be ready to accept web requests, where the actual number of hidden modules will likely be different. Note is says is is listening on port 3000 since that is what OED listens on but the ports: changes you made above mean the web requests to port 80 (or whatever you chose) will be sent on to port 3000 for OED. If there was an error in the output then OED might not be running properly. Please contact the OED project if you have questions where sending the terminal text is generally very helpful. If you quickly get the error Invalid interpolation format for &quot;command&quot; option in service &quot;web&quot;: &quot;${install_args:-}&quot; then it is likely you are running an older version of docker-compose (less than version 2). You can fix this error by editing the docker-compose.yml file (as you did above). At the end of the file you will see (Note OED v0.7.0 and earlier does not have the last three lines to deal with older versions of docker compose so you will need to add them during your edits. It also has the reverse proxy line comment that has since been removed.): # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] Edit this to be: # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] If you redo the docker compose up then you should now get the expected output described above. The typical output of the install is available. You can now use a web browser to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where you replace oed.myinstition.org with the name of the server where you installed OED. If all is working properly you will see the main OED page (see Graph Type help page for an image of what it will look like). You won&#39;t be able to graph any data until you have OED acquire meter data. If you did not do the mapping of 80:3000 above, then OED would be reachable at oed.myinstition.org:3000. You now need to create an admin user so you can log into OED on the website. To do this you will need a second terminal where you go to the root OED directory and are a superuser/root (as you have been). This is done so you don&#39;t have to shut down OED to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt you to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password you want to use with this email to login to OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password so you have access to OED admin features on the web pages. You can run the command docker compose run web npm run editUser to change the password if you forget it or you can create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what you type so this information will be in the terminal. You shouldn&#39;t need this terminal any more so you can close it to hide the information or usually type clear to remove it from what is shown in the terminal. You should now log in to make sure this account works. Logging in directions are available but basically you click the &quot;Log in&quot; button in the top, right of the OED website and then enter the information. Shut down OED. You will soon setting up OED to run as a service so you want to stop the one running in the terminal. In the terminal where you started OED (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. In the following steps you need to know the root directory of OED. In the terminal where you are in the OED root directory do: pwd and the output will tell you the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. You are not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on your system. There is a chance that your version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; you need to set below is the one assigned to OED, the one you logged in as before becoming superuser/root or (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming you want to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless you disable this service with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart when you start the service again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If you want to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes you want to see the output of OED when it is running as a service. This can be useful during the install if you want to see why OED did not come up. You do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where you replace &amp;lt;CONTAINER ID&amp;gt; with the one you want from the previous step. You will want to get meter data into OED so the site can display data. See the data acquisition page for more information on doing this. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, you will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If you see a newer version that you want to upgrade to then consult the directions on the OED Upgrading page. Other information Though less likely, you may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is a node_modules directory in the root OED directory) and skips doing it again to save time. However you can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before you do this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta property="og:url" content="https://openenergydashboard.org/helpV0_7_0/adminInstallation/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoHelp.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/helpV0_7_0/">helpV0_7_0</a> <a class="current">Installation Directions</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Documentation<h1>Installation Directions</h1></header><div class="row"><p>Version V0.7.0<div class="alert-box info "><p>The latest version of this page is <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">V1.0.0</a>.</div><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../admin/'>Documentation overview</a></h4><div><h5>Admin documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/admin/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Site Management</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/adminGroupViewing/">Group</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMap/">Map Management</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMapViewing/">Map Viewing</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMeterViewing/">Meter Viewing</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminPreferences/">Site Settings</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminUser/">User</a></br></div></div><div style="padding-left: 1em;"><h6>Data Acquisition</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/adminCsvImport/">CSV Import</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminDataAcquisition/">Data Acquisition</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMamac/">MAMAC</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminMetersImport/">Meter Import</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminReadingsImport/">Reading Import</a></br></div></div><div style="padding-left: 1em;"><h6>Site Installation</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/adminInstallOutput/">Production Install Output</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminInstallation/">Installation Directions</a></br> <a href="https://openenergydashboard.org/helpV0_7_0/adminUpgrading/">Upgrades</a></br></div></div><h5>User documentation</h5><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_7_0/adminInstallation/../user/">User help</a></br></div><h5>Documentation versions for this page</h5><div style="padding-left: 1em;"> <a href="../../helpV1_0_0/adminInstallation/">V1.0.0</a></br> <a href="../../helpV0_8_0/adminInstallation/">V0.8.0</a></br> V0.7.0 (current page)</br></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user.</div><p>This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the <a href="https://openenergydashboard.org/developer/gettingStarted/">getting started</a> page.<h2>Requirements</h2><p>OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows OS Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The <a href="https://openenergydashboard.org/developer/gettingStarted/">developer getting started page</a> has details on WSL and Docker installation.<p>OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the <code>docker compose</code> command. (Note more recent versions of Docker have the <code>docker compose</code> command so you no longer need <code>docker-compose</code>. If your Docker does not support this (likely see an error with <code>docker compose</code> of "docker: 'compose' is not a docker command.") then you need to install docker-compose and replace all the <code>docker compose</code> commands with <code>docker-compose</code>.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from <a href="https://docs.docker.com/engine/install/" rel="nofollow">Docker</a>.<p>It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation.<p>These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization.<p>This guide requires that you enter some commands into an operating system shell, or terminal.<ul><li>On Windows, this is the terminal that connects to the Linux running under WSL.<li>On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program.<li>On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for "Terminal" in your application menu.</ul><h2>Installation</h2><p>Follow these steps to install a production (OED site for you institution) site:<ol><li><p>Clone the desired OED code from Github. Note if you leave off <code>directory</code> in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use "." for the <code>directory</code> (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone.<ul><li>If you want a specific released version of OED (this is most common) then do: <code>git clone --branch &lt;tag_name&gt; https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. You can find the officially released and tagged versions at the <a href="https://github.com/OpenEnergyDashboard/OED/releases" rel="noopener noreferrer">OED GitHub release page</a>. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: <code>git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git</code>. After this you should see the directory OED where you did the clone.<li>If you want the latest version from development then do: <code>git clone https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base.</ul><li>cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone).<li><p>Edit <code>docker-compose.yml</code>. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are:<ol><li>POSTGRES_PASSWORD (under <code>services: -&gt; datebase: -&gt; environment:</code>) to a site specific password instead of the <code>pleaseChange</code> that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: <code>- POSTGRES_PASSWORD=whateverPasswordYouChoose</code><li>OED_PRODUCTION (under <code>services: -&gt; web: -&gt; environment:</code>) to <code>yes</code> so it becomes: <code>- OED_PRODUCTION=yes</code>.<li>OED_TOKEN_SECRET (under <code>services: -&gt; web: -&gt; environment:</code>) to a random value instead of the <code>?</code> that is provided. Keep it secret but you should never need to know this value. It will be: <code>- OED_TOKEN_SECRET=whateverTokenYouChoose</code><li>The port (in <code>services: -&gt; web: -&gt; ports:</code>) to a mapping from host to container; e.g., to host on your computer's port 80, set it to <code>80:3000</code>. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with <code>#</code>). Before you edit it should look like:<pre><code>
     ports:
         - "3000:3000" # Should be commented out if you uncomment 80:3000 below.
         - "9229:9229" # Debug port, should be commented out for production
diff --git a/helpV0_8_0/adminInstallation/index.html b/helpV0_8_0/adminInstallation/index.html
index 8c7fc1e2..441d3884 100644
--- a/helpV0_8_0/adminInstallation/index.html
+++ b/helpV0_8_0/adminInstallation/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Installation Directions Doc</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Version V0.8.0 The latest version of this page is V1.0.0. Documentation overview Admin documentation Information Overview Site Management Group Map Management Map Viewing Meter Viewing Site Settings User Data Acquisition CSV Import Data Acquisition MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades User documentation User help Documentation versions for this page V1.0.0 V0.8.0 (current page) V0.7.0 These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The beginning of the WSL page has details on WSL and Docker installation on Windows 10 Home. OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. (Note more recent versions of Docker have the docker compose command so you no longer need docker-compose. If your Docker does not support this (likely see an error with docker compose of &quot;docker: &#39;compose&#39; is not a docker command.&quot;) then you need to install docker-compose and replace all the docker compose commands with docker-compose.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization. This guide requires that you enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in your application menu. Installation Follow these steps to install a production (OED site for you institution) site: Clone the desired OED code from Github. Note if you leave off directory in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use &quot;.&quot; for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone. If you want a specific released version of OED (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. You can find the officially released and tagged versions at the OED GitHub release page. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git. After this you should see the directory OED where you did the clone. If you want the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone). Edit docker-compose.yml. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; datebase: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but you should never need to know this value. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) to a mapping from host to container; e.g., to host on your computer&#39;s port 80, set it to 80:3000. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before you edit it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If you want to have standard web requests (port 80) serve up OED then edit to look like (you comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if you leave the line - &quot;3000:3000&quot; uncommented and comment out - &quot;9229:9229&quot; then OED will server up on port 3000 (where you leave the - &quot;80:3000&quot; line commented out). OED_SITE_READING_RATE (under services: -&amp;gt; web: -&amp;gt; environment:) might need to be updated. This represents the typical rate that meters at your site provide data. This impacts when OED switches from daily to hourly to original meter data when doing line graphics. The default value is 00:15:00 meaning the meter data is expected every 15 minutes. If the value is roughly right then there should be no issues. Note you do not change OED_TEST_SITE_READING_RATE as that is used internally for the automated tests in OED. More information is available on the help pages. Later in these directions, it is suggested you set up a cron job to send an email to someone each day with any issues the OED installation encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. To do this you need to set these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP). As the comment says this can be secure-smtp to use your SMTP server or none if you are not going to have OED send mail alerts. OED only supports sending mail via secure channels. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this usually becomes OED_MAIL_METHOD=secure-smtp. OED_MAIL_SMTP gives the web address of the SMTP server you are using. For example, it could be OED_MAIL_SMTP=smtp.example.com where example.com would become the domain for your organization or you could use OED_MAIL_SMTP=smtp.gmail.com for Google Mail. OED_MAIL_SMTP_PORT gives the port number of the SMTP server you are using. For example, it is often OED_MAIL_SMTP_PORT=465 for the standard SSL connection port. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with your user name email. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA) unless you have access to a token for the credential (an app password for mail for Google has been tested and it works). OED_MAIL_FROM give the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where you use the desired email address. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name you want. For the remaining steps you need to be the superuser/root to have sufficient permission to modify system files. On some OS setups you can do the install step (next) without being the superuser but it is generally safer to not to try. Make sure you are in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. (On older versions of Docker you must do docker-compose up.) This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of your server. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while normally happening right after the &quot; database system is ready to accept connections&quot; output line) and starting up the web system. When you see the lines: oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web-1 | oed-web-1 | ℹ ｢atl｣: Time: 24033ms then OED should be ready to accept web requests, where the actual number of hidden modules will likely be different. Note is says is is listening on port 3000 since that is what OED listens on but the ports: changes you made above mean the web requests to port 80 (or whatever you chose) will be sent on to port 3000 for OED. If there was an error in the output then OED might not be running properly. Please contact the OED project if you have questions where sending the terminal text is generally very helpful. If you quickly get the error Invalid interpolation format for &quot;command&quot; option in service &quot;web&quot;: &quot;${install_args:-}&quot; then it is likely you are running an older version of docker-compose (less than version 2). You can fix this error by editing the docker-compose.yml file (as you did above). At the end of the file you will see (Note OED v0.7.0 and earlier does not have the last three lines to deal with older versions of docker compose so you will need to add them during your edits. It also has the reverse proxy line comment that has since been removed.): # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] Edit this to be: # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] If you redo the docker compose up then you should now get the expected output described above. The typical output of the install is available. You can now use a web browser to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where you replace oed.myinstition.org with the name of the server where you installed OED. If all is working properly you will see the main OED page (see Graph Type help page for an image of what it will look like). You won&#39;t be able to graph any data until you have OED acquire meter data. If you did not do the mapping of 80:3000 above, then OED would be reachable at oed.myinstition.org:3000. You now need to create an admin user so you can log into OED on the website. To do this you will need a second terminal where you go to the root OED directory and are a superuser/root (as you have been). This is done so you don&#39;t have to shut down OED to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt you to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password you want to use with this email to login to OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password so you have access to OED admin features on the web pages. You can run the command docker compose run web npm run editUser to change the password if you forget it or you can create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what you type so this information will be in the terminal. You shouldn&#39;t need this terminal any more so you can close it to hide the information or usually type clear to remove it from what is shown in the terminal. You should now log in to make sure this account works. Logging in directions are available but basically you click the &quot;Log in&quot; button in the top, right of the OED website and then enter the information. Shut down OED. You will soon be setting up OED to run as a service so you want to stop the one running in the terminal. In the terminal where you started OED (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. In the following steps you need to know the root directory of OED. In the terminal where you are in the OED root directory do: pwd and the output will tell you the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. You are not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the cron job to aggregate the hourly readings needed for the fast data access OED does to the database when zoomed in on data. The site can choose how frequently to do this. If you want to see the latest meter data quickly then this should be done hourly. Note the update takes a modest amount of CPU and can delay when users see data. If you prefer, you could run the script daily just before running the daily updates. This would mean the new hourly data would only become visible after the day completes. In the root OED directory do (this assumes you do the update every hour): cp src/scripts/refreshHourlyReadingViewsCron.bash /etc/cron.hourly/refreshHourlyReadingViewsCron.bash Edit /etc/cron.daily/refreshHourlyReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail but it should be the same as the daily script changes. Do: chmod +x /etc/cron.hourly/refreshHourlyReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on your system. There is a chance that your version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; you need to set below is the one assigned to OED, the one you logged in as before becoming superuser/root or (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming you want to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless you disable this service with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart when you start the service again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If you want to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes you want to see the output of OED when it is running as a service. This can be useful during the install if you want to see why OED did not come up. You do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where you replace &amp;lt;CONTAINER ID&amp;gt; with the one you want from the previous step. You will want to get meter data into OED so the site can display data. See the data acquisition page for more information on doing this. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, you will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If you see a newer version that you want to upgrade to then consult the directions on the OED Upgrading page. Other information Though less likely, you may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is a node_modules directory in the root OED directory) and skips doing it again to save time. However you can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before you do this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/helpV0_8_0/adminInstallation/"><meta property="og:title" content="Installation Directions Doc"><meta property="og:description" content="Version V0.8.0 The latest version of this page is V1.0.0. Documentation overview Admin documentation Information Overview Site Management Group Map Management Map Viewing Meter Viewing Site Settings User Data Acquisition CSV Import Data Acquisition MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades User documentation User help Documentation versions for this page V1.0.0 V0.8.0 (current page) V0.7.0 These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The beginning of the WSL page has details on WSL and Docker installation on Windows 10 Home. OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. (Note more recent versions of Docker have the docker compose command so you no longer need docker-compose. If your Docker does not support this (likely see an error with docker compose of &quot;docker: &#39;compose&#39; is not a docker command.&quot;) then you need to install docker-compose and replace all the docker compose commands with docker-compose.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization. This guide requires that you enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in your application menu. Installation Follow these steps to install a production (OED site for you institution) site: Clone the desired OED code from Github. Note if you leave off directory in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use &quot;.&quot; for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone. If you want a specific released version of OED (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. You can find the officially released and tagged versions at the OED GitHub release page. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git. After this you should see the directory OED where you did the clone. If you want the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone). Edit docker-compose.yml. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; datebase: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but you should never need to know this value. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) to a mapping from host to container; e.g., to host on your computer&#39;s port 80, set it to 80:3000. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before you edit it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If you want to have standard web requests (port 80) serve up OED then edit to look like (you comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if you leave the line - &quot;3000:3000&quot; uncommented and comment out - &quot;9229:9229&quot; then OED will server up on port 3000 (where you leave the - &quot;80:3000&quot; line commented out). OED_SITE_READING_RATE (under services: -&amp;gt; web: -&amp;gt; environment:) might need to be updated. This represents the typical rate that meters at your site provide data. This impacts when OED switches from daily to hourly to original meter data when doing line graphics. The default value is 00:15:00 meaning the meter data is expected every 15 minutes. If the value is roughly right then there should be no issues. Note you do not change OED_TEST_SITE_READING_RATE as that is used internally for the automated tests in OED. More information is available on the help pages. Later in these directions, it is suggested you set up a cron job to send an email to someone each day with any issues the OED installation encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. To do this you need to set these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP). As the comment says this can be secure-smtp to use your SMTP server or none if you are not going to have OED send mail alerts. OED only supports sending mail via secure channels. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this usually becomes OED_MAIL_METHOD=secure-smtp. OED_MAIL_SMTP gives the web address of the SMTP server you are using. For example, it could be OED_MAIL_SMTP=smtp.example.com where example.com would become the domain for your organization or you could use OED_MAIL_SMTP=smtp.gmail.com for Google Mail. OED_MAIL_SMTP_PORT gives the port number of the SMTP server you are using. For example, it is often OED_MAIL_SMTP_PORT=465 for the standard SSL connection port. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with your user name email. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA) unless you have access to a token for the credential (an app password for mail for Google has been tested and it works). OED_MAIL_FROM give the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where you use the desired email address. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name you want. For the remaining steps you need to be the superuser/root to have sufficient permission to modify system files. On some OS setups you can do the install step (next) without being the superuser but it is generally safer to not to try. Make sure you are in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. (On older versions of Docker you must do docker-compose up.) This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of your server. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while normally happening right after the &quot; database system is ready to accept connections&quot; output line) and starting up the web system. When you see the lines: oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web-1 | oed-web-1 | ℹ ｢atl｣: Time: 24033ms then OED should be ready to accept web requests, where the actual number of hidden modules will likely be different. Note is says is is listening on port 3000 since that is what OED listens on but the ports: changes you made above mean the web requests to port 80 (or whatever you chose) will be sent on to port 3000 for OED. If there was an error in the output then OED might not be running properly. Please contact the OED project if you have questions where sending the terminal text is generally very helpful. If you quickly get the error Invalid interpolation format for &quot;command&quot; option in service &quot;web&quot;: &quot;${install_args:-}&quot; then it is likely you are running an older version of docker-compose (less than version 2). You can fix this error by editing the docker-compose.yml file (as you did above). At the end of the file you will see (Note OED v0.7.0 and earlier does not have the last three lines to deal with older versions of docker compose so you will need to add them during your edits. It also has the reverse proxy line comment that has since been removed.): # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] Edit this to be: # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] If you redo the docker compose up then you should now get the expected output described above. The typical output of the install is available. You can now use a web browser to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where you replace oed.myinstition.org with the name of the server where you installed OED. If all is working properly you will see the main OED page (see Graph Type help page for an image of what it will look like). You won&#39;t be able to graph any data until you have OED acquire meter data. If you did not do the mapping of 80:3000 above, then OED would be reachable at oed.myinstition.org:3000. You now need to create an admin user so you can log into OED on the website. To do this you will need a second terminal where you go to the root OED directory and are a superuser/root (as you have been). This is done so you don&#39;t have to shut down OED to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt you to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password you want to use with this email to login to OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password so you have access to OED admin features on the web pages. You can run the command docker compose run web npm run editUser to change the password if you forget it or you can create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what you type so this information will be in the terminal. You shouldn&#39;t need this terminal any more so you can close it to hide the information or usually type clear to remove it from what is shown in the terminal. You should now log in to make sure this account works. Logging in directions are available but basically you click the &quot;Log in&quot; button in the top, right of the OED website and then enter the information. Shut down OED. You will soon be setting up OED to run as a service so you want to stop the one running in the terminal. In the terminal where you started OED (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. In the following steps you need to know the root directory of OED. In the terminal where you are in the OED root directory do: pwd and the output will tell you the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. You are not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the cron job to aggregate the hourly readings needed for the fast data access OED does to the database when zoomed in on data. The site can choose how frequently to do this. If you want to see the latest meter data quickly then this should be done hourly. Note the update takes a modest amount of CPU and can delay when users see data. If you prefer, you could run the script daily just before running the daily updates. This would mean the new hourly data would only become visible after the day completes. In the root OED directory do (this assumes you do the update every hour): cp src/scripts/refreshHourlyReadingViewsCron.bash /etc/cron.hourly/refreshHourlyReadingViewsCron.bash Edit /etc/cron.daily/refreshHourlyReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail but it should be the same as the daily script changes. Do: chmod +x /etc/cron.hourly/refreshHourlyReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on your system. There is a chance that your version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; you need to set below is the one assigned to OED, the one you logged in as before becoming superuser/root or (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming you want to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless you disable this service with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart when you start the service again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If you want to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes you want to see the output of OED when it is running as a service. This can be useful during the install if you want to see why OED did not come up. You do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where you replace &amp;lt;CONTAINER ID&amp;gt; with the one you want from the previous step. You will want to get meter data into OED so the site can display data. See the data acquisition page for more information on doing this. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, you will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If you see a newer version that you want to upgrade to then consult the directions on the OED Upgrading page. Other information Though less likely, you may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is a node_modules directory in the root OED directory) and skips doing it again to save time. However you can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before you do this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta property="og:url" content="https://openenergydashboard.org/helpV0_8_0/adminInstallation/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoHelp.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/helpV0_8_0/">helpV0_8_0</a> <a class="current">Installation Directions</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Documentation<h1>Installation Directions</h1></header><div class="row"><p>Version V0.8.0<div class="alert-box info "><p>The latest version of this page is <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">V1.0.0</a>.</div><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../admin/'>Documentation overview</a></h4><div><h5>Admin documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/admin/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Site Management</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/adminGroupViewing/">Group</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMap/">Map Management</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMapViewing/">Map Viewing</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMeterViewing/">Meter Viewing</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminPreferences/">Site Settings</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminUser/">User</a></br></div></div><div style="padding-left: 1em;"><h6>Data Acquisition</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/adminCsvImport/">CSV Import</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminDataAcquisition/">Data Acquisition</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMamac/">MAMAC</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMetersImport/">Meter Import</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminReadingsImport/">Reading Import</a></br></div></div><div style="padding-left: 1em;"><h6>Site Installation</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/adminInstallOutput/">Production Install Output</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminInstallation/">Installation Directions</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminUpgrading/">Upgrades</a></br></div></div><h5>User documentation</h5><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/adminInstallation/../user/">User help</a></br></div><h5>Documentation versions for this page</h5><div style="padding-left: 1em;"> <a href="../../helpV1_0_0/adminInstallation/">V1.0.0</a></br> V0.8.0 (current page)</br> <a href="../../helpV0_7_0/adminInstallation/">V0.7.0</a></br></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user.</div><p>This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the <a href="https://openenergydashboard.org/developer/gettingStarted/">getting started</a> page.<h2>Requirements</h2><p>OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The beginning of the <a href="https://openenergydashboard.org/developer/wslSteps/">WSL page</a> has details on WSL and Docker installation on Windows 10 Home.<p>OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the <code>docker compose</code> command. (Note more recent versions of Docker have the <code>docker compose</code> command so you no longer need <code>docker-compose</code>. If your Docker does not support this (likely see an error with <code>docker compose</code> of "docker: 'compose' is not a docker command.") then you need to install docker-compose and replace all the <code>docker compose</code> commands with <code>docker-compose</code>.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from <a href="https://docs.docker.com/engine/install/" rel="nofollow">Docker</a>.<p>It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation.<p>These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization.<p>This guide requires that you enter some commands into an operating system shell, or terminal.<ul><li>On Windows, this is the terminal that connects to the Linux running under WSL.<li>On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program.<li>On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for "Terminal" in your application menu.</ul><h2>Installation</h2><p>Follow these steps to install a production (OED site for you institution) site:<ol><li><p>Clone the desired OED code from Github. Note if you leave off <code>directory</code> in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use "." for the <code>directory</code> (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone.<ul><li>If you want a specific released version of OED (this is most common) then do: <code>git clone --branch &lt;tag_name&gt; https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. You can find the officially released and tagged versions at the <a href="https://github.com/OpenEnergyDashboard/OED/releases" rel="noopener noreferrer">OED GitHub release page</a>. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: <code>git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git</code>. After this you should see the directory OED where you did the clone.<li>If you want the latest version from development then do: <code>git clone https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base.</ul><li>cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone).<li><p>Edit <code>docker-compose.yml</code>. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are:<ol><li>POSTGRES_PASSWORD (under <code>services: -&gt; datebase: -&gt; environment:</code>) to a site specific password instead of the <code>pleaseChange</code> that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: <code>- POSTGRES_PASSWORD=whateverPasswordYouChoose</code><li>OED_PRODUCTION (under <code>services: -&gt; web: -&gt; environment:</code>) to <code>yes</code> so it becomes: <code>- OED_PRODUCTION=yes</code>.<li>OED_TOKEN_SECRET (under <code>services: -&gt; web: -&gt; environment:</code>) to a random value instead of the <code>?</code> that is provided. Keep it secret but you should never need to know this value. It will be: <code>- OED_TOKEN_SECRET=whateverTokenYouChoose</code><li>The port (in <code>services: -&gt; web: -&gt; ports:</code>) to a mapping from host to container; e.g., to host on your computer's port 80, set it to <code>80:3000</code>. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with <code>#</code>). Before you edit it should look like:<pre><code>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Installation Directions Doc</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Version V0.8.0 The latest version of this page is V1.0.0. Documentation overview Admin documentation Information Overview Site Management Group Map Management Map Viewing Meter Viewing Site Settings User Data Acquisition CSV Import Data Acquisition MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades User documentation User help Documentation versions for this page V1.0.0 V0.8.0 (current page) V0.7.0 These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The developer getting started page has details on WSL and Docker installation. OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. (Note more recent versions of Docker have the docker compose command so you no longer need docker-compose. If your Docker does not support this (likely see an error with docker compose of &quot;docker: &#39;compose&#39; is not a docker command.&quot;) then you need to install docker-compose and replace all the docker compose commands with docker-compose.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization. This guide requires that you enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in your application menu. Installation Follow these steps to install a production (OED site for you institution) site: Clone the desired OED code from Github. Note if you leave off directory in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use &quot;.&quot; for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone. If you want a specific released version of OED (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. You can find the officially released and tagged versions at the OED GitHub release page. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git. After this you should see the directory OED where you did the clone. If you want the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone). Edit docker-compose.yml. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; datebase: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but you should never need to know this value. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) to a mapping from host to container; e.g., to host on your computer&#39;s port 80, set it to 80:3000. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before you edit it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If you want to have standard web requests (port 80) serve up OED then edit to look like (you comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if you leave the line - &quot;3000:3000&quot; uncommented and comment out - &quot;9229:9229&quot; then OED will server up on port 3000 (where you leave the - &quot;80:3000&quot; line commented out). OED_SITE_READING_RATE (under services: -&amp;gt; web: -&amp;gt; environment:) might need to be updated. This represents the typical rate that meters at your site provide data. This impacts when OED switches from daily to hourly to original meter data when doing line graphics. The default value is 00:15:00 meaning the meter data is expected every 15 minutes. If the value is roughly right then there should be no issues. Note you do not change OED_TEST_SITE_READING_RATE as that is used internally for the automated tests in OED. More information is available on the help pages. Later in these directions, it is suggested you set up a cron job to send an email to someone each day with any issues the OED installation encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. To do this you need to set these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP). As the comment says this can be secure-smtp to use your SMTP server or none if you are not going to have OED send mail alerts. OED only supports sending mail via secure channels. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this usually becomes OED_MAIL_METHOD=secure-smtp. OED_MAIL_SMTP gives the web address of the SMTP server you are using. For example, it could be OED_MAIL_SMTP=smtp.example.com where example.com would become the domain for your organization or you could use OED_MAIL_SMTP=smtp.gmail.com for Google Mail. OED_MAIL_SMTP_PORT gives the port number of the SMTP server you are using. For example, it is often OED_MAIL_SMTP_PORT=465 for the standard SSL connection port. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with your user name email. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA) unless you have access to a token for the credential (an app password for mail for Google has been tested and it works). OED_MAIL_FROM give the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where you use the desired email address. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name you want. For the remaining steps you need to be the superuser/root to have sufficient permission to modify system files. On some OS setups you can do the install step (next) without being the superuser but it is generally safer to not to try. Make sure you are in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. (On older versions of Docker you must do docker-compose up.) This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of your server. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while normally happening right after the &quot; database system is ready to accept connections&quot; output line) and starting up the web system. When you see the lines: oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web-1 | oed-web-1 | ℹ ｢atl｣: Time: 24033ms then OED should be ready to accept web requests, where the actual number of hidden modules will likely be different. Note is says is is listening on port 3000 since that is what OED listens on but the ports: changes you made above mean the web requests to port 80 (or whatever you chose) will be sent on to port 3000 for OED. If there was an error in the output then OED might not be running properly. Please contact the OED project if you have questions where sending the terminal text is generally very helpful. If you quickly get the error Invalid interpolation format for &quot;command&quot; option in service &quot;web&quot;: &quot;${install_args:-}&quot; then it is likely you are running an older version of docker-compose (less than version 2). You can fix this error by editing the docker-compose.yml file (as you did above). At the end of the file you will see (Note OED v0.7.0 and earlier does not have the last three lines to deal with older versions of docker compose so you will need to add them during your edits. It also has the reverse proxy line comment that has since been removed.): # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] Edit this to be: # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] If you redo the docker compose up then you should now get the expected output described above. The typical output of the install is available. You can now use a web browser to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where you replace oed.myinstition.org with the name of the server where you installed OED. If all is working properly you will see the main OED page (see Graph Type help page for an image of what it will look like). You won&#39;t be able to graph any data until you have OED acquire meter data. If you did not do the mapping of 80:3000 above, then OED would be reachable at oed.myinstition.org:3000. You now need to create an admin user so you can log into OED on the website. To do this you will need a second terminal where you go to the root OED directory and are a superuser/root (as you have been). This is done so you don&#39;t have to shut down OED to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt you to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password you want to use with this email to login to OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password so you have access to OED admin features on the web pages. You can run the command docker compose run web npm run editUser to change the password if you forget it or you can create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what you type so this information will be in the terminal. You shouldn&#39;t need this terminal any more so you can close it to hide the information or usually type clear to remove it from what is shown in the terminal. You should now log in to make sure this account works. Logging in directions are available but basically you click the &quot;Log in&quot; button in the top, right of the OED website and then enter the information. Shut down OED. You will soon be setting up OED to run as a service so you want to stop the one running in the terminal. In the terminal where you started OED (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. In the following steps you need to know the root directory of OED. In the terminal where you are in the OED root directory do: pwd and the output will tell you the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. You are not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the cron job to aggregate the hourly readings needed for the fast data access OED does to the database when zoomed in on data. The site can choose how frequently to do this. If you want to see the latest meter data quickly then this should be done hourly. Note the update takes a modest amount of CPU and can delay when users see data. If you prefer, you could run the script daily just before running the daily updates. This would mean the new hourly data would only become visible after the day completes. In the root OED directory do (this assumes you do the update every hour): cp src/scripts/refreshHourlyReadingViewsCron.bash /etc/cron.hourly/refreshHourlyReadingViewsCron.bash Edit /etc/cron.daily/refreshHourlyReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail but it should be the same as the daily script changes. Do: chmod +x /etc/cron.hourly/refreshHourlyReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on your system. There is a chance that your version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; you need to set below is the one assigned to OED, the one you logged in as before becoming superuser/root or (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming you want to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless you disable this service with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart when you start the service again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If you want to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes you want to see the output of OED when it is running as a service. This can be useful during the install if you want to see why OED did not come up. You do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where you replace &amp;lt;CONTAINER ID&amp;gt; with the one you want from the previous step. You will want to get meter data into OED so the site can display data. See the data acquisition page for more information on doing this. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, you will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If you see a newer version that you want to upgrade to then consult the directions on the OED Upgrading page. Other information Though less likely, you may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is a node_modules directory in the root OED directory) and skips doing it again to save time. However you can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before you do this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/helpV0_8_0/adminInstallation/"><meta property="og:title" content="Installation Directions Doc"><meta property="og:description" content="Version V0.8.0 The latest version of this page is V1.0.0. Documentation overview Admin documentation Information Overview Site Management Group Map Management Map Viewing Meter Viewing Site Settings User Data Acquisition CSV Import Data Acquisition MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades User documentation User help Documentation versions for this page V1.0.0 V0.8.0 (current page) V0.7.0 These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The developer getting started page has details on WSL and Docker installation. OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. (Note more recent versions of Docker have the docker compose command so you no longer need docker-compose. If your Docker does not support this (likely see an error with docker compose of &quot;docker: &#39;compose&#39; is not a docker command.&quot;) then you need to install docker-compose and replace all the docker compose commands with docker-compose.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization. This guide requires that you enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in your application menu. Installation Follow these steps to install a production (OED site for you institution) site: Clone the desired OED code from Github. Note if you leave off directory in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use &quot;.&quot; for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone. If you want a specific released version of OED (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. You can find the officially released and tagged versions at the OED GitHub release page. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git. After this you should see the directory OED where you did the clone. If you want the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone). Edit docker-compose.yml. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; datebase: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but you should never need to know this value. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) to a mapping from host to container; e.g., to host on your computer&#39;s port 80, set it to 80:3000. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before you edit it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If you want to have standard web requests (port 80) serve up OED then edit to look like (you comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if you leave the line - &quot;3000:3000&quot; uncommented and comment out - &quot;9229:9229&quot; then OED will server up on port 3000 (where you leave the - &quot;80:3000&quot; line commented out). OED_SITE_READING_RATE (under services: -&amp;gt; web: -&amp;gt; environment:) might need to be updated. This represents the typical rate that meters at your site provide data. This impacts when OED switches from daily to hourly to original meter data when doing line graphics. The default value is 00:15:00 meaning the meter data is expected every 15 minutes. If the value is roughly right then there should be no issues. Note you do not change OED_TEST_SITE_READING_RATE as that is used internally for the automated tests in OED. More information is available on the help pages. Later in these directions, it is suggested you set up a cron job to send an email to someone each day with any issues the OED installation encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. To do this you need to set these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP). As the comment says this can be secure-smtp to use your SMTP server or none if you are not going to have OED send mail alerts. OED only supports sending mail via secure channels. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this usually becomes OED_MAIL_METHOD=secure-smtp. OED_MAIL_SMTP gives the web address of the SMTP server you are using. For example, it could be OED_MAIL_SMTP=smtp.example.com where example.com would become the domain for your organization or you could use OED_MAIL_SMTP=smtp.gmail.com for Google Mail. OED_MAIL_SMTP_PORT gives the port number of the SMTP server you are using. For example, it is often OED_MAIL_SMTP_PORT=465 for the standard SSL connection port. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with your user name email. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA) unless you have access to a token for the credential (an app password for mail for Google has been tested and it works). OED_MAIL_FROM give the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where you use the desired email address. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name you want. For the remaining steps you need to be the superuser/root to have sufficient permission to modify system files. On some OS setups you can do the install step (next) without being the superuser but it is generally safer to not to try. Make sure you are in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. (On older versions of Docker you must do docker-compose up.) This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of your server. You will see a lot of output about installing the database (Postgres), getting needed packages (this can take a while so you may not see output for a while normally happening right after the &quot; database system is ready to accept connections&quot; output line) and starting up the web system. When you see the lines: oed-web-1 | &amp;lt;s&amp;gt; [webpack.Progress] 100% oed-web-1 | oed-web-1 | ℹ ｢atl｣: Time: 24033ms then OED should be ready to accept web requests, where the actual number of hidden modules will likely be different. Note is says is is listening on port 3000 since that is what OED listens on but the ports: changes you made above mean the web requests to port 80 (or whatever you chose) will be sent on to port 3000 for OED. If there was an error in the output then OED might not be running properly. Please contact the OED project if you have questions where sending the terminal text is generally very helpful. If you quickly get the error Invalid interpolation format for &quot;command&quot; option in service &quot;web&quot;: &quot;${install_args:-}&quot; then it is likely you are running an older version of docker-compose (less than version 2). You can fix this error by editing the docker-compose.yml file (as you did above). At the end of the file you will see (Note OED v0.7.0 and earlier does not have the last three lines to deal with older versions of docker compose so you will need to add them during your edits. It also has the reverse proxy line comment that has since been removed.): # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] Edit this to be: # Lets docker-compose up work right # If environment variable install_args is not set the it becomes blank without warning user. # command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;, &quot;${install_args:-}&quot;] # Use this if you are using a docker-compose that is earlier than version 2 and comment out the one above. command: [&quot;bash&quot;, &quot;./src/scripts/installOED.sh&quot;] If you redo the docker compose up then you should now get the expected output described above. The typical output of the install is available. You can now use a web browser to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where you replace oed.myinstition.org with the name of the server where you installed OED. If all is working properly you will see the main OED page (see Graph Type help page for an image of what it will look like). You won&#39;t be able to graph any data until you have OED acquire meter data. If you did not do the mapping of 80:3000 above, then OED would be reachable at oed.myinstition.org:3000. You now need to create an admin user so you can log into OED on the website. To do this you will need a second terminal where you go to the root OED directory and are a superuser/root (as you have been). This is done so you don&#39;t have to shut down OED to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt you to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password you want to use with this email to login to OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password so you have access to OED admin features on the web pages. You can run the command docker compose run web npm run editUser to change the password if you forget it or you can create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what you type so this information will be in the terminal. You shouldn&#39;t need this terminal any more so you can close it to hide the information or usually type clear to remove it from what is shown in the terminal. You should now log in to make sure this account works. Logging in directions are available but basically you click the &quot;Log in&quot; button in the top, right of the OED website and then enter the information. Shut down OED. You will soon be setting up OED to run as a service so you want to stop the one running in the terminal. In the terminal where you started OED (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. In the following steps you need to know the root directory of OED. In the terminal where you are in the OED root directory do: pwd and the output will tell you the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. You are not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the cron job to aggregate the hourly readings needed for the fast data access OED does to the database when zoomed in on data. The site can choose how frequently to do this. If you want to see the latest meter data quickly then this should be done hourly. Note the update takes a modest amount of CPU and can delay when users see data. If you prefer, you could run the script daily just before running the daily updates. This would mean the new hourly data would only become visible after the day completes. In the root OED directory do (this assumes you do the update every hour): cp src/scripts/refreshHourlyReadingViewsCron.bash /etc/cron.hourly/refreshHourlyReadingViewsCron.bash Edit /etc/cron.daily/refreshHourlyReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail but it should be the same as the daily script changes. Do: chmod +x /etc/cron.hourly/refreshHourlyReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on your system. There is a chance that your version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; you need to set below is the one assigned to OED, the one you logged in as before becoming superuser/root or (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming you want to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless you disable this service with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart when you start the service again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If you want to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes you want to see the output of OED when it is running as a service. This can be useful during the install if you want to see why OED did not come up. You do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where you replace &amp;lt;CONTAINER ID&amp;gt; with the one you want from the previous step. You will want to get meter data into OED so the site can display data. See the data acquisition page for more information on doing this. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, you will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If you see a newer version that you want to upgrade to then consult the directions on the OED Upgrading page. Other information Though less likely, you may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is a node_modules directory in the root OED directory) and skips doing it again to save time. However you can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before you do this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta property="og:url" content="https://openenergydashboard.org/helpV0_8_0/adminInstallation/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoHelp.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/helpV0_8_0/">helpV0_8_0</a> <a class="current">Installation Directions</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Documentation<h1>Installation Directions</h1></header><div class="row"><p>Version V0.8.0<div class="alert-box info "><p>The latest version of this page is <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">V1.0.0</a>.</div><div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../admin/'>Documentation overview</a></h4><div><h5>Admin documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/admin/">Overview</a></br></div></div><div style="padding-left: 1em;"><h6>Site Management</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/adminGroupViewing/">Group</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMap/">Map Management</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMapViewing/">Map Viewing</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMeterViewing/">Meter Viewing</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminPreferences/">Site Settings</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminUser/">User</a></br></div></div><div style="padding-left: 1em;"><h6>Data Acquisition</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/adminCsvImport/">CSV Import</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminDataAcquisition/">Data Acquisition</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMamac/">MAMAC</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminMetersImport/">Meter Import</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminReadingsImport/">Reading Import</a></br></div></div><div style="padding-left: 1em;"><h6>Site Installation</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/adminInstallOutput/">Production Install Output</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminInstallation/">Installation Directions</a></br> <a href="https://openenergydashboard.org/helpV0_8_0/adminUpgrading/">Upgrades</a></br></div></div><h5>User documentation</h5><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV0_8_0/adminInstallation/../user/">User help</a></br></div><h5>Documentation versions for this page</h5><div style="padding-left: 1em;"> <a href="../../helpV1_0_0/adminInstallation/">V1.0.0</a></br> V0.8.0 (current page)</br> <a href="../../helpV0_7_0/adminInstallation/">V0.7.0</a></br></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user.</div><p>This describes the installation of an OED site for production use. If you are a developer, you likely want to follow the directions on the <a href="https://openenergydashboard.org/developer/gettingStarted/">getting started</a> page.<h2>Requirements</h2><p>OED uses Unix, including Linux, features to work. Mac-OS X is based on Unix and Docker can be installed directly as an application. Windows OS is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume your system is at that level of Windows (and use the OS name Windows 10). If you have Windows 10 Professional, Enterprise or Education, you should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If you have Windows 10 Home then you can use WSL 2 to enable Linux and then install Docker. Once you have Docker installed and working, you can follow the direction given here since they only depend on Docker/docker compose. The <a href="https://openenergydashboard.org/developer/gettingStarted/">developer getting started page</a> has details on WSL and Docker installation.<p>OED is installed using the Docker containerization tool. This allows it to be segregated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the <code>docker compose</code> command. (Note more recent versions of Docker have the <code>docker compose</code> command so you no longer need <code>docker-compose</code>. If your Docker does not support this (likely see an error with <code>docker compose</code> of "docker: 'compose' is not a docker command.") then you need to install docker-compose and replace all the <code>docker compose</code> commands with <code>docker-compose</code>.) You will need Docker version 18.06 CE or higher but that should not be an issue if you have any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home you can see the link on the WSL page given in the previous step. General Docker installation information is available from <a href="https://docs.docker.com/engine/install/" rel="nofollow">Docker</a>.<p>It is assumed that your server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless you change the default OED port). It is also assumed the server can access the internet for the installation.<p>These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of your organization.<p>This guide requires that you enter some commands into an operating system shell, or terminal.<ul><li>On Windows, this is the terminal that connects to the Linux running under WSL.<li>On MacOS, you can use Terminal.app (the default), iTerm2, or any other terminal program.<li>On Linux, your distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for "Terminal" in your application menu.</ul><h2>Installation</h2><p>Follow these steps to install a production (OED site for you institution) site:<ol><li><p>Clone the desired OED code from Github. Note if you leave off <code>directory</code> in the next step then the OED code will be placed in the current directory in the subdirectory OED. If you use "." for the <code>directory</code> (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. You can place the OED software anywhere you want but be sure to be in the desired directory before you begin the clone.<ul><li>If you want a specific released version of OED (this is most common) then do: <code>git clone --branch &lt;tag_name&gt; https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. You can find the officially released and tagged versions at the <a href="https://github.com/OpenEnergyDashboard/OED/releases" rel="noopener noreferrer">OED GitHub release page</a>. In general, you should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v0.7.0 in the subdirectory OED of the current directory do: <code>git clone --branch v0.7.0 https://github.com/OpenEnergyDashboard/OED.git</code>. After this you should see the directory OED where you did the clone.<li>If you want the latest version from development then do: <code>git clone https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. Note this will likely be code that has yet gone through complete testing as done for an official release version but will have the latest OED code base.</ul><li>cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. What follows assumes you are in the root directory of OED (as is the default when you clone).<li><p>Edit <code>docker-compose.yml</code>. Note that for values with an = you should not put spaces before or after the equal sign as is shown in the sample value. The edits are:<ol><li>POSTGRES_PASSWORD (under <code>services: -&gt; datebase: -&gt; environment:</code>) to a site specific password instead of the <code>pleaseChange</code> that is provided. Keep it secret but you should never need to know this value unless you want to access the PostgreSQL database outside of the docker container. It will be: <code>- POSTGRES_PASSWORD=whateverPasswordYouChoose</code><li>OED_PRODUCTION (under <code>services: -&gt; web: -&gt; environment:</code>) to <code>yes</code> so it becomes: <code>- OED_PRODUCTION=yes</code>.<li>OED_TOKEN_SECRET (under <code>services: -&gt; web: -&gt; environment:</code>) to a random value instead of the <code>?</code> that is provided. Keep it secret but you should never need to know this value. It will be: <code>- OED_TOKEN_SECRET=whateverTokenYouChoose</code><li>The port (in <code>services: -&gt; web: -&gt; ports:</code>) to a mapping from host to container; e.g., to host on your computer's port 80, set it to <code>80:3000</code>. This assumes you want to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with <code>#</code>). Before you edit it should look like:<pre><code>
     ports:
         - "3000:3000" # Should be commented out if you uncomment 80:3000 below.
         - "9229:9229" # Debug port, should be commented out for production
diff --git a/helpV1_0_0/adminInstallation/index.html b/helpV1_0_0/adminInstallation/index.html
index 040efc0b..bc0bb911 100644
--- a/helpV1_0_0/adminInstallation/index.html
+++ b/helpV1_0_0/adminInstallation/index.html
@@ -1,4 +1,4 @@
-<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Installation Directions Doc</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Version V1.0.0 Documentation overview Admin documentation Information Overview Standard Units Pages Units &amp; Conversions Site Management Conversion Creating Conversion Editing Conversion Viewing Group Creating Group Editing Group Map Creating Map Viewing Meter Creating Meter Editing Meter Viewing Site Settings Unit Creating Unit Editing Unit Viewing User Data Acquisition CSV Import Data Acquisition eGauge MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades Upgrades V1.0.0 User documentation User help Documentation versions for this page V1.0.0 (current page) V0.8.0 V0.7.0 These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If one is a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work and run Docker. Most sites have servers running Unix/Linux and can directly run OED. MacOS is based on Unix and Docker can be installed directly as an application. Windows from Microsoft is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume the system is at that level of Windows. If one has Windows 10/11 Professional, Enterprise or Education, one should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If one has Windows 10/11 Home then one can use WSL 2 to enable Linux and then install Docker. Once Docker is installed and working, one can follow the direction given here since they only depend on Docker/docker compose. The beginning of the WSL page has details on WSL and Docker installation on Windows 10/11 Home. OED is installed using the Docker containerization tool. This allows it to be isolated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. One will need Docker version 19.03 or higher (since July 2019) but that should not be an issue if running any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home one can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that the server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless the default OED port is changed). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of an organization. This guide requires that one enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, one can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, the distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in the application menu. Installation Follow these steps to install a production (OED site for an organization) site: Clone the desired OED code from Github. Note if the directory is left off in the next step then the OED code will be placed in the current directory in the subdirectory OED. If &quot;.&quot; is used for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. The OED software can be placed anywhere desired but the terminal should be using the desired directory before beginning the clone of the OED software. If a specific released version of OED is desired (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. The officially released and tagged versions at the OED GitHub release page list all OED releases. In general, a site should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v1.0.0 in the subdirectory OED of the current directory do: git clone --branch v1.0.0 https://github.com/OpenEnergyDashboard/OED.git. After this there should be the directory OED where the clone was done. If a site wants the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has not yet gone through complete testing as done for an official release version but will have the latest OED code base. In general, production sites do not use this code. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. Edit docker-compose.yml. Note that for values with an = one should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; database: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but it should never need to known unless one wants to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but it should never need to known. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) for mapping from host to container; e.g., to host on the server&#39;s port 80, set it to 80:3000. This assumes the site wants to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before editing it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If the site wants to have standard web requests (port 80) serve up OED then edit to look like (comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if the line - &quot;3000:3000&quot; is uncommented and the line - &quot;9229:9229&quot; is commented out then OED will server up on port 3000 (where the line - &quot;80:3000&quot; is commented out). Later in these directions, it is suggested to set up a cron job to send an email to someone each day with any issues the OED installation encountered. No email is sent unless an issue is encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. This is done by setting these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP). As the comment says this can be secure-smtp to use an SMTP server or none if the site is not going to have OED send mail alerts. OED only supports sending mail via secure channels. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this usually becomes OED_MAIL_METHOD=secure-smtp. OED_MAIL_SMTP gives the web address of the SMTP server for sending mail. For example, it could be OED_MAIL_SMTP=smtp.example.com where example.com would become the domain for your organization or one could use OED_MAIL_SMTP=smtp.gmail.com for Google Mail. OED_MAIL_SMTP_PORT gives the port number of the SMTP server for sending mail. For example, it is often OED_MAIL_SMTP_PORT=465 for the standard SSL connection port. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with the user name email for sending mail. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA) unless given a token for the credential (an app password for mail for Google has been tested and it works). OED_MAIL_FROM gives the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where the desired email address is used. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name is desired. For the remaining steps one needs to be the superuser/root to have sufficient permission to modify system files. Some OS setups allow the install step (next) without being the superuser but it is generally safer not to try. Make sure the terminal is in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of the server. The terminal will display a lot of output about installing the database (Postgres), getting needed packages (this can take a while so during this process there may not be more output for a while; this normally happens right after the &quot;database system is ready to accept connections&quot; output line) and starting up the web system (this can take a while so during this process there may not be more output for a while; this normally happens right after the &quot;webpack build --node-env production&quot; output line). Future builds will go much faster. When the terminal displays the lines: oed-web-1 | webpack 5.76.0 compiled successfully in 200210 ms oed-web-1 | OED install finished oed-web-1 | Starting OED in production mode oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 start oed-web-1 | &gt; node ./src/bin/www oed-web-1 | oed-web-1 | [INFO@2023-10-20T11:22:35.803-05:00] Listening on port 3000 then OED should be ready to accept web requests. If there was an error in the output then OED might not be running properly. Please contact the OED project if there are questions where sending the terminal text is generally very helpful. The typical output of the install is available. A web browser can now be used to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where oed.myinstition.org is replaced with the name of the server where OED is installed. If all is working properly, the main OED page (see Home Navigation documentation page for an image of what it will look like). The page won&#39;t be able to graph any data until the site has OED acquire meter data. If the mapping of 80:3000 was not done above, then OED would be reachable at oed.myinstition.org:3000. The site now needs to create an admin user to log into OED on the website. To do this, a second terminal is opened, go to the root OED directory and become a superuser/root user (as has been done). This is done so OED remains running in the first terminal to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password desired to use with this email to login into OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password to access with OED admin features on the web pages. Run the command docker compose run web npm run editUser to change the password if forgotten or to create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what is typed so this information will be in the terminal. This terminal shouldn&#39;t be needed any more so it can be closed to hide the information or usually type clear to remove it from what is shown in the terminal. Now log in on the OED web page to make sure this account works. The options menu documentation is available but basically just click the &quot;Log in&quot; choice in the top, right of the OED website under &quot;Options&quot; and then enter the information. Shut down OED. Soon OED will be set up to run as a service so the OED currently running in the terminal should be shut down. In the terminal where OED was started (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. The following steps require knowledge of the root directory path of OED. In the terminal located in the OED root directory do: pwd and the output will tell the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. It is not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the cron job to aggregate the hourly readings needed for the fast data access OED does to the database when zoomed in on data. The site can choose how frequently to do this. If the site wants to see the latest meter data quickly then this should be done hourly. Note the update takes a modest amount of CPU and can delay when users see data. If preferred, the site could run the script daily just before running the daily updates. This would mean the new hourly data would only become visible after the day completes. However, sites generally do not have issues with doing this every hour so it is normally done. In the root OED directory do (this assumes the site updates every hour): cp src/scripts/refreshHourlyReadingViewsCron.bash /etc/cron.hourly/refreshHourlyReadingViewsCron.bash Edit /etc/cron.daily/refreshHourlyReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail but it should be the same as the daily script changes. Do: chmod +x /etc/cron.hourly/refreshHourlyReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on the server. There is a chance that the server version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; needed to set below is the one assigned to OED. It is the one logged into the terminal before becoming superuser/root and (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming the site wants to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless this service is disabled with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart whenever the service is started again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If one wants to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes one wants to see the output of OED when it is running as a service. This can be useful during the install to see why OED did not come up. Do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where &amp;lt;CONTAINER ID&amp;gt; is replaced with the value from the previous step. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, a site will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If a newer version is desired then upgrade to it. Consult the directions on the OED Upgrading page. Admin setup The designated admin can use the login created above to set the desired features and items of OED. The following may be desired where the links can be used to get more information: Site preferences. Allows for setting of the site name, default actions on the graphic pages, creating other users, and certain limits among other things. data acquisition. Discusses getting meter data into OED so the site can display data. Standard units and conversions. Discusses the units and conversions provided by OED and making more of them visible to the user. Users. To create additional user logins and manage them. Admin features. Discusses the range of actions that admins can take and the related documentation pages. There are many OED features other than the ones linked directly above. Other information Though less likely, one may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is an up-to-date node_modules directory in the root OED directory) and skips doing it again to save time. However, a site can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before doing this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/"><meta property="og:title" content="Installation Directions Doc"><meta property="og:description" content="Version V1.0.0 Documentation overview Admin documentation Information Overview Standard Units Pages Units &amp; Conversions Site Management Conversion Creating Conversion Editing Conversion Viewing Group Creating Group Editing Group Map Creating Map Viewing Meter Creating Meter Editing Meter Viewing Site Settings Unit Creating Unit Editing Unit Viewing User Data Acquisition CSV Import Data Acquisition eGauge MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades Upgrades V1.0.0 User documentation User help Documentation versions for this page V1.0.0 (current page) V0.8.0 V0.7.0 These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If one is a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work and run Docker. Most sites have servers running Unix/Linux and can directly run OED. MacOS is based on Unix and Docker can be installed directly as an application. Windows from Microsoft is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume the system is at that level of Windows. If one has Windows 10/11 Professional, Enterprise or Education, one should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If one has Windows 10/11 Home then one can use WSL 2 to enable Linux and then install Docker. Once Docker is installed and working, one can follow the direction given here since they only depend on Docker/docker compose. The beginning of the WSL page has details on WSL and Docker installation on Windows 10/11 Home. OED is installed using the Docker containerization tool. This allows it to be isolated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. One will need Docker version 19.03 or higher (since July 2019) but that should not be an issue if running any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home one can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that the server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless the default OED port is changed). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of an organization. This guide requires that one enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, one can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, the distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in the application menu. Installation Follow these steps to install a production (OED site for an organization) site: Clone the desired OED code from Github. Note if the directory is left off in the next step then the OED code will be placed in the current directory in the subdirectory OED. If &quot;.&quot; is used for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. The OED software can be placed anywhere desired but the terminal should be using the desired directory before beginning the clone of the OED software. If a specific released version of OED is desired (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. The officially released and tagged versions at the OED GitHub release page list all OED releases. In general, a site should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v1.0.0 in the subdirectory OED of the current directory do: git clone --branch v1.0.0 https://github.com/OpenEnergyDashboard/OED.git. After this there should be the directory OED where the clone was done. If a site wants the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has not yet gone through complete testing as done for an official release version but will have the latest OED code base. In general, production sites do not use this code. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. Edit docker-compose.yml. Note that for values with an = one should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; database: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but it should never need to known unless one wants to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but it should never need to known. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) for mapping from host to container; e.g., to host on the server&#39;s port 80, set it to 80:3000. This assumes the site wants to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before editing it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If the site wants to have standard web requests (port 80) serve up OED then edit to look like (comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if the line - &quot;3000:3000&quot; is uncommented and the line - &quot;9229:9229&quot; is commented out then OED will server up on port 3000 (where the line - &quot;80:3000&quot; is commented out). Later in these directions, it is suggested to set up a cron job to send an email to someone each day with any issues the OED installation encountered. No email is sent unless an issue is encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. This is done by setting these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP). As the comment says this can be secure-smtp to use an SMTP server or none if the site is not going to have OED send mail alerts. OED only supports sending mail via secure channels. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this usually becomes OED_MAIL_METHOD=secure-smtp. OED_MAIL_SMTP gives the web address of the SMTP server for sending mail. For example, it could be OED_MAIL_SMTP=smtp.example.com where example.com would become the domain for your organization or one could use OED_MAIL_SMTP=smtp.gmail.com for Google Mail. OED_MAIL_SMTP_PORT gives the port number of the SMTP server for sending mail. For example, it is often OED_MAIL_SMTP_PORT=465 for the standard SSL connection port. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with the user name email for sending mail. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA) unless given a token for the credential (an app password for mail for Google has been tested and it works). OED_MAIL_FROM gives the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where the desired email address is used. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name is desired. For the remaining steps one needs to be the superuser/root to have sufficient permission to modify system files. Some OS setups allow the install step (next) without being the superuser but it is generally safer not to try. Make sure the terminal is in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of the server. The terminal will display a lot of output about installing the database (Postgres), getting needed packages (this can take a while so during this process there may not be more output for a while; this normally happens right after the &quot;database system is ready to accept connections&quot; output line) and starting up the web system (this can take a while so during this process there may not be more output for a while; this normally happens right after the &quot;webpack build --node-env production&quot; output line). Future builds will go much faster. When the terminal displays the lines: oed-web-1 | webpack 5.76.0 compiled successfully in 200210 ms oed-web-1 | OED install finished oed-web-1 | Starting OED in production mode oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 start oed-web-1 | &gt; node ./src/bin/www oed-web-1 | oed-web-1 | [INFO@2023-10-20T11:22:35.803-05:00] Listening on port 3000 then OED should be ready to accept web requests. If there was an error in the output then OED might not be running properly. Please contact the OED project if there are questions where sending the terminal text is generally very helpful. The typical output of the install is available. A web browser can now be used to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where oed.myinstition.org is replaced with the name of the server where OED is installed. If all is working properly, the main OED page (see Home Navigation documentation page for an image of what it will look like). The page won&#39;t be able to graph any data until the site has OED acquire meter data. If the mapping of 80:3000 was not done above, then OED would be reachable at oed.myinstition.org:3000. The site now needs to create an admin user to log into OED on the website. To do this, a second terminal is opened, go to the root OED directory and become a superuser/root user (as has been done). This is done so OED remains running in the first terminal to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password desired to use with this email to login into OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password to access with OED admin features on the web pages. Run the command docker compose run web npm run editUser to change the password if forgotten or to create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what is typed so this information will be in the terminal. This terminal shouldn&#39;t be needed any more so it can be closed to hide the information or usually type clear to remove it from what is shown in the terminal. Now log in on the OED web page to make sure this account works. The options menu documentation is available but basically just click the &quot;Log in&quot; choice in the top, right of the OED website under &quot;Options&quot; and then enter the information. Shut down OED. Soon OED will be set up to run as a service so the OED currently running in the terminal should be shut down. In the terminal where OED was started (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. The following steps require knowledge of the root directory path of OED. In the terminal located in the OED root directory do: pwd and the output will tell the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. It is not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the cron job to aggregate the hourly readings needed for the fast data access OED does to the database when zoomed in on data. The site can choose how frequently to do this. If the site wants to see the latest meter data quickly then this should be done hourly. Note the update takes a modest amount of CPU and can delay when users see data. If preferred, the site could run the script daily just before running the daily updates. This would mean the new hourly data would only become visible after the day completes. However, sites generally do not have issues with doing this every hour so it is normally done. In the root OED directory do (this assumes the site updates every hour): cp src/scripts/refreshHourlyReadingViewsCron.bash /etc/cron.hourly/refreshHourlyReadingViewsCron.bash Edit /etc/cron.daily/refreshHourlyReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail but it should be the same as the daily script changes. Do: chmod +x /etc/cron.hourly/refreshHourlyReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on the server. There is a chance that the server version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; needed to set below is the one assigned to OED. It is the one logged into the terminal before becoming superuser/root and (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming the site wants to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless this service is disabled with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart whenever the service is started again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If one wants to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes one wants to see the output of OED when it is running as a service. This can be useful during the install to see why OED did not come up. Do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where &amp;lt;CONTAINER ID&amp;gt; is replaced with the value from the previous step. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, a site will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If a newer version is desired then upgrade to it. Consult the directions on the OED Upgrading page. Admin setup The designated admin can use the login created above to set the desired features and items of OED. The following may be desired where the links can be used to get more information: Site preferences. Allows for setting of the site name, default actions on the graphic pages, creating other users, and certain limits among other things. data acquisition. Discusses getting meter data into OED so the site can display data. Standard units and conversions. Discusses the units and conversions provided by OED and making more of them visible to the user. Users. To create additional user logins and manage them. Admin features. Discusses the range of actions that admins can take and the related documentation pages. There are many OED features other than the ones linked directly above. Other information Though less likely, one may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is an up-to-date node_modules directory in the root OED directory) and skips doing it again to save time. However, a site can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before doing this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta property="og:url" content="https://openenergydashboard.org/helpV1_0_0/adminInstallation/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoHelp.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/helpV1_0_0/">helpV1_0_0</a> <a class="current">Installation Directions</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Documentation<h1>Installation Directions</h1></header><div class="row"><p>Version V1.0.0<div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../admin/'>Documentation overview</a></h4><div><h5>Admin documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/admin/">Overview</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminOedUnits/">Standard Units</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminPageChoices/">Pages</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUnitInfo/">Units & Conversions</a></br></div></div><div style="padding-left: 1em;"><h6>Site Management</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/adminConversionCreating/">Conversion Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminConversionEditing/">Conversion Editing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminConversionViewing/">Conversion Viewing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminGroupCreating/">Group Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminGroupEditing/">Group Editing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminGroupViewing/">Group</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMapCreating/">Map Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMapViewing/">Map Viewing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMeterCreating/">Meter Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMeterEditing/">Meter Editing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMeterViewing/">Meter Viewing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminPreferences/">Site Settings</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUnitCreating/">Unit Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUnitEditing/">Unit Editing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUnitViewing/">Unit Viewing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUser/">User</a></br></div></div><div style="padding-left: 1em;"><h6>Data Acquisition</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/adminCsvImport/">CSV Import</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminDataAcquisition/">Data Acquisition</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminEgauge/">eGauge</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMamac/">MAMAC</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMetersImport/">Meter Import</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminReadingsImport/">Reading Import</a></br></div></div><div style="padding-left: 1em;"><h6>Site Installation</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallOutput/">Production Install Output</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">Installation Directions</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUpgrading/">Upgrades</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUpgradingV1/">Upgrades V1.0.0</a></br></div></div><h5>User documentation</h5><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/../user/">User help</a></br></div><h5>Documentation versions for this page</h5><div style="padding-left: 1em;"> V1.0.0 (current page)</br> <a href="../../helpV0_8_0/adminInstallation/">V0.8.0</a></br> <a href="../../helpV0_7_0/adminInstallation/">V0.7.0</a></br></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user.</div><p>This describes the installation of an OED site for production use. If one is a developer, you likely want to follow the directions on the <a href="https://openenergydashboard.org/developer/gettingStarted/">getting started</a> page.<h2>Requirements</h2><p>OED uses Unix, including Linux, features to work and run Docker. Most sites have servers running Unix/Linux and can directly run OED. MacOS is based on Unix and Docker can be installed directly as an application. Windows from Microsoft is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume the system is at that level of Windows. If one has Windows 10/11 Professional, Enterprise or Education, one should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If one has Windows 10/11 Home then one can use WSL 2 to enable Linux and then install Docker. Once Docker is installed and working, one can follow the direction given here since they only depend on Docker/docker compose. The beginning of the <a href="https://openenergydashboard.org/developer/wslSteps/">WSL page</a> has details on WSL and Docker installation on Windows 10/11 Home.<p>OED is installed using the Docker containerization tool. This allows it to be isolated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the <code>docker compose</code> command. One will need Docker version 19.03 or higher (since July 2019) but that should not be an issue if running any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home one can see the link on the WSL page given in the previous step. General Docker installation information is available from <a href="https://docs.docker.com/engine/install/" rel="nofollow">Docker</a>.<p>It is assumed that the server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless the default OED port is changed). It is also assumed the server can access the internet for the installation.<p>These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of an organization.<p>This guide requires that one enter some commands into an operating system shell, or terminal.<ul><li>On Windows, this is the terminal that connects to the Linux running under WSL.<li>On MacOS, one can use Terminal.app (the default), iTerm2, or any other terminal program.<li>On Linux, the distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for "Terminal" in the application menu.</ul><h2>Installation</h2><p>Follow these steps to install a production (OED site for an organization) site:<ol><li><p>Clone the desired OED code from Github. Note if the <code>directory</code> is left off in the next step then the OED code will be placed in the current directory in the subdirectory OED. If "." is used for the <code>directory</code> (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. The OED software can be placed anywhere desired but the terminal should be using the desired directory before beginning the clone of the OED software.<ul><li>If a specific released version of OED is desired (this is most common) then do: <code>git clone --branch &lt;tag_name&gt; https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. The officially released and tagged versions at the <a href="https://github.com/OpenEnergyDashboard/OED/releases" rel="noopener noreferrer">OED GitHub release page</a> list all OED releases. In general, a site should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v1.0.0 in the subdirectory OED of the current directory do: <code>git clone --branch v1.0.0 https://github.com/OpenEnergyDashboard/OED.git</code>. After this there should be the directory OED where the clone was done.<li>If a site wants the latest version from development then do: <code>git clone https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. Note this will likely be code that has not yet gone through complete testing as done for an official release version but will have the latest OED code base. In general, production sites do not use this code.</ul><li>cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others.<li><p>Edit <code>docker-compose.yml</code>. Note that for values with an = one should not put spaces before or after the equal sign as is shown in the sample value. The edits are:<ol type="a"><li>POSTGRES_PASSWORD (under <code>services: -&gt; database: -&gt; environment:</code>) to a site specific password instead of the <code>pleaseChange</code> that is provided. Keep it secret but it should never need to known unless one wants to access the PostgreSQL database outside of the docker container. It will be: <code>- POSTGRES_PASSWORD=whateverPasswordYouChoose</code><li>OED_PRODUCTION (under <code>services: -&gt; web: -&gt; environment:</code>) to <code>yes</code> so it becomes: <code>- OED_PRODUCTION=yes</code>.<li>OED_TOKEN_SECRET (under <code>services: -&gt; web: -&gt; environment:</code>) to a random value instead of the <code>?</code> that is provided. Keep it secret but it should never need to known. It will be: <code>- OED_TOKEN_SECRET=whateverTokenYouChoose</code><li>The port (in <code>services: -&gt; web: -&gt; ports:</code>) for mapping from host to container; e.g., to host on the server's port 80, set it to <code>80:3000</code>. This assumes the site wants to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with <code>#</code>). Before editing it should look like:<pre><code>
+<!doctype html><html class="no-js" lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Installation Directions Doc</title><link rel="stylesheet" type="text/css" href="https://openenergydashboard.org/assets/css/styles_feeling_responsive.css"> <script src="https://openenergydashboard.org/assets/js/modernizr.min.js"></script> <script src="https://ajax.googleapis.com/ajax/libs/webfont/1.5.18/webfont.js"></script> <script> WebFont.load({ google: { families: [ 'Lato:400,700,400italic:latin', 'Volkhov::latin' ] } }); </script> <noscript><link href='http://fonts.googleapis.com/css?family=Lato:400,700,400italic%7CVolkhov' rel='stylesheet' type='text/css'> </noscript><meta name="description" content="Version V1.0.0 Documentation overview Admin documentation Information Overview Standard Units Pages Units &amp; Conversions Site Management Conversion Creating Conversion Editing Conversion Viewing Group Creating Group Editing Group Map Creating Map Viewing Meter Creating Meter Editing Meter Viewing Site Settings Unit Creating Unit Editing Unit Viewing User Data Acquisition CSV Import Data Acquisition eGauge MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades Upgrades V1.0.0 User documentation User help Documentation versions for this page V1.0.0 (current page) V0.8.0 V0.7.0 These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If one is a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work and run Docker. Most sites have servers running Unix/Linux and can directly run OED. MacOS is based on Unix and Docker can be installed directly as an application. Windows from Microsoft is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume the system is at that level of Windows. If one has Windows 10/11 Professional, Enterprise or Education, one should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If one has Windows 10/11 Home then one can use WSL 2 to enable Linux and then install Docker. Once Docker is installed and working, one can follow the direction given here since they only depend on Docker/docker compose. The developer getting started page has details on WSL and Docker installation. OED is installed using the Docker containerization tool. This allows it to be isolated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. One will need Docker version 19.03 or higher (since July 2019) but that should not be an issue if running any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home one can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that the server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless the default OED port is changed). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of an organization. This guide requires that one enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, one can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, the distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in the application menu. Installation Follow these steps to install a production (OED site for an organization) site: Clone the desired OED code from Github. Note if the directory is left off in the next step then the OED code will be placed in the current directory in the subdirectory OED. If &quot;.&quot; is used for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. The OED software can be placed anywhere desired but the terminal should be using the desired directory before beginning the clone of the OED software. If a specific released version of OED is desired (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. The officially released and tagged versions at the OED GitHub release page list all OED releases. In general, a site should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v1.0.0 in the subdirectory OED of the current directory do: git clone --branch v1.0.0 https://github.com/OpenEnergyDashboard/OED.git. After this there should be the directory OED where the clone was done. If a site wants the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has not yet gone through complete testing as done for an official release version but will have the latest OED code base. In general, production sites do not use this code. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. Edit docker-compose.yml. Note that for values with an = one should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; database: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but it should never need to known unless one wants to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but it should never need to known. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) for mapping from host to container; e.g., to host on the server&#39;s port 80, set it to 80:3000. This assumes the site wants to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before editing it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If the site wants to have standard web requests (port 80) serve up OED then edit to look like (comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if the line - &quot;3000:3000&quot; is uncommented and the line - &quot;9229:9229&quot; is commented out then OED will server up on port 3000 (where the line - &quot;80:3000&quot; is commented out). Later in these directions, it is suggested to set up a cron job to send an email to someone each day with any issues the OED installation encountered. No email is sent unless an issue is encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. This is done by setting these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP). As the comment says this can be secure-smtp to use an SMTP server or none if the site is not going to have OED send mail alerts. OED only supports sending mail via secure channels. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this usually becomes OED_MAIL_METHOD=secure-smtp. OED_MAIL_SMTP gives the web address of the SMTP server for sending mail. For example, it could be OED_MAIL_SMTP=smtp.example.com where example.com would become the domain for your organization or one could use OED_MAIL_SMTP=smtp.gmail.com for Google Mail. OED_MAIL_SMTP_PORT gives the port number of the SMTP server for sending mail. For example, it is often OED_MAIL_SMTP_PORT=465 for the standard SSL connection port. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with the user name email for sending mail. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA) unless given a token for the credential (an app password for mail for Google has been tested and it works). OED_MAIL_FROM gives the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where the desired email address is used. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name is desired. For the remaining steps one needs to be the superuser/root to have sufficient permission to modify system files. Some OS setups allow the install step (next) without being the superuser but it is generally safer not to try. Make sure the terminal is in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of the server. The terminal will display a lot of output about installing the database (Postgres), getting needed packages (this can take a while so during this process there may not be more output for a while; this normally happens right after the &quot;database system is ready to accept connections&quot; output line) and starting up the web system (this can take a while so during this process there may not be more output for a while; this normally happens right after the &quot;webpack build --node-env production&quot; output line). Future builds will go much faster. When the terminal displays the lines: oed-web-1 | webpack 5.76.0 compiled successfully in 200210 ms oed-web-1 | OED install finished oed-web-1 | Starting OED in production mode oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 start oed-web-1 | &gt; node ./src/bin/www oed-web-1 | oed-web-1 | [INFO@2023-10-20T11:22:35.803-05:00] Listening on port 3000 then OED should be ready to accept web requests. If there was an error in the output then OED might not be running properly. Please contact the OED project if there are questions where sending the terminal text is generally very helpful. The typical output of the install is available. A web browser can now be used to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where oed.myinstition.org is replaced with the name of the server where OED is installed. If all is working properly, the main OED page (see Home Navigation documentation page for an image of what it will look like). The page won&#39;t be able to graph any data until the site has OED acquire meter data. If the mapping of 80:3000 was not done above, then OED would be reachable at oed.myinstition.org:3000. The site now needs to create an admin user to log into OED on the website. To do this, a second terminal is opened, go to the root OED directory and become a superuser/root user (as has been done). This is done so OED remains running in the first terminal to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password desired to use with this email to login into OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password to access with OED admin features on the web pages. Run the command docker compose run web npm run editUser to change the password if forgotten or to create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what is typed so this information will be in the terminal. This terminal shouldn&#39;t be needed any more so it can be closed to hide the information or usually type clear to remove it from what is shown in the terminal. Now log in on the OED web page to make sure this account works. The options menu documentation is available but basically just click the &quot;Log in&quot; choice in the top, right of the OED website under &quot;Options&quot; and then enter the information. Shut down OED. Soon OED will be set up to run as a service so the OED currently running in the terminal should be shut down. In the terminal where OED was started (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. The following steps require knowledge of the root directory path of OED. In the terminal located in the OED root directory do: pwd and the output will tell the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. It is not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the cron job to aggregate the hourly readings needed for the fast data access OED does to the database when zoomed in on data. The site can choose how frequently to do this. If the site wants to see the latest meter data quickly then this should be done hourly. Note the update takes a modest amount of CPU and can delay when users see data. If preferred, the site could run the script daily just before running the daily updates. This would mean the new hourly data would only become visible after the day completes. However, sites generally do not have issues with doing this every hour so it is normally done. In the root OED directory do (this assumes the site updates every hour): cp src/scripts/refreshHourlyReadingViewsCron.bash /etc/cron.hourly/refreshHourlyReadingViewsCron.bash Edit /etc/cron.daily/refreshHourlyReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail but it should be the same as the daily script changes. Do: chmod +x /etc/cron.hourly/refreshHourlyReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on the server. There is a chance that the server version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; needed to set below is the one assigned to OED. It is the one logged into the terminal before becoming superuser/root and (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming the site wants to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless this service is disabled with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart whenever the service is started again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If one wants to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes one wants to see the output of OED when it is running as a service. This can be useful during the install to see why OED did not come up. Do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where &amp;lt;CONTAINER ID&amp;gt; is replaced with the value from the previous step. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, a site will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If a newer version is desired then upgrade to it. Consult the directions on the OED Upgrading page. Admin setup The designated admin can use the login created above to set the desired features and items of OED. The following may be desired where the links can be used to get more information: Site preferences. Allows for setting of the site name, default actions on the graphic pages, creating other users, and certain limits among other things. data acquisition. Discusses getting meter data into OED so the site can display data. Standard units and conversions. Discusses the units and conversions provided by OED and making more of them visible to the user. Users. To create additional user logins and manage them. Admin features. Discusses the range of actions that admins can take and the related documentation pages. There are many OED features other than the ones linked directly above. Other information Though less likely, one may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is an up-to-date node_modules directory in the root OED directory) and skips doing it again to save time. However, a site can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before doing this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta name="google-site-verification" content="Vk0IOJ2jwG_qEoG7fuEXYqv0m2rLa8P778Fi_GrsgEQ"><meta name="msvalidate.01" content="0FB4C028ABCF07C908C54386ABD2D97F" ><link rel="canonical" href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/"><meta property="og:title" content="Installation Directions Doc"><meta property="og:description" content="Version V1.0.0 Documentation overview Admin documentation Information Overview Standard Units Pages Units &amp; Conversions Site Management Conversion Creating Conversion Editing Conversion Viewing Group Creating Group Editing Group Map Creating Map Viewing Meter Creating Meter Editing Meter Viewing Site Settings Unit Creating Unit Editing Unit Viewing User Data Acquisition CSV Import Data Acquisition eGauge MAMAC Meter Import Reading Import Site Installation Production Install Output Installation Directions Upgrades Upgrades V1.0.0 User documentation User help Documentation versions for this page V1.0.0 (current page) V0.8.0 V0.7.0 These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user. This describes the installation of an OED site for production use. If one is a developer, you likely want to follow the directions on the getting started page. Requirements OED uses Unix, including Linux, features to work and run Docker. Most sites have servers running Unix/Linux and can directly run OED. MacOS is based on Unix and Docker can be installed directly as an application. Windows from Microsoft is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume the system is at that level of Windows. If one has Windows 10/11 Professional, Enterprise or Education, one should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If one has Windows 10/11 Home then one can use WSL 2 to enable Linux and then install Docker. Once Docker is installed and working, one can follow the direction given here since they only depend on Docker/docker compose. The developer getting started page has details on WSL and Docker installation. OED is installed using the Docker containerization tool. This allows it to be isolated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the docker compose command. One will need Docker version 19.03 or higher (since July 2019) but that should not be an issue if running any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home one can see the link on the WSL page given in the previous step. General Docker installation information is available from Docker. It is assumed that the server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless the default OED port is changed). It is also assumed the server can access the internet for the installation. These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of an organization. This guide requires that one enter some commands into an operating system shell, or terminal. On Windows, this is the terminal that connects to the Linux running under WSL. On MacOS, one can use Terminal.app (the default), iTerm2, or any other terminal program. On Linux, the distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for &quot;Terminal&quot; in the application menu. Installation Follow these steps to install a production (OED site for an organization) site: Clone the desired OED code from Github. Note if the directory is left off in the next step then the OED code will be placed in the current directory in the subdirectory OED. If &quot;.&quot; is used for the directory (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. The OED software can be placed anywhere desired but the terminal should be using the desired directory before beginning the clone of the OED software. If a specific released version of OED is desired (this is most common) then do: git clone --branch &amp;lt;tag_name&amp;gt; https://github.com/OpenEnergyDashboard/OED.git [directory]. The officially released and tagged versions at the OED GitHub release page list all OED releases. In general, a site should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v1.0.0 in the subdirectory OED of the current directory do: git clone --branch v1.0.0 https://github.com/OpenEnergyDashboard/OED.git. After this there should be the directory OED where the clone was done. If a site wants the latest version from development then do: git clone https://github.com/OpenEnergyDashboard/OED.git [directory]. Note this will likely be code that has not yet gone through complete testing as done for an official release version but will have the latest OED code base. In general, production sites do not use this code. cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others. Edit docker-compose.yml. Note that for values with an = one should not put spaces before or after the equal sign as is shown in the sample value. The edits are: POSTGRES_PASSWORD (under services: -&amp;gt; database: -&amp;gt; environment:) to a site specific password instead of the pleaseChange that is provided. Keep it secret but it should never need to known unless one wants to access the PostgreSQL database outside of the docker container. It will be: - POSTGRES_PASSWORD=whateverPasswordYouChoose OED_PRODUCTION (under services: -&amp;gt; web: -&amp;gt; environment:) to yes so it becomes: - OED_PRODUCTION=yes. OED_TOKEN_SECRET (under services: -&amp;gt; web: -&amp;gt; environment:) to a random value instead of the ? that is provided. Keep it secret but it should never need to known. It will be: - OED_TOKEN_SECRET=whateverTokenYouChoose The port (in services: -&amp;gt; web: -&amp;gt; ports:) for mapping from host to container; e.g., to host on the server&#39;s port 80, set it to 80:3000. This assumes the site wants to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with #). Before editing it should look like: ports: - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: # - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above If the site wants to have standard web requests (port 80) serve up OED then edit to look like (comment out the debug port because it is not normally used in production): ports: # - &quot;3000:3000&quot; # Should be commented out if you uncomment 80:3000 below. # - &quot;9229:9229&quot; # Debug port, should be commented out for production # For production you might want something like: - &quot;80:3000&quot; # and comment out the debug port and 3000:3000 line above It is possible to use a different port. For example, if the line - &quot;3000:3000&quot; is uncommented and the line - &quot;9229:9229&quot; is commented out then OED will server up on port 3000 (where the line - &quot;80:3000&quot; is commented out). Later in these directions, it is suggested to set up a cron job to send an email to someone each day with any issues the OED installation encountered. No email is sent unless an issue is encountered. For this to work, OED needs to have access to a mail system (SMTP server) to send the mail. This is done by setting these environment values under services: -&amp;gt; web: -&amp;gt; environment: OED_MAIL_METHOD gives the way email is sent (SMTP). As the comment says this can be secure-smtp to use an SMTP server or none if the site is not going to have OED send mail alerts. OED only supports sending mail via secure channels. Note that the SMTP listed here does not have to relate to the mail recipient. In the end, this usually becomes OED_MAIL_METHOD=secure-smtp. OED_MAIL_SMTP gives the web address of the SMTP server for sending mail. For example, it could be OED_MAIL_SMTP=smtp.example.com where example.com would become the domain for your organization or one could use OED_MAIL_SMTP=smtp.gmail.com for Google Mail. OED_MAIL_SMTP_PORT gives the port number of the SMTP server for sending mail. For example, it is often OED_MAIL_SMTP_PORT=465 for the standard SSL connection port. OED_MAIL_IDENT gives the user name on the SMTP server where the mail will be sent. Replace someone@example.com with the user name email for sending mail. OED_MAIL_CREDENTIAL gives the password for the SMTP user in OED_MAIL_IDENT. Replace credential with that password. Note this setup cannot accommodate two factor authentication (2FA) unless given a token for the credential (an app password for mail for Google has been tested and it works). OED_MAIL_FROM gives the email address that the mail will be from. This is often the same as the OED_MAIL_IDENT so it might be OED_MAIL_FROM=mydomain@example.com where the desired email address is used. OED_MAIL_TO gives the email address of who will get the emails. Replace someone@example.com with the desired email. It can be the same as the SMTP email above or something different. OED_MAIL_ORG gives the organization name that will be part of the subject of the email sent. This may be important in recognizing the email, esp. if the person receiving it gets email from multiple OED sites (not common). Replace My Organization Name with whatever name is desired. For the remaining steps one needs to be the superuser/root to have sufficient permission to modify system files. Some OS setups allow the install step (next) without being the superuser but it is generally safer not to try. Make sure the terminal is in the root OED directory (where the README.md file is located). Install OED on the server by doing docker compose up. This will get all the needed software including Postgres, all node packages and then installs all the needed software. This can take from a minute to 10+ minutes depending on the speed of the server. The terminal will display a lot of output about installing the database (Postgres), getting needed packages (this can take a while so during this process there may not be more output for a while; this normally happens right after the &quot;database system is ready to accept connections&quot; output line) and starting up the web system (this can take a while so during this process there may not be more output for a while; this normally happens right after the &quot;webpack build --node-env production&quot; output line). Future builds will go much faster. When the terminal displays the lines: oed-web-1 | webpack 5.76.0 compiled successfully in 200210 ms oed-web-1 | OED install finished oed-web-1 | Starting OED in production mode oed-web-1 | oed-web-1 | &gt; open-energy-dashboard@1.0.0 start oed-web-1 | &gt; node ./src/bin/www oed-web-1 | oed-web-1 | [INFO@2023-10-20T11:22:35.803-05:00] Listening on port 3000 then OED should be ready to accept web requests. If there was an error in the output then OED might not be running properly. Please contact the OED project if there are questions where sending the terminal text is generally very helpful. The typical output of the install is available. A web browser can now be used to check that OED is properly serving up web pages. Use the web address oed.myinstition.org where oed.myinstition.org is replaced with the name of the server where OED is installed. If all is working properly, the main OED page (see Home Navigation documentation page for an image of what it will look like). The page won&#39;t be able to graph any data until the site has OED acquire meter data. If the mapping of 80:3000 was not done above, then OED would be reachable at oed.myinstition.org:3000. The site now needs to create an admin user to log into OED on the website. To do this, a second terminal is opened, go to the root OED directory and become a superuser/root user (as has been done). This is done so OED remains running in the first terminal to add the user. Run the script with: docker compose run web npm run createUser. The code will prompt to enter an email address and password: # docker compose run web npm run createUser Starting checkoed_database_1 ... done &gt; Open-Energy-Dashboard@0.6.0 createUser &gt; node ./src/server/services/user/createUser.js Email of user to create: someEmail@yourInstitution.org Password: passwordYouChoose [INFO@2021-10-13T21:40:31.853Z] User created or already exists where you replace someEmail@yourInstitution.org with any email (it does not have to be an active one) and passwordYouChoose with the password desired to use with this email to login into OED (passwords must be at least 8 characters long). It is important to remember this email &amp; password to access with OED admin features on the web pages. Run the command docker compose run web npm run editUser to change the password if forgotten or to create a new user. Note an OED admin user can create more users on the site so this is normally a one-time step. Note that OED echos what is typed so this information will be in the terminal. This terminal shouldn&#39;t be needed any more so it can be closed to hide the information or usually type clear to remove it from what is shown in the terminal. Now log in on the OED web page to make sure this account works. The options menu documentation is available but basically just click the &quot;Log in&quot; choice in the top, right of the OED website under &quot;Options&quot; and then enter the information. Shut down OED. Soon OED will be set up to run as a service so the OED currently running in the terminal should be shut down. In the terminal where OED was started (with docker compose up), do &quot;^c&quot; to shut down OED. Be a little patient since doing a second &quot;^c&quot; will cause a rapid stop of docker without the normal cleanup. The following steps require knowledge of the root directory path of OED. In the terminal located in the OED root directory do: pwd and the output will tell the directory path. Set up the daily cron job to email the OED admin with any issues that occurred in the past day. It is not required to do this but it is a very good idea. It gives someone a daily email of any issue so they are not missed. See above about needed values in docker-compose.yml to support sending emails. In the root OED directory do: cp src/scripts/sendLogEmailCron.bash /etc/cron.daily/sendLogEmailCron.bash Edit /etc/cron.daily/sendLogEmailCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/sendLogEmailCron.bash to make the script executable. Set up the daily cron job to aggregate the daily readings needed for the fast data access OED does to the database. In the root OED directory do: cp src/scripts/refreshReadingViewsCron.bash /etc/cron.daily/refreshReadingViewsCron.bash Edit /etc/cron.daily/refreshReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail. Do: chmod +x /etc/cron.daily/refreshReadingViewsCron.bash to make the script executable. Set up the cron job to aggregate the hourly readings needed for the fast data access OED does to the database when zoomed in on data. The site can choose how frequently to do this. If the site wants to see the latest meter data quickly then this should be done hourly. Note the update takes a modest amount of CPU and can delay when users see data. If preferred, the site could run the script daily just before running the daily updates. This would mean the new hourly data would only become visible after the day completes. However, sites generally do not have issues with doing this every hour so it is normally done. In the root OED directory do (this assumes the site updates every hour): cp src/scripts/refreshHourlyReadingViewsCron.bash /etc/cron.hourly/refreshHourlyReadingViewsCron.bash Edit /etc/cron.daily/refreshHourlyReadingViewsCron.bash to make the necessary modifications to the script. See the script for more detail but it should be the same as the daily script changes. Do: chmod +x /etc/cron.hourly/refreshHourlyReadingViewsCron.bash to make the script executable. Set up the service so OED runs regularly on the server. There is a chance that the server version of Unix requires a modification of these steps. These steps should work on a Red Hat/Centos Unix. The &quot;User&quot; needed to set below is the one assigned to OED. It is the one logged into the terminal before becoming superuser/root and (hopefully not) the superuser/root. In the root OED directory do: cp src/scripts/oed.service /etc/systemd/system/oed.service Edit /etc/systemd/system/oed.service to make the necessary modifications to the script. See the script for more detail. Do: systemctl enable oed.service to make the service start on server boot. Assuming the site wants to start OED at this time do: systemctl start oed.service. Stop the app at any time by doing: systemctl stop oed.service but note it will restart on the next reboot unless this service is disabled with: systemctl disable oed.service. To check the status of the OED service do: systemctl list-units --type=service | grep -i oed. Note that OED needs to reinstall/restart whenever the service is started again so it will take a little while from the time this lists the service as loaded and active running until it is ready to serve up web pages. If one wants to check this is all set up correctly then restart the server and check it is still serving up web pages (as described above). Sometimes one wants to see the output of OED when it is running as a service. This can be useful during the install to see why OED did not come up. Do this by: Get the container ID by using: docker ps -a. The CONTAINER ID will be the one with the IMAGE of ...oed_web (where there may be some name in the ...) for the install/web output and IMAGE of ...oed_database for any database output. docker logs &amp;lt;CONTAINER ID&amp;gt; | more where &amp;lt;CONTAINER ID&amp;gt; is replaced with the value from the previous step. OED upgrades The OED project is regularly improving the code and releasing new versions of OED. To get the latest features, a site will probably want to upgrade OED over time. Information on officially released and tagged versions is given on the OED GitHub release page. If a newer version is desired then upgrade to it. Consult the directions on the OED Upgrading page. Admin setup The designated admin can use the login created above to set the desired features and items of OED. The following may be desired where the links can be used to get more information: Site preferences. Allows for setting of the site name, default actions on the graphic pages, creating other users, and certain limits among other things. data acquisition. Discusses getting meter data into OED so the site can display data. Standard units and conversions. Discusses the units and conversions provided by OED and making more of them visible to the user. Users. To create additional user logins and manage them. Admin features. Discusses the range of actions that admins can take and the related documentation pages. There are many OED features other than the ones linked directly above. Other information Though less likely, one may want to consult: Environment variable page about all the OED environment variables. NPM script page about the available scripts to support the OED setup. It is rare that the node/npm installation is not okay in a production environment. The OED installation detects if the node install already happened (because there is an up-to-date node_modules directory in the root OED directory) and skips doing it again to save time. However, a site can force OED to do the node install by going to the root OED directory and deleting the node_modules directory with: rm -rf node_modules/. Make sure OED is not running (see stopping the service above) before doing this since it will break the application. Redoing the OED install with docker compose up will recreate this directory."><meta property="og:url" content="https://openenergydashboard.org/helpV1_0_0/adminInstallation/"><meta property="og:locale" content="en_EN"><meta property="og:type" content="website"><meta property="og:site_name" content="Open Energy Dashboard"><link rel="icon" sizes="32x32" href="https://openenergydashboard.org/assets/img/OEDIcon22x32.png"><link rel="icon" sizes="192x192" href="https://openenergydashboard.org/assets/img/OEDIcon192x274.png"><body id="top-of-page" class="page-fullwidth"><div id="navigation" class="sticky"><nav class="top-bar" role="navigation" data-topbar data-options="scrolltop: false"><ul class="title-area"><li class="name"><h1 class="hide-for-large-up"><a href="https://openenergydashboard.org/" class="icon-tree"> Open Energy Dashboard</a></h1><li class="toggle-topbar toggle-topbar-click menu-icon"><a><span>Nav</span></a></ul><section class="top-bar-section"><ul class="left"><li><a href="https://openenergydashboard.org/">home</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/features/">features</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/features/">features by type</a><li><a href="https://openenergydashboard.org/useAcademic/">features by academic use</a></ul><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/helpV1_0_0/user/">Documentation</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/helpV1_0_0/user/">oed version 1.0.0</a><li><a href="https://openenergydashboard.org/helpV0_8_0/user/">oed version 0.8.0</a><li><a href="https://openenergydashboard.org/helpV0_7_0/user/">oed version 0.7.0</a><li><a href="https://openenergydashboard.org/helpV0_6_0/user/">oed version 0.6.0</a></ul><li class="divider"><li><a href="https://openenergydashboard.org/use/">Adopting</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/news/">info</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/news/">news</a><li><a href="https://openenergydashboard.org/principles/">project principles</a><li><a href="https://openenergydashboard.org/free/">free &amp; maintained</a><li><a href="https://openenergydashboard.org/mission/">mission</a><li><a href="https://openenergydashboard.org/why/">why exists</a><li><a href="https://openenergydashboard.org/projectInfo/">project information pages &amp; license</a><li><a href="https://openenergydashboard.org/name/">why OED name, logo &amp; some history</a></ul><li class="divider"></ul><ul class="right"><li class="divider"><li><a href="https://openenergydashboard.org/search/">Search</a><li class="divider"><li><a href="https://openenergydashboard.org/contact/">Contact</a><li class="divider"><li><a href="https://openenergydashboard.org/developer/developer/">developer docs</a><li class="divider"><li class="has-dropdown"> <a href="https://openenergydashboard.org/involved/">get involved</a><ul class="dropdown"><li><a href="https://openenergydashboard.org/internship/">becoming a developer</a><li><a href="https://openenergydashboard.org/studentExperience/">student experience</a></ul></ul></section></nav></div><div id="masthead-no-image-header"><div class="row"><div class="small-6 small-centered columns"> <a id="logo" title="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> <img src="https://openenergydashboard.org/assets/img/logoHelp.png" alt="Open Energy Dashboard – A Free, Open Source Energy/Resource Dashboard"> </a></div></div></div><nav class="breadcrumbs" role="menubar" aria-label="breadcrumbs"> <a href="https://openenergydashboard.org/">Start</a> <a href="https://openenergydashboard.org/helpV1_0_0/">helpV1_0_0</a> <a class="current">Installation Directions</a></nav><div class="row t15"><div class="medium-12 columns"><article><header><p class="subheadline">OED Documentation<h1>Installation Directions</h1></header><div class="row"><p>Version V1.0.0<div class="medium-4 medium-push-8 columns" markdown="1"><div class="panel radius" markdown="1"><div style="list-style: none;" class="side-nav"><h4><a href='../admin/'>Documentation overview</a></h4><div><h5>Admin documentation</h5><div style="padding-left: 1em;"><h6>Information</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/admin/">Overview</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminOedUnits/">Standard Units</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminPageChoices/">Pages</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUnitInfo/">Units & Conversions</a></br></div></div><div style="padding-left: 1em;"><h6>Site Management</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/adminConversionCreating/">Conversion Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminConversionEditing/">Conversion Editing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminConversionViewing/">Conversion Viewing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminGroupCreating/">Group Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminGroupEditing/">Group Editing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminGroupViewing/">Group</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMapCreating/">Map Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMapViewing/">Map Viewing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMeterCreating/">Meter Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMeterEditing/">Meter Editing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMeterViewing/">Meter Viewing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminPreferences/">Site Settings</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUnitCreating/">Unit Creating</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUnitEditing/">Unit Editing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUnitViewing/">Unit Viewing</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUser/">User</a></br></div></div><div style="padding-left: 1em;"><h6>Data Acquisition</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/adminCsvImport/">CSV Import</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminDataAcquisition/">Data Acquisition</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminEgauge/">eGauge</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMamac/">MAMAC</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminMetersImport/">Meter Import</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminReadingsImport/">Reading Import</a></br></div></div><div style="padding-left: 1em;"><h6>Site Installation</h6><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallOutput/">Production Install Output</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/">Installation Directions</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUpgrading/">Upgrades</a></br> <a href="https://openenergydashboard.org/helpV1_0_0/adminUpgradingV1/">Upgrades V1.0.0</a></br></div></div><h5>User documentation</h5><div style="padding-left: 1em;"> <a href="https://openenergydashboard.org/helpV1_0_0/adminInstallation/../user/">User help</a></br></div><h5>Documentation versions for this page</h5><div style="padding-left: 1em;"> V1.0.0 (current page)</br> <a href="../../helpV0_8_0/adminInstallation/">V0.8.0</a></br> <a href="../../helpV0_7_0/adminInstallation/">V0.7.0</a></br></div></div></div></div></div><div class="medium-8 medium-pull-4 columns" markdown="1"><div class="alert-box info "><p>These features are only available to select people who oversee the OED site (called admins) so this information is not usually of interest to a general user.</div><p>This describes the installation of an OED site for production use. If one is a developer, you likely want to follow the directions on the <a href="https://openenergydashboard.org/developer/gettingStarted/">getting started</a> page.<h2>Requirements</h2><p>OED uses Unix, including Linux, features to work and run Docker. Most sites have servers running Unix/Linux and can directly run OED. MacOS is based on Unix and Docker can be installed directly as an application. Windows from Microsoft is not based on Unix so other steps are necessary. Given that Windows 10+ is generally needed to install OED and the fact that most systems run at least Windows 10, these directions assume the system is at that level of Windows. If one has Windows 10/11 Professional, Enterprise or Education, one should be able to directly install Docker via the Hyper-V though it may need to be enabled (this has not been tested by OED). If one has Windows 10/11 Home then one can use WSL 2 to enable Linux and then install Docker. Once Docker is installed and working, one can follow the direction given here since they only depend on Docker/docker compose. The <a href="https://openenergydashboard.org/developer/gettingStarted/">developer getting started page</a> has details on WSL and Docker installation.<p>OED is installed using the Docker containerization tool. This allows it to be isolated from the rest of the system, and makes updates easier to perform, since the dependencies are all taken care of through the container definitions. Under Docker, OED is installed and administered using the <code>docker compose</code> command. One will need Docker version 19.03 or higher (since July 2019) but that should not be an issue if running any reasonably up-to-date version. Some versions of Linux already have Docker or it can be installed. Docker for MacOS is an app that can easily be installed. For Windows 10 Home one can see the link on the WSL page given in the previous step. General Docker installation information is available from <a href="https://docs.docker.com/engine/install/" rel="nofollow">Docker</a>.<p>It is assumed that the server is set up to respond to web requests (port 80) and that port 3000 is allowed (unless the default OED port is changed). It is also assumed the server can access the internet for the installation.<p>These directions assume someone with root access to the server where OED is being installed and a working knowledge of doing Unix shell commands including editing text files. This is generally someone within the IT department of an organization.<p>This guide requires that one enter some commands into an operating system shell, or terminal.<ul><li>On Windows, this is the terminal that connects to the Linux running under WSL.<li>On MacOS, one can use Terminal.app (the default), iTerm2, or any other terminal program.<li>On Linux, the distribution will provide a terminal; it can generally be opened with Ctrl+Shift+T or by searching for "Terminal" in the application menu.</ul><h2>Installation</h2><p>Follow these steps to install a production (OED site for an organization) site:<ol><li><p>Clone the desired OED code from Github. Note if the <code>directory</code> is left off in the next step then the OED code will be placed in the current directory in the subdirectory OED. If "." is used for the <code>directory</code> (just a period without the quotes) then the OED software will be placed directly into the current directory without a subdirectory. The OED software can be placed anywhere desired but the terminal should be using the desired directory before beginning the clone of the OED software.<ul><li>If a specific released version of OED is desired (this is most common) then do: <code>git clone --branch &lt;tag_name&gt; https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. The officially released and tagged versions at the <a href="https://github.com/OpenEnergyDashboard/OED/releases" rel="noopener noreferrer">OED GitHub release page</a> list all OED releases. In general, a site should take the latest release (at the top of the page). Note that the clone will not include git history (with detached head) but that should not be needed in a production environment. For example, to get release v1.0.0 in the subdirectory OED of the current directory do: <code>git clone --branch v1.0.0 https://github.com/OpenEnergyDashboard/OED.git</code>. After this there should be the directory OED where the clone was done.<li>If a site wants the latest version from development then do: <code>git clone https://github.com/OpenEnergyDashboard/OED.git [directory]</code>. Note this will likely be code that has not yet gone through complete testing as done for an official release version but will have the latest OED code base. In general, production sites do not use this code.</ul><li>cd into the directory that has the cloned version of OED. This is known as the root directory of OED. It has a README.md file and others.<li><p>Edit <code>docker-compose.yml</code>. Note that for values with an = one should not put spaces before or after the equal sign as is shown in the sample value. The edits are:<ol type="a"><li>POSTGRES_PASSWORD (under <code>services: -&gt; database: -&gt; environment:</code>) to a site specific password instead of the <code>pleaseChange</code> that is provided. Keep it secret but it should never need to known unless one wants to access the PostgreSQL database outside of the docker container. It will be: <code>- POSTGRES_PASSWORD=whateverPasswordYouChoose</code><li>OED_PRODUCTION (under <code>services: -&gt; web: -&gt; environment:</code>) to <code>yes</code> so it becomes: <code>- OED_PRODUCTION=yes</code>.<li>OED_TOKEN_SECRET (under <code>services: -&gt; web: -&gt; environment:</code>) to a random value instead of the <code>?</code> that is provided. Keep it secret but it should never need to known. It will be: <code>- OED_TOKEN_SECRET=whateverTokenYouChoose</code><li>The port (in <code>services: -&gt; web: -&gt; ports:</code>) for mapping from host to container; e.g., to host on the server's port 80, set it to <code>80:3000</code>. This assumes the site wants to serve OED up on the standard web port. There are multiple lines here and some are commented out (begin with <code>#</code>). Before editing it should look like:<pre><code>
     ports:
         - "3000:3000" # Should be commented out if you uncomment 80:3000 below.
         - "9229:9229" # Debug port, should be commented out for production
diff --git a/sitemap.xml b/sitemap.xml
index f3a33777..76125c71 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -7,7 +7,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/404.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -22,7 +22,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/admin.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -37,7 +37,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/admin.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -52,7 +52,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/admin.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -67,7 +67,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/admin.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -82,7 +82,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminConversionCreating.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -97,7 +97,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminConversionEditing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -112,7 +112,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminConversionViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -127,7 +127,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminCsvImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -142,7 +142,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminCsvImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -157,7 +157,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminCsvImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -172,7 +172,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminDataAcquisition.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -187,7 +187,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminDataAcquisition.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -202,7 +202,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/adminDataAcquisition.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -217,7 +217,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminDataAcquisition.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -232,7 +232,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminEgauge.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -247,7 +247,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminGroupCreating.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -262,7 +262,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminGroupEditing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -277,7 +277,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminGroupViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -292,7 +292,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminGroupViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -307,7 +307,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/adminGroupViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -322,7 +322,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminGroupViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -337,7 +337,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminInstallOutput.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -352,7 +352,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminInstallOutput.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -367,7 +367,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminInstallOutput.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -382,7 +382,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminInstallation.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -397,7 +397,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminInstallation.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -412,7 +412,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminInstallation.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -427,7 +427,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminMamac.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -442,7 +442,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminMamac.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -457,7 +457,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminMamac.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -472,7 +472,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminMap.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -487,7 +487,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/adminMap.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -502,7 +502,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminMap.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -517,7 +517,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminMapCreating.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -532,7 +532,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminMapViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -547,7 +547,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminMapViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -562,7 +562,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/adminMapViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -577,7 +577,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminMapViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -592,7 +592,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminMeterCreating.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -607,7 +607,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminMeterEditing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -622,7 +622,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminMeterViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -637,7 +637,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminMeterViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -652,7 +652,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/adminMeterViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -667,7 +667,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminMeterViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -682,7 +682,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminMetersImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -697,7 +697,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminMetersImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -712,7 +712,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminMetersImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -727,7 +727,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminOedUnits.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -742,7 +742,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminPageChoices.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -757,7 +757,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminPreferences.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -772,7 +772,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminPreferences.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -787,7 +787,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/adminPreferences.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -802,7 +802,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminPreferences.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -817,7 +817,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminReadingsImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -832,7 +832,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminReadingsImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -847,7 +847,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminReadingsImport.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -862,7 +862,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminUnitCreating.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -877,7 +877,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminUnitEditing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -892,7 +892,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminUnitInfo.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -907,7 +907,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminUnitViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -922,7 +922,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminUpgrading.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -937,7 +937,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminUpgrading.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -952,7 +952,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminUpgrading.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -967,7 +967,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminUpgradingV1.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -982,7 +982,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/adminUser.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -997,7 +997,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/adminUser.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1012,7 +1012,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/adminUser.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1027,7 +1027,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/blog/archive/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1042,7 +1042,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/areaNormalization.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1061,7 +1061,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/barGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1076,7 +1076,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/barGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1091,7 +1091,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/barGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1106,7 +1106,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/barGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1121,7 +1121,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/chartLink.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1136,7 +1136,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/chartLink.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1151,7 +1151,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/chartLink.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1166,7 +1166,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/chartLink.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1181,7 +1181,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/compareGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1196,7 +1196,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/compareGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1211,7 +1211,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/compareGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1226,7 +1226,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/compareGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1241,7 +1241,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/contact/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1256,7 +1256,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/conversionsUnits.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1271,7 +1271,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/demo/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1286,7 +1286,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/exampleDescription.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1301,7 +1301,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/export.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1316,7 +1316,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/export.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1331,7 +1331,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/export.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1346,7 +1346,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/export.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1361,7 +1361,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/features/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1376,7 +1376,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/free/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1391,7 +1391,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/graphType.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1406,7 +1406,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/graphType.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1421,7 +1421,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/graphType.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1436,7 +1436,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/graphType.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1451,7 +1451,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/graphingGroups.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1466,7 +1466,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/graphingGroups.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1481,7 +1481,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/graphingGroups.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1496,7 +1496,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/graphingGroups.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1511,7 +1511,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/graphingMeters.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1526,7 +1526,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/graphingMeters.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1541,7 +1541,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/graphingMeters.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1556,7 +1556,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/graphingMeters.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1571,7 +1571,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/graphingRates.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1586,7 +1586,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/graphingUnits.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1601,7 +1601,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/groupViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1616,7 +1616,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/groupViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1631,7 +1631,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/groupViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1646,7 +1646,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/groupViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1661,7 +1661,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/hideOptions.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1676,7 +1676,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/hideOptions.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1691,7 +1691,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/hideOptions.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1706,7 +1706,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/hideOptions.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1721,7 +1721,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/home.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1736,7 +1736,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/home.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1751,7 +1751,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/home.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1766,7 +1766,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/home.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1781,7 +1781,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/blog/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1796,7 +1796,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1811,7 +1811,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1826,7 +1826,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1841,7 +1841,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1856,7 +1856,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1871,7 +1871,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/internship/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1886,7 +1886,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/involved/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1901,7 +1901,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/language.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1916,7 +1916,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/language.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1931,7 +1931,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/language.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1946,7 +1946,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/lineGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1961,7 +1961,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/lineGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1976,7 +1976,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/lineGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -1991,7 +1991,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/lineGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2006,7 +2006,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/mapGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2021,7 +2021,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/mapGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2036,7 +2036,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/mapGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2051,7 +2051,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/mapGraphic.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2066,7 +2066,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/meterViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2081,7 +2081,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/meterViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2096,7 +2096,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/meterViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2111,7 +2111,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/meterViewing.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2126,7 +2126,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/mission/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2141,7 +2141,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/name/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2156,7 +2156,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/news/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2171,7 +2171,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/optionsMenu.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2186,7 +2186,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/optionsMenu.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2201,7 +2201,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/optionsMenu.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2216,7 +2216,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/optionsMenu.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2231,7 +2231,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/pageChoices.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2246,7 +2246,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/pageChoices.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2261,7 +2261,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/pageChoices.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2276,7 +2276,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/pageChoices.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2291,7 +2291,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/principles/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2306,7 +2306,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/projectInfo/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2321,7 +2321,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/robots.txt</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2340,7 +2340,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/search/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2355,7 +2355,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/sitemap.xml</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2370,7 +2370,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/studentExperience/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2387,7 +2387,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/time.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2402,7 +2402,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/time.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2417,7 +2417,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/time.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2432,7 +2432,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/time.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2447,7 +2447,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/tooltip.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2462,7 +2462,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/tooltip.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2477,7 +2477,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/tooltip.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2492,7 +2492,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/tooltip.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2507,7 +2507,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/use/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2522,7 +2522,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/useAcademic/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2537,7 +2537,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v1.0.0/user.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2552,7 +2552,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.7.0/user.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2567,7 +2567,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.6.0/user.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2582,7 +2582,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/help/v0.8.0/user.html</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>
@@ -2597,7 +2597,7 @@
 	<url>
 	<loc>https://openenergydashboard.org/why/</loc>
 	
-		<lastmod>2024-07-29T10:19:41-05:00</lastmod>
+		<lastmod>2024-09-01T15:17:53-05:00</lastmod>
 	
 	
 		<changefreq>monthly</changefreq>