Closed hnordquist closed 7 years ago
It's because the unnormalized values are not retained, they need to be recalculated when pulled in from the database . I was working on this when I stopped earlier this year. We use the NDATest branch here.
Sent from my iPhone
On 26 Sep 2017, at 19:07, "notifications@github.commailto:notifications@github.com" notifications@github.com<mailto:notifications@github.com> wrote:
I did an acquire| rates with an LM instrument from file pairs. That all worked.
Subsequently, I did an acquire | rates from the db, using the resultant rates measurement. On cycle 2, there were not the same number of values in the AMult as the RAMult, so it crashed going over edge of array. Will have to see if this is a result of how the hits are computed in LM or something else entirely.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/hnordquist/INCC6/issues/156, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGpMngWfORI89NfETzFM1L84ktF-4nPUks5smS8zgaJpZM4PklA0.
This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
It doesn't matter that they aren't retained. How does the AMult and RAMult distribution array return different #s of values?
Input values must be different, (counts, coefficients and ?) my first guess.
Sent from my iPhone
On 26 Sep 2017, at 19:35, "notifications@github.commailto:notifications@github.com" notifications@github.com<mailto:notifications@github.com> wrote:
It doesn't matter that they aren't retained. How does the AMult and RAMult distribution array return different #s of values?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/hnordquist/INCC6/issues/156#issuecomment-332275630, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGpMnlWAg9DqBC-OWMW0PynTkCjlHbagks5smTWOgaJpZM4PklA0.
This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
The coefficients are different the second time, but still, how would that make the distribution a different length for the RA than for the A? Do you see what I'm saying?
I'm going to try this as a pure shift register next. The one I was doing was LM from a pulse pair input.
On Wed, Sep 27, 2017 at 12:18 AM, J F Longo notifications@github.com wrote:
Input values must be different, (counts, coefficients and ?) my first guess.
Sent from my iPhone
On 26 Sep 2017, at 19:35, "notifications@github.com<mailto: notifications@github.com>" <notifications@github.com<mailto: notifications@github.com>> wrote:
It doesn't matter that they aren't retained. How does the AMult and RAMult distribution array return different #s of values?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/ hnordquist/INCC6/issues/156#issuecomment-332275630, or mute the thread< https://github.com/notifications/unsubscribe-auth/AGpMnlWAg9DqBC- OWMW0PynTkCjlHbagks5smTWOgaJpZM4PklA0>.
This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/hnordquist/INCC6/issues/156#issuecomment-332420475, or mute the thread https://github.com/notifications/unsubscribe-auth/AFqkLzKDvl48R_vZ_NXxchbXA1pyWkeMks5smei9gaJpZM4PklA0 .
RA, A and Un-normalized A can have differing lengths, and often do. The distribution length of each distribution changes if the either the gatewidth or the deadtime coefficient C (aka T) changes. Also you can have runs of 0s followed by positive counts and so the length of each distro must account for that condition. The DB and AB-related code handles all these conditions. That is all I know. Martyn or Daniela or Johnathon Dowell (is he still available there?) can discuss much better.
This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
no changes made in coeff c, only a and b. also using same gate. I will talk to Martyn today. Daniela is out.
On Wed, Sep 27, 2017 at 5:46 AM, J F Longo notifications@github.com wrote:
RA, A and Un-normalized A can have differing lengths, and often do. The distribution length of each distribution changes if the either the gatewidth or the deadtime coefficient C (aka T) changes. Also you can have runs of 0s followed by positive counts and so the length of each distro must account for that condition. The DB and AB-related code handles all these conditions. That is all I know. Martyn or Daniela or Johnathon Dowell (is he still available there?) can discuss much better.
This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/hnordquist/INCC6/issues/156#issuecomment-332495436, or mute the thread https://github.com/notifications/unsubscribe-auth/AFqkL5J5G9Wbwr7-vOsAncDDXffHi2yNks5smjWcgaJpZM4PklA0 .
I did an acquire| rates with an LM instrument from file pairs. That all worked.
Subsequently, I did an acquire | rates from the db, using the resultant rates measurement. On cycle 2, there were not the same number of values in the AMult as the RAMult, so it crashed going over edge of array. Will have to see if this is a result of how the hits are computed in LM or something else entirely.