Skip to content
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

Tracking setup plots flatline for all channels in subbands 51 and 75 for all 500 MHz bands #97

Open
swh76 opened this issue Sep 19, 2019 · 1 comment
Labels

Comments

@swh76
Copy link
Collaborator

swh76 commented Sep 19, 2019

The tracked frequency in tracking_setup plots in DSPv3 fw is a flat line for any channels which fall in subbands 51 and 75, but the channels are actually able to track (we know this because in Frankenpolar a couple of these channels are TES-coupled and we can read out TESs on them just fine). Additional details in this JIRA ticket - https://jira.slac.stanford.edu/browse/ESCRYODET-391.

Mitch looked at this some yesterday and found that even though the tracking setup plots for two channels in subband 75 look like this ;

image (1)

but when he plotted all tracking setup data it looks like this (with no other channels on):

f, df, sync = S.tracking_setup(band=band,reset_rate_khz=4, lms_freq_hz=20129.4, \
                               fraction_full_scale=0.540, make_plot=True, show_plot=True, \
                               save_plot=True,channel=S.which_on(band),nsamp=2**18, \
                               feedback_start_frac=0.2,feedback_end_frac=0.98,lms_gain=6)
plt.plot(f)

image (2)

so the channels are tracking, and the data is there, we must just have the channel mapping from fw to pysmurf wrong, for at least subbands 51 and 75, somewhere. @jmdewart wonders if part of the issue may be the mapping from the 416 DSP channels in fw to the 512 pysmurf channels.

@swh76 swh76 pinned this issue Dec 16, 2019
@eyyoung24
Copy link
Contributor

In [26]: S.which_on(2)
Out[26]: 
array([  0,  15,  16,  23,  31,  32,  47,  48,  55,  63,  64,  79,  80,
        87,  95,  96, 111, 112, 119, 127, 128, 143, 144, 151, 160, 176,
       183, 256, 271, 272, 279, 288, 303, 311, 319, 320, 335, 336, 343,
       352, 367, 375, 383, 384, 399, 400, 407, 416, 431, 471])

In [27]: sb = np.zeros_like(S.which_on(2))

In [28]: for i, ch in enumerate(S.which_on(2)):
    ...:     sb[i] = S.get_subband_from_channel(2, ch)
    ...: 
In [29]: sb
Out[29]: 
array([63, 55, 67, 51, 59, 65, 57, 69, 53, 61, 63, 55, 67, 51, 59, 65, 57,
       69, 53, 61, 63, 55, 67, 51, 65, 69, 53, 64, 56, 68, 52, 66, 58, 54,
       62, 64, 56, 68, 52, 66, 58, 54, 62, 64, 56, 68, 52, 66, 58, 52])

So it looks like these are all within the desired subband.

1576545855_FRtracking_band2_ch000
1576545855_FRtracking_band2_ch015
1576545855_FRtracking_band2_ch016
1576545855_FRtracking_band2_ch023
1576545855_FRtracking_band2_ch031
1576545855_FRtracking_band2_ch032
1576545855_FRtracking_band2_ch047
1576545855_FRtracking_band2_ch048
1576545855_FRtracking_band2_ch055
1576545855_FRtracking_band2_ch063
1576545855_FRtracking_band2_ch064
1576545855_FRtracking_band2_ch079
1576545855_FRtracking_band2_ch080

@agustiner agustiner unpinned this issue Oct 18, 2021
@agustiner agustiner pinned this issue Oct 18, 2021
@agustiner agustiner added the SLAC label Nov 5, 2021
@agustiner agustiner unpinned this issue Mar 9, 2022
@swh76 swh76 pinned this issue Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants