GithubHelp home page GithubHelp logo

lhcb / starterkit Goto Github PK

View Code? Open in Web Editor NEW
7.0 26.0 8.0 38.66 MB

Central website for all efforts related to the LHCb Starterkit.

Home Page: https://lhcb.github.io/starterkit

License: MIT License

Ruby 0.23% HTML 46.67% SCSS 53.11%

starterkit's Introduction

Starterkit

The source code for the website for the LHCb Starterkit organisation.

Building the website

The site is built automatically whenever the gh-pages branch is updated on GitHub.

To build the site locally, you need to install the github-pages gem and then run Jekyll, a program that converts the collection of HTML templates and Markdown files in this repository to full HTML pages. Assuming you have Ruby installed on your machine, which should be the case on anything but Windows, inside this repository you can do:

$ gem install bundler
$ bundle install --path=vendor/bundle
$ bundle exec jekyll build

(The use of the --path option in bundle install and of bundle exec makes the dependency installation local to the folder containing the repository, so that your ‘global’ list of gems isn't touched.)

This will build the site into the _site directory, and you can then open _site/index.html in your browser to see the site.

To have Jekyll monitor the repository for changes and serve the website on a local development server, do:

$ bundle exec jekyll serve --watch

You can visit the site using the local address http://127.0.0.1:4000/starterkit/.

starterkit's People

Contributors

alexpearce avatar kdungs avatar chrisburr avatar vlisovsk avatar lcapriot avatar ibab avatar betatim avatar vlukashenko avatar pseyfert avatar

Stargazers

Alaa Abdelhamid avatar Sascha Stahl avatar Christoph Hasse avatar  avatar Placido Fernandez Declara avatar  avatar  avatar

Watchers

 avatar Albert Puig avatar James Cloos avatar Oliver Lantwin avatar Sebastian Neubert avatar Henry Schreiner avatar Violaine Bellée avatar Eduardo Rodrigues avatar  avatar Giulio Dujany avatar  avatar Rosen Matev avatar Roel Aaij avatar  avatar Antje Mödden avatar Sascha Stahl avatar Dylan Jaide White avatar Stefano Petrucci avatar Victor Daussy-Renaudin avatar Johannes Heuel avatar Luca avatar Alejandro Alfonso avatar  avatar  avatar  avatar Arnau Brossa avatar

starterkit's Issues

Report on Run II

The page for "Starterkit Run II" is still a stub. It should be filled to resemble "First Starterkit".

Projects for 2019 Impactkit

We should start making notes of project ideas for the next Impactkit:

  • Outreach ideas (especially in preparation for the open days in September 2019)

As I can't assign you: @andriiusachov

Travis

Set up Travis to build the page as a rudimentary check.

Domain

We could get something like lhcb-starterkit.web.cern.ch with little effort I think.
Ideally lhcb-starterkit.cern but I have no idea how to go about that.

Grammtical mistake/unclear wording in "Changes to data flow in Run2"

The text to the section "Changes to data flow in Run2" contains the following sentence:

That is to say, any tracks or detector responses that don't form part of the decay that the trigger lines uses to evaluate its selection is thrown away.

"Trigger lines" is plural, but the following verb "uses" is singular. Unfortunately I cannot correct this because I really don't know what the right answer is.

Are tracks really thrown away until they contribute to trigger any of the L0, Hlt1, oder Hlt2 lines? Doesn't that throw away a lot of good TIS events?

New template for *-analysis-steps

The current template for the lessons is based on the software carpentry template. It has served us well, but I think we can do better.

I'd like us to discuss two things: moving to a different lesson template, and the possibility of merging the two lesson repos.

Changing the lesson template

Pros

  1. It works! We've been using the lesson templates for three workshops now.
  2. It doesn't look terrible.
  3. We've had to spend very little time fiddling with layouts and CSS and blah, just concentrated on the content.

Cons

  1. We never got around to fully customising the template; e.g. some links in the footer still point to Software Carpentry stuff.
  2. It doesn't look particularly nice. Could have proper syntax highlighting, could match the style of the central site, have a better layout, and so on.
  3. We would have to do some designing/website building, and it's hard enough getting the content ready in time.

Having a single lessons repository

This is just an idea I had.

I'm not sure if there's a big benefit in having two repos, first- and second-analysis steps. We could just have a single lhcb-starterkit-lessons repo, which we can pick and chose from when putting together a course. Then we don't have to have clumsy links referring to lessons in “the first Starterkit” or “in First Analysis Steps”; everything will be easy to find because it's all on one page.

(I had students in the Impactkit who didn't realise/forgot that we'd already taught some things in first-analysis-steps that they could use for stuff in second-*. Having all the lessons visible on a single index might help.)

Font and icons

There seems to be a problem related to the fonts.
screen shot 2016-05-12 at 13 55 41

This doesn't match the screenshots in the PR.

Participant feedback and thank you email

We should prepare a Google Form for the participants to fill in, asking a few questions about how they found the course overall. The email with the link can also act as the ‘closing message’ from the organisers, thanking people for coming, for actively participating, etc.

Some ideas for questions:

  • What aspects of the course did you really like (or: what things did we do well)?
  • What things did you dislike (or: what things could we do better)?
  • Did you enjoy the projects day?
    • Liked the project you were assigned?
    • Would have preferred a larger choice of projects?
    • Supervisor(s) gave you enough support?
    • Felt satisfied with the outcome?
    • Would you have preferred to have more of the usual lessons instead?
  • Would you recommend a course like Impactkit to other students?

Tmux / screen in starterkit

Hi!

This is just an idea to add to the LHCb starterkit.
Tmux / screen are very handy tools for running scripts, and (searching for a few minutes this repo) I don't think they are now included, but probably should be mentioned.
Both are installed on lxplus.
PS: I can help to create an example and description.

Cheers,
Ana

Responsive design

screen shot 2016-09-19 at 22 18 44

Just discovered that the beautiful design doesn't do so well on mobile. WDYT about going single column for mobile?

CONTRIBUTING.md

Add standard contributing document. Main point is to explain how to build the pages locally as well as list the default rules and guidelines etc. LICENSE aussi?

Ganga, grid usage, etc: Which practices are good and which are bad?

I've had mixed responses to practices I've learned from the Starterkit from people in Distributed Analysis, about a couple of things:

HTCondor usage

corresp. page: https://lhcb.github.io/starterkit-lessons/self-guided-lessons/htcondor.html

Apparently using HTCondor / LXBATCH is against LHCb fair usage policy? See
https://mattermost.web.cern.ch/lhcb/channels/distributed-analysis/s7ckr86kwpyxubu3n6mfsxupia

Replication of grid files to CERN-USER storage elements for analysis purposes

corresp. page: https://lhcb.github.io/starterkit-lessons/second-analysis-steps/managing-files-with-ganga.html
I've been discouraged from doing this, and told I should instead access my files by authenticating with a grid certificate.

Project follow-ups for May 2016 Impactkit

I think the project supervisors should contact the project groups to summarise the progress made during the project day. This will give the students a chance to have any questions they didn't ask on Friday, and for the supervisors to give the students some more ideas to write about.

One of my projects will be continuing, so the email will be an opportunity to discuss what the team will be doing.

Migrate away from GitBook

At some point we should consider moving from GitBook to something else as the CLI interface we use is no longer maintained and contains various bugs. We could consider moving to CERN GitLab, but this would only apply to the LHCb repositories and we might not want to maintain multiple CI pipelines. I think the preference is to use a "popular" static site generator in the hope that we avoid being stuck with an abandonded tool.

Essential features:

  • Full text search
  • LaTeX math rendering
  • Syntax highlighting
  • Collapseable pop outs for challenges or additional details

Potentially desirable features:

  • Better support for viewing/downloading code files
  • Testing of code snippets (ALICE are already doing this)
  • Printable for teachers to use as a reference
  • Tempate and CI maintained outside of the documentation repository to allow it to be updated in a single place
  • Able to ingest Jupyter notebooks for the Python lessons

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.