Comments (5)
The BaBar track fit flipped 'on demand' between covariance and weights -- as for measurement nodes one need weights, but (IIRC!) transport typically wants covariances... And I think I discussed this with Wouter (he is the right person to ask!) but I think the conclusion was that either it didn't match the LHCb coding convention of strict separation between 'data' and 'algorithms' or it didn't gain us enough to bother... But regardless of that, we should reconsider this as an option, as maybe things have changed and the balance has shifted.
As for the 2nd point, one class of speedups we have implemented in a few hot spots is to not compute with more accuracy than needed (eg. Manuel's improvement on the T0 walk correction, which doesn't need to be known with 53 bits (16 digits) of precision, when the TDC that it corrects has only 8 bits in the first place). This should (IMHO) be propagated 'throughout' the code. There is precious little information on how accurate individual bits of code have to be. And in many cases, we just spend time computing 'random digits' beyond the required accuracy -- I've suggested a few times that we should sometimes explicitly truncate our precision to make things more reproducible. Conversely, I'd also like to know which parts of the code are 'borderline' on precision. I can imagine that there are algorithms where the precision isn't good enough. So in a perfect world, I'd like each bit of reconstruction code come with a specification on how accurate it should be, but I doubt we'll ever get to that stage. But it is something to strive for.
from scheduling-event-model.
Regarding the first point, we put Pierre in contact with Wouter so hopefully there are exchanging valuable information.
Regarding the second point : "There is precious little information on how accurate individual bits of code have to be. " I agree, I failed miserably to find this information when Pierre asked me questions about this. Maybe we can be optimistic and decide from now on "specification on how accurate it should be" shall be quoted together with the efficiencies, ghost rate etc. ? This is probably algorithm dependent but maybe @manuelschiller could teach us how to work this out ?
from scheduling-event-model.
@GerhardRaven ps : what does it mean (IIRC!) ?
from scheduling-event-model.
IIRC = If I Remenber Correctly
from scheduling-event-model.
Chatted with @manuelschiller, it seems tough to have a talk about code accuracy, since this is too algorithm dependent. We stick to the talk from Pierre.
from scheduling-event-model.
Related Issues (14)
- Little projects HOT 5
- Input from Marco Cattaneo HOT 1
- Data preservation
- List of contributions HOT 2
- Scheduling/Framework session schedule HOT 4
- Computational Graph Specification
- EDM design considerations HOT 9
- Lxplus Ninja HOT 4
- setup-lhcb-build.sh cannot work in chroot environments HOT 4
- Standup HOT 3
- broken links in CONTRIBUTING.md
- Contribution from Florian HOT 6
- Upgrade tracking HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from scheduling-event-model.