Home
last modified time | relevance | path

Searched full:patterns (Results 1 – 25 of 194) sorted by relevance

12345678

/cmsis-dsp-latest/Testing/PatternGeneration/
DExample.py6 # generating test patterns.
10 # This function is generating patterns for an addition
16 # So, we generate two long patterns and in the different tests we may load
24 # We normalize the data to ensure that the q31, q15 and q7 patterns won't
29 # The input patterns are written. The writeInput function of the config object is
48 # This function is generating patterns for all the types
51 # We define the path to the patterns.
54 # By default, the root folder for pattern is Patterns and the root one for
60 PATTERNDIR = os.path.join("Patterns","Example","ExampleCategory","ExampleCategory")
70 # Test patterns for each config are generated.
DBIQUAD.py9 # Those patterns are used for tests and benchmarks.
71 # Write test with fixed and known patterns
113 # Now random patterns to test different tail sizes
176 PATTERNDIR = os.path.join("Patterns","DSP","Filtering","BIQUAD","BIQUAD")
DDecimate.py16 # Those patterns are used for tests and benchmarks.
17 # This is containing patterns for decimation and interpolation
41 PATTERNDIR = os.path.join("Patterns","DSP","Filtering","DECIM","DECIM")
228 PATTERNDIR = os.path.join("Patterns","DSP","Filtering","DECIM","DECIM")
DController.py7 # Those patterns are used for tests and benchmarks.
21 PATTERNDIR = os.path.join("Patterns","DSP","Controller","Controller")
DFIR.py8 # Those patterns are used for tests and benchmarks.
98 PATTERNDIR = os.path.join("Patterns","DSP","Filtering","FIR","FIR")
DComplexMaths.py7 # Those patterns are used for tests and benchmarks.
104 PATTERNDIR = os.path.join("Patterns","DSP","ComplexMaths","ComplexMaths")
DTransform.py7 # Those patterns are used for tests and benchmarks.
105 PATTERNDIR = os.path.join("Patterns","DSP","Transform","Transform")
/cmsis-dsp-latest/Testing/
DREADME.md104 #### R5 : The test description shall list the test patterns and input patterns required by the tests
135 #### R12 : The tested function should not know where are the patterns and how to get them
168 The patterns, output of tests, parameters are also following a hierarchical structure. But they do …
193 A test is requiring input patterns, reference patterns and outputs (to be compared to the reference…
345 According to R12 and R15, tests do not know how to access patterns. It is a responsiblity implement…
347 IO is about loading patterns and dumping output. It is not about IO in general.
352 Patterns is the interface to patterns and output from the test point of view.
364 But it means that no test using patterns shoudl be used in the middle of the test or some part of i…
388 ### Generate the test patterns in Patterns folder
390 We have archived lot of test patterns on github. So this step is needed only if you write new test …
[all …]
Dtestmain.cpp24 // char* array describing the tests and the input patterns.
25 // Reference patterns are ignored in this case.
34 int testmain(const char *patterns) in testmain() argument
50 Client::FPGA io(testDesc,patterns); in testmain()
52 Client::Semihosting io("../TestDesc.txt","../Patterns","../Output","../Parameters"); in testmain()
Dpatterndata.c8 #include "Patterns.h"
10 const char *patternData=(const char*)patterns;
/cmsis-dsp-latest/Testing/TestScripts/
DCodeGen.py172 # Generate the pattern ID for patterns
176 for p in root.patterns:
291 The number of patterns path is generated
292 The patterns names are generated
374 # Generate patterns path
375 textFile.write("%d\n" % len(root.patterns))
376 for (patid,patpath) in root.patterns:
434 It is used to dump input patterns in include files
467 It is used to dump input patterns in include files
493 It is used to dump input patterns in include files
[all …]
DParser.py15 patterns (list) : List of pairs
37 self.patterns=[]
92 # for the patterns or output of a group of suite)
243 self.patterns.append((theId,thePath))
245 #print(self.patterns)
258 #print(self.patterns)
/cmsis-dsp-latest/Testing/Include/Tests/
DExampleCategoryF32.h24 There are always some input patterns, some reference patterns
33 /* Input patterns */
41 /* Reference patterns */
DComplexTestsQ15.h19 // Reference patterns are not loaded when we are in dump mode
23 // Reference patterns are not loaded when we are in dump mode
DComplexTestsQ31.h18 // Reference patterns are not loaded when we are in dump mode
22 // Reference patterns are not loaded when we are in dump mode
/cmsis-dsp-latest/Testing/DebugScripts/
Ddebug.py10 # Example script to read patterns and test outputs
29 …inputPath = os.path.join("Patterns","DSP","Transform","Transform%s" % args.f.upper(),"ComplexInput…
30 …refPath = os.path.join("Patterns","DSP","Transform","Transform%s" % args.f.upper(),"ComplexInputSa…
34 …inputPath = os.path.join("Patterns","DSP","Transform","Transform%s" % args.f.upper(),"ComplexInput…
35 …refPath = os.path.join("Patterns","DSP","Transform","Transform%s" % args.f.upper(),"ComplexFFTSamp…
Ddebugbiquad.py20 inputPath = os.path.join(parent_dir,"Patterns","DSP","Filtering","BIQUAD","BIQUAD%s" % f.upper(),"B…
21 refPath = os.path.join(parent_dir,"Patterns","DSP","Filtering","BIQUAD","BIQUAD%s" % f.upper(),"Biq…
/cmsis-dsp-latest/Testing/FrameworkInclude/
DTest.h39 // It is used when importing patterns and we want to read
63 /* In Dump only, reference patterns are never read.
266 to identify patterns in a suite and know
347 /** Import list of patterns from the driver
352 combined with the path to identify patterns in other part of the class.
391 // It knows how to import patterns into memory or dump
397 // In theory they should only be visible to Patterns
471 /** Free all allocated patterns.
548 // (Load input and reference patterns)
/cmsis-dsp-latest/Testing/Source/Tests/
DExampleCategoryF32.cpp54 setUp function is used to load the patterns and create required buffers
78 /* Load patterns with all samples */ in setUp()
86 /* Load patterns with 9 samples */ in setUp()
DBasicTestsF16.cpp11 Reference patterns are generated with
322 // Must be coherent with Python script used to generate test patterns in setUp()
331 // Must be coherent with Python script used to generate test patterns in setUp()
340 // Must be coherent with Python script used to generate test patterns in setUp()
DBasicTestsF32.cpp9 Reference patterns are generated with
313 // Must be coherent with Python script used to generate test patterns in setUp()
321 // Must be coherent with Python script used to generate test patterns in setUp()
329 // Must be coherent with Python script used to generate test patterns in setUp()
DBasicTestsF64.cpp9 Reference patterns are generated with
313 // Must be coherent with Python script used to generate test patterns in setUp()
321 // Must be coherent with Python script used to generate test patterns in setUp()
329 // Must be coherent with Python script used to generate test patterns in setUp()
/cmsis-dsp-latest/.github/workflows/
Druntest.yaml72 python processTests.py -gen . -p Patterns -d Parameters -f Output.pickle -e
73 python processTests.py -gen . -p Patterns -d Parameters -f Output_f16.pickle -e
/cmsis-dsp-latest/Testing/FrameworkSource/
DIORunner.cpp213 // Read list of patterns in run()
266 // setUp will generally load patterns in run()
317 // since the reference patterns are not loaded in run()
330 // since the reference patterns are not loaded in run()
DArrayMemory.cpp148 indirectly unvalidating all patterns.
149 If the patterns are not reloaded after this, they'll return NULL

12345678