Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

nanograv / PINT Public

Notifications You must be signed in to change notification settings
Fork 101
Star 124

Code
Issues 157
Pull requests 23
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Home

Jump to bottom Edit New page

Paul Ray edited this page Feb 12, 2015 · 21 revisions

PINT is not TEMPO3

Coding Practices
Python Compatibility
Code Architecture
Installation Notes

Add a custom footer

Toggle table of contents Pages 13

Home
Clock Corrections and Timescales in PINT
Code Architecture
Discussion of Control Parameters
Git Workflow
How To
How To: Common Timing Workflow
How To: Simple Python PINT Tools
Modern Par File Format
Observatory Special Cases
PINT vs. TEMPO(2) par file changes
Python Compatibility
Tagging PINT Versions

Add a custom sidebar

Clone this wiki locally

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.