Hi Nicolas,
On Tue, Sep 10, 2013 at 06:33:16PM +0200, Nicolas Goaziou wrote:
>
> Suvayu Ali <fatkasuvayu+li...@gmail.com> writes:
>
> > On Tue, Sep 10, 2013 at 11:02:35AM +0200, Carsten Dominik wrote:
> >>
> >> And by linear, I think we don't mean strictly linear, but on a
> >> paragraph/table/item scale, ignoring hierarchy.
> >
> > Yes. However I think I differ a bit on items. For me in a list like
> > the following, I would call moving by paragraphs _within_ the list items
> > linear; so, "Lorem..." → "Cras..." → "Integer..." → "Aenean..." →
> > "Pellentesque...", and so on.
>
> Here's a first draft for the linear forward motion. Disclaimer: I didn't
> test it thoroughly.
>
> (defun org-forward-linear-element ()
Some comments and a backtrace (I used the corrected 2nd revision):
1. When traversing the file header, goes one line at a time. I would
expect to go to the next blank line. In the attached Org file, from
somewhere on #+TITLE to the blank line before the first headline.
2. Skips whole source block even if there are blank lines. So can't
navigate large source blocks for small edits. Try on the python
source block under the first headline.
3. Goes through each row of a table instead of going over the table in
one go. Start with cursor on "From ConDBBrowser:".
4. Skips the whole body under a headline when followed by link. Try
putting point on the headline "Important points" and move; you will
jump to "Tagging Issues" instead of the link and the list after.
How can I test going backward?
--
Suvayu
Open source is the future. It sets us free.
#+TITLE: B-physics stuff
#+AUTHOR: Suvayu Ali
#+EMAIL: Suvayu dot Ali at cern dot ch
#+LANGUAGE: en
#+OPTIONS: H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:{} -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:nil
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
* Parameters
A random source block
#+begin_src python
print 'Hello'
print 'Hello again!'
print 'Hello again, again!'
#+end_src
>From ConDBBrowser:
| PARTICLE | GEANTID | PDGID | MASS(GeV) | TLIFE(s) | EVTGENNAME |
|----------+---------+-------+------------+---------------+------------|
| B_s0 | 75 | 531 | 5.36630000 | 1.472000e-012 | B_s0 |
| B_s~0 | 76 | -531 | 5.36630000 | 1.472000e-012 | anti-B_s0 |
| B_s0H | 99996 | 530 | 5.36630000 | 1.536875e-012 | B_s0H |
| B_s0L | 99997 | 350 | 5.36630000 | 1.407125e-012 | B_s0L |
* Bachelor particle opening angle as PID
:PROPERTIES:
:CUSTOM_ID: opening-angle
:END:
** Important points
[[notmuch:id:20120102164039.28276...@nikhef.nl][Notmuch email thread with
comments]]
1. Bs⁰ is pseudo-scalar meson: decays isotropically in its rest frame,
idea is to exploit this fact to better separate Bs⁰→Dsπ and Bs⁰→DsK
crossfeed
2. Dependence on mass hypotheses:
- Opening angle in lab frame (does not depend on mass hyp.)
- Boost back to Bs⁰ rest frame (depends on mass hyp.)
- if mass hyp. correct, cos(θ*) must be flat (isotropic decay of
scalar!), mass must be Bs⁰ mass within resolution
some modification to flat cos(θ*) distribution due to /detector
acceptance/ effects
* Tagging Issues
:PROPERTIES:
:CUSTOM_ID: tagging
:END:
How should SS and OS tagging decisions be combined? What do we do in
overlap regions b/w the two taggers?
#+begin_example
+----------------------------------+
| |
| +---------------+ |
| | | |
| | OST +-+-+-+--------+ |
| | |/ / /| | |
| | | / / | | |
| +---------++-+-++ | |
| | SSK | |
| All events | | |
| +--------------+ |
| |
+----------------------------------+
#+end_example
# Local Variables:
# org-export-allow-BIND: t
# default-input-method: TeX
# End:
