Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
L
lalsuite
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 113
    • Issues 113
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 33
    • Merge Requests 33
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lscsoft
  • lalsuite
  • Merge Requests
  • !1347

Merged
Created Jun 09, 2020 by Matthew David Pitkin@matthew-pitkinDeveloper1 of 4 tasks completed1/4 tasks

Allow glitch and timing noise pulsar phase evolution as inputs to HeterodynedPulsarGetModel

  • Overview 2
  • Commits 29
  • Pipelines 16
  • Changes 7

Description

The model of a pulsar's phase evolution can include components that model pulsar glitches and also that model timing noise (FITWAVES parameters in TEMPO2). These can be precomputed and then added together to get the full pahse evolution. This is currently done in the lalapps pulsar model (ppe_model.c in lalapps/src/pulsar/HeterodynedSearch), but was not included in the version ported into lalpulsar. This MR updates the HeterodynedPulsarGetModel function to allow these components to be passed to it. It also updates the equivalent Python API for the producing the simulated signals.

These functions are currently not use in any production code, so changes to the API do not affect any search code. I will be adding some tests of these to show that they work correctly.

API Changes and Justification

Backwards Compatible Changes

  • This change introduces no API changes
  • This change adds new API calls

Backwards Incompatible Changes

  • This change modifies an existing API
  • This change removes an existing API

No production code yet uses these functions, so the API changes will not affect any search codes.

Review Status

cc @karl-wette @david-keitel - I'll have some tests to add to this MR soon.

Edited Jun 15, 2020 by Matthew David Pitkin
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fitwaves