<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi David,
<div class=""><br class="">
</div>
<div class="">that’s a good point actually. What about 'prepare'? Just o throw one more option in ;-)</div>
<div class=""><br class="">
</div>
<div class="">Cheers,</div>
<div class="">Chris</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 13 Jun 2016, at 10:54, David Grellscheid <<a href="mailto:david.grellscheid@durham.ac.uk" class="">david.grellscheid@durham.ac.uk</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">I still prefer schedule over declare, exactly _because_ it has the implication that it is something that will be run. The caching and so on is an implementation detail users don't need to bother with.<br class="">
<br class="">
declare is too computer sciency for me. With that background you know what it means, but the generic meaning of declare is not really useful for us.<br class="">
<br class="">
David<br class="">
<br class="">
<br class="">
On 12/06/2016 02:06, Christian Gutschow wrote:<br class="">
<blockquote type="cite" class="">Oh I like declare! I think that’s my favourite of all the suggestions. Yes, let’s go for that one if there are no objections?<br class="">
<br class="">
Chris<br class="">
<br class="">
On 11 Jun 2016, at 22:24, Andy Buckley <<a href="mailto:a.g.buckley@gmail.com" class="">a.g.buckley@gmail.com</a><<a href="mailto:a.g.buckley@gmail.com" class="">mailto:a.g.buckley@gmail.com</a>>> wrote:<br class="">
<br class="">
I read appoint as annoint, which is even better ;-) Perhaps also consecrate, sanctify, or bless?<br class="">
<br class="">
But more seriously, I thought of "declare" earlier today and am not sure why it didn't come to mind sooner. For me it is at least as nice as "register" -- in fact, we already use it in the macro that registers/declares analysis plugins (and no, I don't think
there's any danger of confusion). And way more appropriate than "add", IMHO. What do you think, can we use it?<br class="">
<br class="">
Andy<br class="">
<br class="">
<br class="">
On 10/06/16 22:17, Christian Gutschow wrote:<br class="">
Hi Andy, all,<br class="">
<br class="">
schedule seems alright to me. Here are some more alternatives for the<br class="">
brainstorming: commission, employ, engage, enlist, appoint, establish. ;-)<br class="">
<br class="">
Cheers,<br class="">
Chris<br class="">
On 10 Jun 2016, at 20:58, Andy Buckley <<a href="mailto:andy.buckley@cern.ch" class="">andy.buckley@cern.ch</a><<a href="mailto:andy.buckley@cern.ch" class="">mailto:andy.buckley@cern.ch</a>><br class="">
<<a href="mailto:andy.buckley@cern.ch" class="">mailto:andy.buckley@cern.ch</a>>> wrote:<br class="">
<br class="">
Ha, we had the same response to "register" being forbidden!<br class="">
<br class="">
I certainly agree with dropping reg().<br class="">
<br class="">
schedule() is not bad -- I'd like to know what others think. The only<br class="">
flaw is that to me it implies that that projection will be run at a<br class="">
set time / order, while in practice it's lazy (and the result may<br class="">
already be cached).<br class="">
<br class="">
enroll() / enrol() will probably suck others into that US/other<br class="">
spelling trap ;-)<br class="">
<br class="">
record() is not quite right -- I feel like it specifies writing<br class="">
something to disk immediately.<br class="">
<br class="">
And catalog()... I don't really know what that implies.<br class="">
<br class="">
Grr, words. Right, I'm going to try and have a weekend now, and let<br class="">
this little word puzzle itch away in the background. Feel free to join<br class="">
me in this bikeshedding: names are important ;-)<br class="">
<br class="">
Andy<br class="">
<br class="">
<br class="">
<br class="">
On 10/06/16 17:30, David Grellscheid wrote:<br class="">
Hi Andy,<br class="">
<br class="">
Here's my preference (after some thesaurus googling):<br class="">
<br class="">
drop add() and reg()<br class="">
<br class="">
use schedule(), enroll(), record() or catalog() instead of register()<br class="">
<br class="">
We shouldn't multiply names for the same functionality. One deprecated<br class="">
name and one replacement is enough.<br class="">
<br class="">
See you,<br class="">
<br class="">
David<br class="">
<br class="">
<br class="">
<br class="">
On 10/06/2016 16:30, Andy Buckley wrote:<br class="">
Ah, I see!<br class="">
<br class="">
Anyway, yes we have had feedback that people don't really understand how<br class="">
the concept maps to the Rivet code so I think hiding by default is a<br class="">
good thing. And if it allows us to have shorter function names without<br class="">
losing clarity, that's no bad thing.<br class="">
<br class="">
I've implemented this on the 2.5 branch now. The one stumbling block was<br class="">
with the idea of register(someproj, "SomeName"): 'register' is a C(++)<br class="">
keyword, so I think we can't use it as a function name -- right? For now<br class="">
I've created aliases for addProjection called both add(...) and<br class="">
reg(...): any better ideas, or a preference to drop one? While I prefer<br class="">
the name "register" to "add", given that addProjection is being retained<br class="">
and that "reg" is not so obvious to remember or interpret, I'm inclined<br class="">
to ditch it. Thoughts?<br class="">
<br class="">
Andy<br class="">
<br class="">
<br class="">
On 24/05/16 14:17, Leif Lönnblad wrote:<br class="">
On 2016-05-24 00:06, Andy Buckley wrote:<br class="">
On 23/05/16 22:31, Frank Siegert wrote:<br class="">
<br class="">
I quite like the picture, but a) the algebraic mapping is not exact<br class="">
because you can't actually do P(P(Event))<br class="">
<br class="">
In fact that was how the original design intended things to work,<br class="">
but it<br class="">
was lost along way. Don't quite remember why.<br class="">
<br class="">
Anyway, I don't mind hiding the word from the users, if they are<br class="">
confused by it.<br class="">
<br class="">
<br class="">
/Leif<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Rivet mailing list<br class="">
<a href="mailto:Rivet@projects.hepforge.org" class="">Rivet@projects.hepforge.org</a><<a href="mailto:Rivet@projects.hepforge.org" class="">mailto:Rivet@projects.hepforge.org</a>> <<a href="mailto:Rivet@projects.hepforge.org" class="">mailto:Rivet@projects.hepforge.org</a>><br class="">
<a href="https://www.hepforge.org/lists/listinfo/rivet" class="">https://www.hepforge.org/lists/listinfo/rivet</a><br class="">
<br class="">
<br class="">
<br class="">
<br class="">
--<br class="">
Dr Andy Buckley, Lecturer / Royal Society University Research Fellow<br class="">
Particle Physics Expt Group, University of Glasgow<br class="">
_______________________________________________<br class="">
Rivet mailing list<br class="">
Rivet@projects.hepforge.org<mailto:Rivet@projects.hepforge.org> <mailto:Rivet@projects.hepforge.org><br class="">
https://www.hepforge.org/lists/listinfo/rivet<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
—<br class="">
<br class="">
Dr. Christian Gütschow<br class="">
<br class="">
TU Dresden<br class="">
Institut für Kern- und Teilchenphysik<br class="">
Zellescher Weg 19<br class="">
01069 Dresden<br class="">
<br class="">
> at CERN: 104-02-C02<br class="">
> at IKTP: E17, ASB<br class="">
> chris.g@cern.ch<mailto:chris.g@cern.ch> <mailto:chris.g@cern.ch><br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
--<br class="">
Dr Andy Buckley, Lecturer / Royal Society University Research Fellow<br class="">
Particle Physics Expt Group, University of Glasgow<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
—<br class="">
<br class="">
Dr. Christian Gütschow<br class="">
<br class="">
TU Dresden<br class="">
Institut für Kern- und Teilchenphysik<br class="">
Zellescher Weg 19<br class="">
01069 Dresden<br class="">
<br class="">
> at CERN: 104-02-C02<br class="">
> at IKTP: E17, ASB<br class="">
> chris.g@cern.ch<mailto:chris.g@cern.ch><br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
<br class="Apple-interchange-newline">
<br class="">
</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
<br class="">
</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
—</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
<br class="">
</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
Dr. Christian Gütschow</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
<br class="">
</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
TU Dresden</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
Institut für Kern- und Teilchenphysik</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
Zellescher Weg 19</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
01069 Dresden</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
<br class="">
</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
> at CERN: 104-02-C02</div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
> at IKTP: E17, ASB<span style="color: rgb(0, 0, 0); font-family: Verdana, Helvetica, Arial, sans-serif; font-size: 11px;" class=""> </span></div>
<div style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;" class="">
> <a href="mailto:chris.g@cern.ch" target="_blank" style="color: rgb(17, 85, 204);" class="">chris.g@cern.ch</a></div>
</div>
<div class=""><br class="">
</div>
</div>
<br class="Apple-interchange-newline">
</div>
<br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<br class="Apple-interchange-newline">
</div>
</div>
<br class="">
</div>
</body>
</html>