'프로그램 사용 > fft, fftw' 카테고리의 다른 글
| fftw wisdom (0) | 2022.11.04 |
|---|---|
| FFT (0) | 2022.10.24 |
| fftw 테스트(tests/bench) (0) | 2022.10.19 |
| fftw cross compile (0) | 2022.10.19 |
| fft (0) | 2020.11.25 |
| fftw wisdom (0) | 2022.11.04 |
|---|---|
| FFT (0) | 2022.10.24 |
| fftw 테스트(tests/bench) (0) | 2022.10.19 |
| fftw cross compile (0) | 2022.10.19 |
| fft (0) | 2020.11.25 |
도대체 저 옵션들은 먼지 모르겠다.
| fftw-3.3.4/tests/bench -o nthreads=2 --verbose=1 --verify 'ok10bx6bx6e11x13b' --verify 'ik10bx6bx6e11x13b' --verify 'obrd7x13v16' --verify 'ibrd7x13v16' --verify 'ofrd7x13v16' --verify 'ifrd7x13v16' --verify '//obcd7x13v16' --verify '//ibcd7x13v16' --verify '//ofcd7x13v16' --verify '//ifcd7x13v16' --verify 'obcd7x13v16' --verify 'ibcd7x13v16' --verify 'ofcd7x13v16' --verify 'ifcd7x13v16' --verify 'okd10bv127' --verify 'ikd10bv127' --verify '//obr240' --verify '//ibr240' --verify '//ofr240' --verify '//ifr240' --verify 'obr240' --verify 'ibr240' --verify 'ofr240' --verify 'ifr240' --verify '//obc240' --verify '//ibc240' --verify '//ofc240' --verify '//ifc240' --verify 'obc240' --verify 'ibc240' --verify 'ofc240' --verify 'ifc240' --verify 'ok11760e00' --verify 'ik11760e00' --verify 'obr33v31' --verify 'ibr33v31' --verify 'ofr33v31' --verify 'ifr33v31' --verify '//obc33v31' --verify '//ibc33v31' --verify '//ofc33v31' --verify '//ifc33v31' --verify 'obc33v31' --verify 'ibc33v31' |
[링크 : https://unix.stackexchange.com/questions/209753/how-do-i-check-if-fftw-installed-correctly]
+
[링크 : https://people.sc.fsu.edu/~jburkardt/c_src/fftw_test/]
[링크 : https://people.sc.fsu.edu/~jburkardt/c_src/fftw_test/fftw_test.html]
| FFT (0) | 2022.10.24 |
|---|---|
| fftw 예제 와 복소수 처리 (0) | 2022.10.19 |
| fftw cross compile (0) | 2022.10.19 |
| fft (0) | 2020.11.25 |
| fftw (0) | 2020.11.25 |
[링크 : https://www.fftw.org/download.html]
| ./configure --prefix=/home/zhouxiaoyong/fftw3_test --disable-fortran --with-slow-timer --host=arm-none-linux-gnueabi --enable-single --enable-neon --enable-shared CC=arm-none-linux-gnueabi-gcc CFLAGS="-march=armv7-a -mfpu=neon -fPIC -ldl -mfloat-abi=softfp" |
[링크 : https://codeantenna.com/a/ztGG77F10Z]
| The basic usage of FFTW is simple. A typical call to FFTW looks like: #include <fftw.h> ... { fftw_complex in[N], out[N]; fftw_plan p; ... p = fftw_create_plan(N, FFTW_FORWARD, FFTW_ESTIMATE); ... fftw_one(p, in, out); ... fftw_destroy_plan(p); } For example, code to perform an in-place FFT of a three-dimensional array might look like: #include <fftw.h> ... { fftw_complex in[L][M][N]; fftwnd_plan p; ... p = fftw3d_create_plan(L, M, N, FFTW_FORWARD, FFTW_MEASURE | FFTW_IN_PLACE); ... fftwnd_one(p, &in[0][0][0], NULL); ... fftwnd_destroy_plan(p); } The following is a brief example in which the wisdom is read from a file, a plan is created (possibly generating more wisdom), and then the wisdom is exported to a string and printed to stdout. { fftw_plan plan; char *wisdom_string; FILE *input_file; /* open file to read wisdom from */ input_file = fopen("sample.wisdom", "r"); if (FFTW_FAILURE == fftw_import_wisdom_from_file(input_file)) printf("Error reading wisdom!\n"); fclose(input_file); /* be sure to close the file! */ /* create a plan for N=64, possibly creating and/or using wisdom */ plan = fftw_create_plan(64,FFTW_FORWARD, FFTW_MEASURE | FFTW_USE_WISDOM); /* ... do some computations with the plan ... */ /* always destroy plans when you are done */ fftw_destroy_plan(plan); /* write the wisdom to a string */ wisdom_string = fftw_export_wisdom_to_string(); if (wisdom_string != NULL) { printf("Accumulated wisdom: %s\n",wisdom_string); /* Just for fun, destroy and restore the wisdom */ fftw_forget_wisdom(); /* all gone! */ fftw_import_wisdom_from_string(wisdom_string); /* wisdom is back! */ fftw_free(wisdom_string); /* deallocate it since we're done */ } } |
| fftw 예제 와 복소수 처리 (0) | 2022.10.19 |
|---|---|
| fftw 테스트(tests/bench) (0) | 2022.10.19 |
| fft (0) | 2020.11.25 |
| fftw (0) | 2020.11.25 |
| ffmpeg fft 분석 예제 (0) | 2020.11.25 |
예를 들어 ls -al을 하려면 아래와 같이 하면 된다.
| $ gdb --args ls -al |
그냥 넣으면 gdb의 옵션으로 해석한다.
| $ gdb ls -al gdb: 인식할 수 없는 옵션 '-al' Use `gdb --help' for a complete list of options. |
| $ gdb --args executablename arg1 arg2 arg3 |
| gdbserver taget (0) | 2023.07.19 |
|---|---|
| gdb conditional break (0) | 2023.07.19 |
| gdb break (0) | 2021.04.09 |
| gdb/insight target window (0) | 2010.05.19 |
| insight/gdb 우분투에서 컴파일하기 실패 - insight/gdb compiling on ubuntu failed (2) | 2010.05.18 |
| docker 이미지 만들기 (0) | 2024.05.08 |
|---|---|
| 도커 cpu 갯수 제한 (0) | 2024.03.22 |
| Dockerfile... 2? (0) | 2019.07.15 |
| docker remote (0) | 2019.07.15 |
| UTS name space (0) | 2019.07.15 |
rfbCheckPasswordByList()는 계정-패스워드 쌍으로 되어있는 값을 이용하여 로그인을 구현하는 기본 함수이다.
희망(?)을 가졌던 newClientHook 이벤트는 시도때도 없이 발생했고(원래 기대했던 것은 로그인 시 1회)
로그인 별로 어떤 계정이 로그인 성공,실패 했는지는 함수를 확장해서 만들어야 할 듯..
newClientHook 에서도 cl->viewOnly가 설정되지 않는 걸 보면, vnc client 측의 설정과는 별개 인 듯
| /* for this method, authPasswdData is really a pointer to an array of char*'s, where the last pointer is 0. */ rfbBool rfbCheckPasswordByList(rfbClientPtr cl,const char* response,int len) { char **passwds; int i=0; for(passwds=(char**)cl->screen->authPasswdData;*passwds;passwds++,i++) { uint8_t auth_tmp[CHALLENGESIZE]; memcpy((char *)auth_tmp, (char *)cl->authChallenge, CHALLENGESIZE); rfbEncryptBytes(auth_tmp, *passwds); if (memcmp(auth_tmp, response, len) == 0) { if(i>=cl->screen->authPasswdFirstViewOnly) cl->viewOnly=TRUE; return(TRUE); } } rfbErr("authProcessClientMessage: authentication failed from %s\n", cl->host); return(FALSE); } |
[링크 : https://libvnc.github.io/doc/html/main_8c_source.html#l00786]
| libvncserver 기본 인자 (0) | 2022.11.04 |
|---|---|
| libvncserver 종료 절차 (0) | 2022.11.01 |
| libvncserver 접속 끊어짐 문제 (0) | 2022.08.16 |
| libvncserver websocket example (0) | 2022.08.12 |
| libvncserver 마우스 이벤트 (0) | 2022.02.25 |
| git stash drop , clear (0) | 2024.09.19 |
|---|---|
| git submodule ... 2? (0) | 2024.06.19 |
| git reset 서버 commit (0) | 2021.09.14 |
| git blame (0) | 2021.06.21 |
| git pull rebase 설정 (0) | 2021.06.02 |
| select current_timestamp(3) |
[링크 : https://stackoverflow.com/questions/9624284/current-timestamp-in-milliseconds]
| NOW([precision]) CURRENT_TIMESTAMP CURRENT_TIMESTAMP([precision]) LOCALTIME, LOCALTIME([precision]) LOCALTIMESTAMP LOCALTIMESTAMP([precision]) |
| mariaDB 설치 실패 (0) | 2025.03.04 |
|---|---|
| mariadb 초기설정 (0) | 2022.08.30 |
| mariadb c# connector (0) | 2021.10.22 |
| HeidiSQL (2) | 2021.08.18 |
| sql zerofill (0) | 2019.11.25 |
| SDRangel can decode multiple broadcast FM channels simultaneously |
[링크 : https://www.reddit.com/r/RTLSDR/comments/ql1jpe/problem_rtl_sdr_recording_multiple_fm_channel/]
| SDRangel is an Open Source Qt5 / OpenGL 3.0+ SDR and signal analyzer frontend to various hardware. |
[링크 : https://github.com/f4exb/sdrangel]
[링크 : https://github.com/f4exb/sdrangelcli]
[링크 : https://github.com/szpajder/RTLSDR-Airband]
[링크 : https://github.com/pvachon/tsl-sdr]
[링크 : https://www.rtl-sdr.com/a-multichannel-fm-demodulator/]
| pulseaudio error : access denied (0) | 2024.08.26 |
|---|---|
| gqrx, gnu radio, rfcat (0) | 2024.08.21 |
| ubuntu 18.04에 사운드 카드가 갑자기 사라졌다? (0) | 2022.07.20 |
| RTL-SDR 11시 땡! (0) | 2022.01.07 |
| gqrx 오디오 스트리밍 (0) | 2022.01.07 |
어쩐지(?) mariadb 설치시 암호를 안물어 본다고 했더니
저런 이상한(?) 스크립트를 추가해놓은 듯.
| $ sudo mysql_secure_installation NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY! In order to log into MariaDB to secure it, we'll need the current password for the root user. If you've just installed MariaDB, and haven't set the root password yet, you should just press enter here. Enter current password for root (enter for none): OK, successfully used password, moving on... Setting the root password or using the unix_socket ensures that nobody can log into the MariaDB root user without the proper authorisation. You already have your root account protected, so you can safely answer 'n'. Switch to unix_socket authentication [Y/n] Enabled successfully! Reloading privilege tables.. ... Success! You already have your root account protected, so you can safely answer 'n'. Change the root password? [Y/n] New password: Re-enter new password: Password updated successfully! Reloading privilege tables.. ... Success! By default, a MariaDB installation has an anonymous user, allowing anyone to log into MariaDB without having to have a user account created for them. This is intended only for testing, and to make the installation go a bit smoother. You should remove them before moving into a production environment. Remove anonymous users? [Y/n] ... Success! Normally, root should only be allowed to connect from 'localhost'. This ensures that someone cannot guess at the root password from the network. Disallow root login remotely? [Y/n] y ... Success! By default, MariaDB comes with a database named 'test' that anyone can access. This is also intended only for testing, and should be removed before moving into a production environment. Remove test database and access to it? [Y/n] y - Dropping test database... ... Success! - Removing privileges on test database... ... Success! Reloading the privilege tables will ensure that all changes made so far will take effect immediately. Reload privilege tables now? [Y/n] y ... Success! Cleaning up... All done! If you've completed all of the above steps, your MariaDB installation should now be secure. Thanks for using MariaDB! |
| mariaDB 설치 실패 (0) | 2025.03.04 |
|---|---|
| mariadb msec 단위 시간 얻기 (0) | 2022.08.31 |
| mariadb c# connector (0) | 2021.10.22 |
| HeidiSQL (2) | 2021.08.18 |
| sql zerofill (0) | 2019.11.25 |