Skip to content

Commit 72bc58e

Browse files
graeme-a-stewarteduardo-rodrigues
graeme-a-stewart
authored and
eduardo-rodrigues
committed
Minutes from 2018-01-11 (#202)
* Minutes from 2018-01-11 Move advice on arXiv upload procedure to a separate page Link to two recent CWP talks * Address review comments and make a few formatting improvements
1 parent 3be5779 commit 72bc58e

File tree

3 files changed

+229
-0
lines changed

3 files changed

+229
-0
lines changed

‎_activities/cwp.md

+4
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ for the roadmap.
2323

2424
The roadmap summarised reports from fourteen working groups who studied the challenges in their
2525
sub-domains. All of the reports produced during the Community White Paper process are listed below.
26+
Working groups are in the process of [finalising and uploading](../cwp/cwp-wg-papers.html) their work to arXiv.
2627

2728
{:.table .table-hover .table-condensed .table-striped}
2829
| *Paper* | *Report Number* | *Link* |
@@ -48,6 +49,9 @@ sub-domains. All of the reports produced during the Community White Paper proces
4849

4950
This is a list of talks about the CWP Roadmap that were given by various HSF members:
5051

52+
* 2018-01-10 [Presentation](https://indico.cern.ch/event/651349/contributions/2830237/attachments/1580497/2497360/cwp-gdb-january-2018.pdf) at the [January 2018 GDB](https://indico.cern.ch/event/651349/) by Graeme Stewart.
53+
* 2017-01-05 [Talk](https://indico.cern.ch/event/666278/contributions/2830239/attachments/1579352/2495271/Advances_in_software_and_computing_for_HEP.pdf) at the [2018 Spåtlid Nordic Particle Physics Meeting](https://indico.cern.ch/event/666278/overview) in Skeikampen, Norway by Graeme Stewart (covers HEP software and computing
54+
challenges in general, as well as the CWP).
5155
* 2017-11-28 [Presentation](https://indico.desy.de/indico/event/18681/session/8/contribution/114/material/slides/0.pdf) at the [11th Terascale Alliance Workshop](https://indico.desy.de/indico/event/18681/) by Benedikt Hegner.
5256
* 2017-10-29 [Presentation](https://indico.cern.ch/event/663273/contributions/2708178/attachments/1545100/2431717/HSF-CWP-Roadmap.pdf) on the CWP Roadmap at
5357
the [3rd Scientific Computing Forum](https://indico.cern.ch/event/663273/) by Graeme Stewart.

‎cwp/cwp-wg-papers.md

+54
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: "Community White Paper - Publishing to arXiv"
3+
author: "Graeme Stewart"
4+
layout: default
5+
---
6+
7+
## Publishing CWP Working Group Papers to arXiv
8+
9+
This is the currently recommended way to publish each of the CWP WG
10+
papers to [arXiv](https://arxiv.org). This route ensures a high presentation standard
11+
for the finished paper, allows reuse of bibtex files and archives
12+
the document sources in the HSF document repository, so it it strongly
13+
recommended.
14+
15+
1. Finalise paper text, ensuring a good standard of English,
16+
scientific content and rigour (we have come a long way -
17+
let's not fall at the final hurdle!).
18+
- Try to do this as much as possible within your working
19+
group, but ask the [CWP Ghost Writers team](mailto:[email protected])
20+
for help if needed.
21+
1. If necessary, convert from Google Doc to LaTeX using pandoc
22+
- Download your Google Doc as docx, a.k.a. MS Word, format
23+
- Using [pandoc](https://pandoc.org/), which is easily [installed](https://pandoc.org/installing.html),
24+
convert your docx file to latex:
25+
- `pandoc -f docx -t latex -o wgpaper.tex wgpaper.docx`
26+
- The conversion is generally very accurate, but within `itemize` environments you
27+
may find that text is inside a spurious `quote` environment and that some
28+
odd non-breaking spaces appear. Just delete these.
29+
1. Adopt the JHEP preprint style, using the template in the
30+
[software development paper](https://github.com/HEP-SF/documents/tree/master/CWP/papers/HSF-CWP-2017-13_soft-dev/latex/).
31+
- Copy the `jheppub.sty` file into your latex area as it is needed for arXiv side compilation.
32+
1. The paper title should be `HEP Software Foundation Community White Paper Working Group \-- *My Working Group*`.
33+
1. You will need to add an abstract for arXiv.
34+
1. Add a copyright and license statement as a comment - we strongly recommend <br>`% Copyright (C) 2018, The HSF Community White Paper authors, licence CC-BY-4.0.`
35+
1. When finalised/finalising add the document sources to the
36+
HSF documents github repo,
37+
[https://github.com/HEP-SF/documents](https://github.com/HEP-SF/documents), following the
38+
usual pull request workflow. You can ask `hegner`, `eduardo-rodrigues`, `graeme-a-stewart`
39+
or `jouvin` for a review (best to pick at least two).
40+
- Your paper should go into
41+
`CWP/papers/HSF-CWP-2017-XX_short-wg-name/latex` (the first part for correct ordering,
42+
the second for allowing people to know which paper is which at a glance).
43+
1. You can now take advantage of the [large bibtex](https://github.com/graeme-a-stewart/documents/blob/master/CWP/papers/HSF-CWP-2017-01_roadmap/latex/cwp.bib) file that
44+
was used for the roadmap for your references.
45+
- There is also a common file for references to [WG papers](https://github.com/graeme-a-stewart/documents/blob/master/CWP/papers/HSF-CWP-2017-01_roadmap/latex/cwp-chapters.bib) themselves.
46+
1. Upload to arXiv, use "Computational Physics (physics.comp-ph)" as the primary
47+
subject, with "High Energy Physics - Experiment (hep-ex)" as a secondary.
48+
- Note that when uploading files to arXiv, it is the `.bbl` file of resolved and formatted
49+
references that is required, not the source `.bib` files.
50+
1. You can now finalise your own paper's reference in
51+
[CWP/papers/HSF-CWP-2017-01\_roadmap/latex/cwp-chapters.bib](https://github.com/graeme-a-stewart/documents/blob/master/CWP/papers/HSF-CWP-2017-01_roadmap/latex/cwp-chapters.bib).
52+
- Make a final commit to github with this last piece of information so that all regenerated
53+
WG texts will include the new cross reference correctly.
54+

‎organization/_posts/2018-01-11-startup.md

+171
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,171 @@
1+
---
2+
title: "HSF Weekly Meeting #121, January 11, 2018"
3+
layout: default
4+
---
5+
6+
### *Present/Contributors*: Dario Menasce, Giulio Eluise, Graeme Stewart, Benedikt Hegner, Ian Bird, Simone Campana, Pere Mato, Thomas Kuhr, Mike Sokoloff, Liz Sexton-Kennedy, Eduardo Rodrigues, Stewart Martin-Haugh, Pete Elmer
7+
8+
News, general matters
9+
=====================
10+
- ### Happy New Year!
11+
12+
CWP
13+
===
14+
- ### General Matters and Roadmap
15+
- Reminder of the published URL:
16+
[https://arxiv.org/abs/1712.06982](https://arxiv.org/abs/1712.06982).
17+
- We continue to add authors on request to
18+
[[email protected]](mailto:[email protected]).
19+
- Not a lot of new names so far this year.
20+
- At some point we have to decide when we are done.
21+
- Two talks so far this year:
22+
- Nordic Physics Conference:
23+
[https://indico.cern.ch/event/666278/contributions/2830239/](https://indico.cern.ch/event/666278/contributions/2830239/).
24+
- Grid Deployment Board:
25+
[https://indico.cern.ch/event/651349/](https://indico.cern.ch/event/651349/).
26+
- Graeme approached the CERN Courier and the editor's feedback is
27+
that this is interesting, should be a \~2400 word article. To be confirmed
28+
early next week after their editorial meeting.
29+
- Article on CWP published last year in the CERN EP department
30+
newsletter:
31+
[http://ep-news.web.cern.ch/content/hep-software-foundation-community-white-paper-looks-forward-hl-lhc](http://ep-news.web.cern.ch/content/hep-software-foundation-community-white-paper-looks-forward-hl-lhc).
32+
- Newsletter in [interactions.org](https://www.interactions.org/) - Eduardo to follow up.
33+
- We have been approached by the editors of the [Computing and
34+
Software for Big Science journal](https://www.springer.com/physics/particle+and+nuclear+physics/journal/41781)
35+
about publishing it there.
36+
- Pere wondered if this was really suitable for a research
37+
journal. As we were approached by the editors we think
38+
so - more of a review article.
39+
- Those who have known about this (Ghost Writers) are positive
40+
about this.
41+
- This would provide a natural cut off for signing.
42+
- General conclusion is that we should pursue this with the
43+
journal editors.
44+
45+
- #### Publication strategy for Individual WG Papers
46+
- We noted that conversion from Google Doc to LaTeX was far less
47+
painful than had been thought so our recommendation for arXiv
48+
publication for individual papers is updated. This was
49+
followed to get the Software Development paper to arXiv late
50+
last year.
51+
- [Advice on WG publication](/cwp/cwp-wg-papers.html).
52+
- We have to decide what to do when the WG paper is in a much less
53+
developed state than the roadmap (Generators, ML) or only only
54+
really exists in the roadmap (Security).
55+
- #### Software Development
56+
- Done as exemplar:
57+
[https://arxiv.org/abs/1712.07959](https://arxiv.org/abs/1712.07959)
58+
- #### Simulation
59+
- Need to revisit the detailed paper ensure consistency. Then
60+
will follow the procedure.
61+
- #### Machine Learning
62+
- To follow up.
63+
- #### Software Trigger and Event Reconstruction
64+
- Neither Vava nor David can attend today. Apologies. We plan
65+
to pick up improvements to our text made during the final
66+
editing of the cwp and hope to submit to the archive next
67+
week. We already have completed one pass of gathering
68+
authors and will do another.
69+
- #### Data Organisation, Management and Access
70+
- To follow up.
71+
- #### Data and Software Preservation
72+
- To follow up.
73+
- #### Data Analysis and Interpretation
74+
- To follow up.
75+
- #### Visualization
76+
- Ric (unable to attend today) will do final paper edits next
77+
week, ready for last circulation before arXiv.
78+
- #### Event/Data Processing Frameworks
79+
- Liz at CERN next week, will follow up with Benedikt.
80+
- #### Careers, Staffing and Training
81+
- Dario will backport material from the roadmap.
82+
- #### Facilities and Distributed Computing
83+
- Clean up needed of the WG document.
84+
- #### Conditions Access
85+
- To follow up.
86+
- #### Generators
87+
- Needs some work from roadmap document. Should get CMS,
88+
Durham IPPP inputs as well.
89+
- #### Security
90+
- To follow up.
91+
- John Harvey - what's the plan for producing a document for the LHCC?
92+
<br>Ian - will give the LHCC a strategy document in February; the WLCG
93+
view of the CWP Roadmap.
94+
95+
Upcoming Events
96+
===============
97+
98+
[HSF/WLCG Workshop](https://indico.cern.ch/event/658060/overview)
99+
-----------------
100+
- Summary yesterday in [GDB meeting](https://indico.cern.ch/event/651349/).
101+
- All local organisation points are done.
102+
- Registration has quietly opened yesterday.
103+
- Need to chase up conveners (we have a wish list - need to
104+
contact them).
105+
- Goal is to follow up on the CWP roadmap, identify and work on
106+
real projects.
107+
- Plenty of parallel session opportunities - *working groups should actively propose
108+
parallel sessions!*
109+
- Discussion: Mike - goal should be cross-experiment development
110+
collaborations. Useful to have 'outcomes' in advance and try to
111+
structure the workshop towards them; though sometimes the outcomes were
112+
different to those originally envisaged. E.g., in software
113+
development could try to discuss tools and methods to implement
114+
suggestions in the white paper. Giulio - could discuss an
115+
incubation procedure to help people to get started on their
116+
projects. Simone - should focus on priorities for WLCG.
117+
- Please check the [agenda](https://indico.cern.ch/event/658060/timetable/).
118+
Main point is to get the right people there.
119+
120+
PyHEP Workshop
121+
--------------
122+
- Reminder: 1st "Python in HEP" workshop to be held as a pre-CHEP
123+
event on 7-8 July 2018, so just before CHEP 2018 itself.
124+
- Goal of workshop(s): provide an environment to discuss and
125+
promote the usage of Python in the HEP community at large.
126+
- Organisation progressing well and we now have a reasonable idea of
127+
workshop structure & agenda.
128+
- Organising committee: Eduardo, Graeme, Jeff.
129+
- The 1.5-day agenda will be composed of plenary sessions dedicated to
130+
the following topics:
131+
1. Historical perspective and overview
132+
2. PyROOT and Python bindings
133+
3. HEP python software ecosystem
134+
4. Distribution and installation
135+
5. Analysis frameworks
136+
6. Python 2 versus 3
137+
7. Open discussion on education and training
138+
- There won't be any training sessions or hackathons in this first
139+
workshop, but some level of tuition will come in small bites in
140+
the various presentations, which will try and be educative, not
141+
just informative, with well-defined examples relevant to the
142+
topics under discussion
143+
- One of the goals of this PyHEP workshop will be to identify
144+
training workshops or hackathons the community would like to
145+
have in the future
146+
- Announcement will go out on Monday 15th
147+
- Dedicated page + advert on HSF website
148+
- Announcement email to be sent around
149+
- Once the announcement is out, find speakers for presentations
150+
foreseen, finalise the agenda, \...
151+
152+
Activity updates
153+
================
154+
155+
Licensing
156+
---------
157+
- Graeme still chasing HepMC status.
158+
159+
Training
160+
--------
161+
- Nothing to report.
162+
163+
Packaging
164+
---------
165+
- Next meeting 17 January.
166+
167+
AOB
168+
===
169+
- HSF New Year Newsletter
170+
- Should cover CWP status and upcoming workshops
171+
- Make sure we propose a CWP talk for CHEP itself.

0 commit comments

Comments
 (0)