Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
pygwinc
pygwinc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 7
    • Merge Requests 7
  • 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
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gwinc
  • pygwincpygwinc
  • Issues
  • #93

Closed
Open
Created Mar 01, 2021 by Lee McCuller@lee-mccullerMaintainer

Quantum Noise h_SQL should be defined in terms of sustf.tst_suscept

Now that the radiation pressure is properly calculated from the testmass susceptibility, the SQL factor used should not be the analytical value calculated under the free mass assumption.

line 300 from quantum.py should go from h_SQL = sqrt(8 * hbar / (m * (Omega * L)**2)) # SQL Strain

to

h_SQL = sqrt(8 * hbar / L**2 * abs(sustf.tst_suscept)) # SQL Strain

It's a pretty small adjustment to the noise, only about .2% around 10Hz in the aplus model. I'd like this since A) it is correct and B) quantum code I'm working on needs correct comparisons.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None