[Hps] Run Sheet

[Nelson, Timothy Knight]

I can see both sides of this.  It’s clearly undesirable to have it generally writable but I do like to be able to see how data taking is going.  As long as it isn’t generally writable, I don’t see the problem.  The instance where the table was re-ordered was an accident by someone that didn’t imagine that the spreadsheet could be writable by them.  Meanwhile, edits are logged and old versions are automatically backed up (under File / See Revision History) so the any editing errors can certainly be recovered from.

If this were the only information we had about our data, or even the definitive source of information, I would be more worried.  However, it isn’t, which is a very good thing since I don’t believe the information in the spreadsheet is anywhere near 100% reliable in any case.

Tim

> On May 7, 2015, at 11:09 AM, Stepan Stepanyan <stepanya at jlab.org> wrote:
> 
> Hi Maurik,
> 
> Yes, I do. First I think all the PCs in counting room has office and I 
> personally have
> used the office spreadsheet on couple of them. The update should not be 
> so difficult,
> it could be part of RCs activities together with wiki updates.
> 
> Other day we found that someone outside reorder the table, may be not a 
> big deal
> but who knows what else could happen.
> 
> Generally I appose to have people from outside changing things that are 
> related
> to the run process that is controlled and managed in the counting house 
> without Rc
> or shift expert knowing about. The outsider may not know the status of 
> things, clearly.
> 
> Of course many people will disagree with me, but any experiment I have 
> been, no one
> could change anything on the ongoing run related stuff without knowledge 
> of RC.
> When we have only one place our production run log and people can freely 
> make
> changes from outside, it is scary, even if the person is a collaborator.
> 
> Regards, Stepan
> 
> On 5/7/15 1:51 PM, Maurik Holtrop wrote:
>> Hi Stepan,
>> 
>> There are a few reasons why we use Google Docs for this. One reason is that there isn’t a copy of something like Excel installed on the systems in the counting house. Another reason is that several people requested a way to have access to the run sheet, and a locally saved copy wouldn’t be updated frequently enough on an externally available location. I think the current solution works well. Do you have objections?
>> 
>> Best,
>> 	Maurik
>> 
>> 
>> 
>>> On May 7, 2015, at 1:09 PM, Stepan Stepanyan <stepanya at jlab.org> wrote:
>>> 
>>> Maurik,
>>> 
>>> I was very surprised to learn day before yesterday during my shift that
>>> we are using
>>> this type of recording. Why we cannot have locally saved copy and make
>>> the list
>>> available outside for reading through our collaboration regular pages.
>>> 
>>> Stepan
>>> 
>>> On 5/7/15 12:59 PM, Maurik Holtrop wrote:
>>>> Dear HPS,
>>>> 
>>>> The run sheet that we have been using and filling from the counting house was up until now “world writable”, which means that anyone with the URL could edit these tables. This is probably a bit too open, even for us.
>>>> 
>>>> I just changed the permission on this table to “world readable”, so that everyone can still see the page, and it is writable by “heavyphotonsearch at gmail.com” with the usual hpsrun password. If you plan on modifying these tables outside of the counting house, please send me an email with your google account and I will give you write permission.
>>>> 
>>>> Best,
>>>> 	Maurik
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Hps mailing list
>>>> Hps at jlab.org
>>>> https://mailman.jlab.org/mailman/listinfo/hps
>>> _______________________________________________
>>> Hps mailing list
>>> Hps at jlab.org
>>> https://mailman.jlab.org/mailman/listinfo/hps
> 
> _______________________________________________
> Hps mailing list
> Hps at jlab.org
> https://mailman.jlab.org/mailman/listinfo/hps