Music notation file formats are specialized digital file types used to represent musical notation and scores. These formats enable composers, musicians, and music educators to create, share, and store their musical compositions in a way that can be read and understood by music notation software. Various file formats serve different purposes and offer different features. Here are some common music notation file formats: 1. **MusicXML (.musicxml, .xml)**: - A standardized format for representing Western music notation.
In music, "articulations" refers to the way in which specific notes or phrases are expressed in terms of their attack, duration, and decay. Articulation affects the character and attack of each note, influencing how they are played or sung. Common types of articulations include: 1. **Staccato**: Notes are played short and detached, creating a crisp sound. 2. **Legato**: Notes are played smoothly and connected, with no noticeable breaks between them.
Ornamentation refers to the decorative elements added to a work of art, music, or architecture to enhance its aesthetic appeal or expressivity. The specifics can vary widely depending on the context: 1. **Visual Arts**: In painting, sculpture, and decorative arts, ornamentation may involve the use of patterns, textures, and colors to embellish a piece. It can include motifs, detailed patterns, or intricate designs that add richness and complexity.
Replication crisis by Ciro Santilli 37 Updated 2025-07-16
Of course, if academic journals require greater reproducibility for publication, then the cost per paper increases.
However, the total cost has to be smaller than the cost everyone who reads the paper spends to reproduce, no?
The truth is, part of the replication crisis is also due to research groups not wanting to share their precious secrets with others, so they can keep ahead of the publication curve, or maybe spin off a startup.
And when it comes to papers, things are even crazier: big companies manage to publish white papers in peer reviewed journals.
Ciro Santilli wants to help in this area with his videos of all key physics experiments project idea.
Cool initiative. Papers that do not share source code should be banned from peer reviewed academic journals.
Video 1.
Phone Intercom by Make (2014)
Source. This video illustrates will the incredible simplicity of the connection of a telephone system. Compare that to the relative complexity of wireless communication, which requires modulation.
Video 2.
Making a Microphone Work with an Oscilloscope by Environmental Radiation LLC (2012)
Source. Not the most detailed setup, but good.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    Figure 3.
    Visual Studio Code extension installation
    .
    Figure 4.
    Visual Studio Code extension tree navigation
    .
    Figure 5.
    Web editor
    . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact