- Joined
- Apr 6, 2015
- Messages
- 250 (0.07/day)
- Location
- Japan
| System Name | ChronicleScienceWorkStation |
|---|---|
| Processor | AMD Threadripper 1950X |
| Motherboard | Asrock X399 Taichi |
| Cooling | Noctua U14S-TR4 |
| Memory | G.Skill DDR4 3200 C14 16GB*4 |
| Video Card(s) | AMD Radeon VII |
| Storage | Samsung 970 Pro*1, Kingston A2000 1TB*2 RAID 0, HGST 8TB*5 RAID 6 |
| Case | Lian Li PC-A75X |
| Power Supply | Corsair AX1600i |
| Software | Proxmox 6.2 |
FYI,
https://en.m.wikipedia.org/wiki/Digital_down_converter
To add to the diagram, a raw input vector will be sent to GPU (VRAM), then got multiplied by a sin and cos vector with the same number of points, element-wise.
The two product vectors are then sent back to the host (RAM).
In practice, I tried to use something called DMA transfer which ideally does not read or write the data from host until run-time, and it should reduce overhead and allowed the read/write to happen together.
For DDC itself, more processing like decimation can be done to reduce the output vector we return from GPU to host, but the feeding of the raw input vector cannot be avoided.
https://en.m.wikipedia.org/wiki/Digital_down_converter
To add to the diagram, a raw input vector will be sent to GPU (VRAM), then got multiplied by a sin and cos vector with the same number of points, element-wise.
The two product vectors are then sent back to the host (RAM).
In practice, I tried to use something called DMA transfer which ideally does not read or write the data from host until run-time, and it should reduce overhead and allowed the read/write to happen together.
For DDC itself, more processing like decimation can be done to reduce the output vector we return from GPU to host, but the feeding of the raw input vector cannot be avoided.
Last edited:
