Difference: OldSctDSPBugs (3 vs. 4)

Revision 42010-02-16 - BruceGallop

Line: 1 to 1
 
META TOPICPARENT name="AldenStradling"

Old SCT ROD DSP Bugs and Feature Requests

Line: 6 to 6
 
  1. Setting variable MVAR_PRESENT doesn't disable the appropriate formatter enable bit

To Do List:

Added:
>
>
o Give this page a nicer name

o Use savannah (project atlassctroddaq) for bugs

  o S-curve fitting on the SDSPs
Added:
>
>
  • An analytical fit is probably enough and easy to do, the main work is in transferring the data to the remainder of the system (make a FitScanResult) and making it understood
  o Sort out the CVS repository (or just move to SVN)

o Expand physics mode scan:

  1. Now using 1 SDSP to do histogramming
Changed:
<
<
  1. Restructuring of the code to exploit using multiple SDSPs (this should be possible with the current code)
>
>
  1. Mostly teaching the SctApi code to exploit different options
    • eg different trigger type on multiple SDSPs (this should be possible with the current DSP code)
 
Changed:
<
<
o Queue up primitives
>
>
o Queue up primitives - Bruce in progress
 
Changed:
<
<
o Modifications to the Mark / Space Ratio Test
>
>
o Noise occupancy (different number of triggers per bin) is implemented as three scans running on top of each other. If the DSP knew the number of triggers for each bin this would be simpler

o Implement further analysis of optical scans in DSP

  • Currently only for 2D RX scan, printed to text buffer and therefore ignored
  o Compress the data (don't use gzip but choose something smaller and quicker)
Added:
>
>
  • NB working on this should be balanced against reduction of information via analysis
  o Module masking primitive
Line: 29 to 41
 
  1. Move code around to optimize further; ICODE to XCODE and vice-versa
  2. How much memory do we really have?
Added:
>
>
  1. How does the boot loader work? - Bruce almost worked it out
  2. Hence, would building the array of primitive functions at compile time save space?
  o Crashes during calibration scans:
Changed:
<
<
  1. How and why do the scans crash?
>
>
  1. How and why do the scans crash? (hit error and chip sequence error?)
 
  1. Check the formatter and then mask off the link?
Changed:
<
<

>
>
o Teach DSP and SctApi to communicate better about what the DSP is doing
  1. Several flags are set by the DSP and unused by SctApi (are they consistent enough?)
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback