Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get time info from TIB #229

Merged
merged 3 commits into from
Nov 24, 2019
Merged

Get time info from TIB #229

merged 3 commits into from
Nov 24, 2019

Conversation

morcuended
Copy link
Member

Until the timing information from UCTS is well tested and trustable, we will use only TIB time information for the time being (see #227)

@rlopezcoto
Copy link
Contributor

thanks @morcuended! I'll wait for @FrancaCassol to have a look to be on the same page regarding PR#15 on ctapipe_io_lst. Then we need to

  • merge the codes
  • make a new ctapipe_io_lst release
  • update ctapipe_io_lst version on cta-lstchain
  • make a new cta-lstchain release
    I can do that during the morning as soon as the codes are approved

# # UCTS timestamps are nanoseconds in UNIX timestamp format and must be given in seconds
# utc_time = Time(datetime.utcfromtimestamp(ucts_timestamp / 1e9))
# else:
start_ntp = event.lst.tel[telescope_id].svc.date
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, now it avoids UCTS time and uses TIB time. This is what you were using before you incorporated UCTS time, right? If so, it seems ok to me.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is how I was first taking time info

Copy link
Collaborator

@labsaha labsaha Nov 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, it is then already tested. It should be fine then. Let's then wait for @FrancaCassol's comments

@FrancaCassol
Copy link
Collaborator

After the merging of `https://github.com/cta-observatory/ctapipe_io_lst/pull/15 one can simplify the code just using the R0/R1 event trigger_time which is now the TIB time (TAI time in s).
So when we will move to UCTS time this part of code must not be updated

@morcuended
Copy link
Member Author

Yes @FrancaCassol , I will fix it

@morcuended
Copy link
Member Author

After the merging of `https://github.com/cta-observatory/ctapipe_io_lst/pull/15 one can simplify the code just using the R0/R1 event trigger_time which is now the TIB time (TAI time in s).
So when we will move to UCTS time this part of code must not be updated

@FrancaCassol @rlopezcoto I just modified the code to take directly the time info from the trigger_time field. Please have a look.

Copy link
Contributor

@rlopezcoto rlopezcoto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good to me, thanks @morcuended! I'll wait for @FrancaCassol to have a look.

@FrancaCassol
Copy link
Collaborator

Yes! That's fine

@rlopezcoto rlopezcoto merged commit ffd42a9 into cta-observatory:master Nov 24, 2019
@morcuended morcuended deleted the fix_time branch November 26, 2019 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants