-
Notifications
You must be signed in to change notification settings - Fork 0
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
Integrate CPT_2016_Extend-FDK #34
Comments
Hi Jan. Congrats to your defended work! When do you plan to implement the preprocessing kernels? As far as I remember it was planned in April 2017? |
Hello André, sorry for the late response. I'm currently implementing the preprocessing work and I think it should be done before the 1st of May. |
Hallo Jan,
ich bin diese Woche noch mit dem CAETHE Projekttreffen voll ausgelastet. Nächste Woche würde ich gern mit über die aktuelle Implementation drüberschauen.
Gruß, Stephan
From: Jan Stephan [mailto:[email protected]]
Sent: Mittwoch, 26. April 2017 12:25
To: HZDR-FWDF/PARIS
Cc: BodenS; Assign
Subject: Re: [HZDR-FWDF/PARIS] Integrate CPT_2016_Extend-FDK (#34)
Hello André,
sorry for the late response. I'm currently implementing the preprocessing work and I think it should be done before the 1st of May.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#34 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/ATP0x-u5pegzYNxraxHsAEsyoc54rseZks5rzxuXgaJpZM4Lyzji> . <https://github.com/notifications/beacon/ATP0x4ZZ01BSK2ZEzJOqSBP1U5TDvUehks5rzxuXgaJpZM4Lyzji.gif>
|
@j-stephan: Okay, that sounds very good. After Stephan verified the new code a new release should be performed. Please try to finish this topic asap to start with the new Fan2Par implementation that is important for the ray beam correction. Maybe you could start while Stephan is verifying the new code. |
Hallo Jan, bitte melde Dich mal bei mir. |
The results look promising, so they should be integrated into one of the next releases.
The text was updated successfully, but these errors were encountered: