Commit 2e0170fb authored by Mitch Burnett's avatar Mitch Burnett
Browse files

fix hardcoded fft size passed to pfb library

still want to work and look into if this is the best way to architecture
all the components if a plugin approach is chosen.
parent a5dacd73
1 merge request!1refactor build script and integrate pfb/correlator
Showing with 15 additions and 3 deletions
+15 -3
......@@ -65,12 +65,16 @@ if not meson.is_subproject()
pfb = subproject('pfb',
required: true,
default_options: ['LIB_ONLY=@0@'.format(shared_only)])
default_options: ['LIB_ONLY=@0@'.format(true)])
pfb_dep = pfb.get_variable('pfb_lib_dep')
pfb_nfft = 256
pfb_ntap = 8
# mcb: rework how the pfb configs are built and included. Right now the pfb
# meson.build doesn't write (touch) pfb_config.h if it is a subproject. So to
# get the subproject configured means that the top-level rtbf needs it as an
# option(is this right? is there a better way?)
pfb_nfft = get_option('PFB_NFFT')
pfb_ntap = get_option('PFB_NTAP')
pfb_ntime = rtbf_ntime
pfb_ninputs = rtbf_nbeam
pfb_nbin_inputs = rtbf_nbin
......
......@@ -17,3 +17,11 @@ option('XB_INPUT_PER_FID', type: 'integer', min: 2, max: 16, value: 12,
option('XB_TIME_PER_FID', type: 'integer', min: 1, value: 14,
description: 'time samples per network packet')
# mcb: temporarily present in rtbf until decided how architecture of building
# all libraries is determined
option('PFB_NFFT', type: 'integer', value: 256,
description: 'pfb transform size (number of polyphase branches)')
option('PFB_NTAP', type: 'integer', value: 8,
description: 'taps per polyphase branch in the pfb')
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment