Bug #1717

Core: GISASSimulation: setBeamParameters and setDetectorParameters have opposite order of alpha, phi

Added by wuttke about 4 years ago. Updated 3 months ago.

Status:RejectedStart date:02 Dec 2016
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

For each choice I can guess a reason. Nonetheless it's confusing and potentially misleading.

One solution could be to remove parameter phi_i from setBeamParameters for good (cf #1716).

History

#1 Updated by wuttke about 4 years ago

  • Description updated (diff)

#2 Updated by pospelov about 3 years ago

  • Status changed from Rfc to Rejected

Rejected, see #1823

#3 Updated by wuttke 3 months ago

  • Subject changed from GISASSimulation: setBeamParameters and setDetectorParameters have opposite order of alpha, phi to Core: GISASSimulation: setBeamParameters and setDetectorParameters have opposite order of alpha, phi
  • Parent task deleted (#1566)

Also available in: Atom PDF