Differences

This shows you the differences between two versions of the page.

--- computational:analysis [2020/04/09 15:25] – [Description] aroberts
+++ computational:analysis [2020/09/01 16:36] (current) – chekanov
@@ Line 1: / Line 1: @@
-**__''UNDER CONSTRUCTION''__**
 ====== CompF5: End user analysis ======
 ===== Working Group Co-Conveners =====
@@ Line 5: / Line 4: @@
 |Gavin Davies|Mississippi|gsdavies[at]phy.olemiss.edu|
 |Peter Onyisi|Texas|ponyisi[at]utexas.edu|
-|Amy Roberts|UC Denver |AMY.ROBERTS[at]UCDENVER.EDU|
+|Amy Roberts|UC Denver |amy.roberts[at]ucdenver.edu|
+===== Joining the Group ======
+We are on the [[https://snowmass2021.slack.com/archives/C012476LS15|#compf05-useranalysis]] channel in the [[https://snowmass2021.slack.com/|Snowmass Slack]], and important announcements are sent via snowmass-compf5-useranalysis[at]fnal.gov (subscribe via [[https://listserv.fnal.gov/scripts/wa.exe?SUBED1=SNOWMASS-COMPF05-USERANALYSIS|this link]]).
+The Indico category that includes our meetings is [[https://indico.fnal.gov/category/1107/|here]].
+===== Topics for Letters of Interest & White Papers =====
+Community input is a critical part of the Snowmass process. We encourage [[https://snowmass21.org/loi|letters of interest (LOI)]] and [[https://snowmass21.org/submissions/start|white papers]] discussing the following (non-exclusive) list of topics relevant to end-user analysis:
+  * Hardware for analysis facilities
+  * Use of accelerators
+  * Analysis libraries
+  * Data storage formats & dataset bookkeeping
+  * Programming languages
+  * Software for collaboration: version control, messaging
+  * “Real-time” analysis
+  * Long-term reproducibility and preservation
+Please consider the following aspects when preparing LOIs and white papers.
+  * Sustainability, both technical and human
+     * Documentation
+     * Training
+     * Long-term software support & development
+     * Integration with the broader ecosystem
+     * Broad applicability to the field
+     * Hardware facility evolution
+  * Interaction with other scientific fields & industry
+     * Role of proprietary technology
+     * Potential contributions to computing outside HEP
+  * User experience
+     * Ease of use & setup
+     * Scalability of technologies
+     * Required training and broad applicability of training to other domains
+     * Accessibility
 ===== Description=====
   * Functional areas
@@ Line 18: / Line 51: @@
     * What is the evolution of these technologies?
     * How are these solutions embedded in industry solutions or solutions used by other science domains?
-    * &lt;questions about statistical tools, to be filled>
+    * questions about statistical tools, to be filled
     * Ensure balance between ROOT/C++ experts and new technology experts
-    * version control
+    * version control ♦
     * slack and similar tools
-    * ZOOM, Skype (important for training end users, also helping them troubleshoot)
+    * ZOOM, Skype
     * What tools are used/needed by the stakeholders to develop code collaboratively, to communicate?
     * How is the intra stakeholder communication working, how will it work in the future?
-    * Proprietary software, licenses
+    * Proprietary software, licenses ♦
-    * VMs, containers
+    * VMs, containers ♦
     * Integration of external packages into experiment software stacks
     * What are other science domains using, what is industry using?
+Items marked with ♦ are also being considered by [[https://snowmass21.org/computational/preservation|CompF8: Reinterpretation and long-term preservation of data and code]].  Our groups will discuss these items once we have identified needs within our individual working groups.
+===== Submitted LOI =====
+ Here is the list of submitted LOIs to this topical group.   First index before "/"  corresponds to the primary frontier used for the submission.
+ {{url>https://www.snowmass21.org/docs/files/list.php?frontier=CompF5  border 100%,1000px}}