GithubHelp home page GithubHelp logo

Comments (4)

TomTomRixRix avatar TomTomRixRix commented on May 29, 2024 1

Regarding the field of view from device: Given the suggested implementation as a list as in #11, one could implement an abstract function get_field_of_view() which must be implemented by each device. This function can then be used in the reconstruction algorithm for determining the dimensions of the reconstructed image like this:

field_of_view = pa_device.get_field_of_view()
xdim = field_of_view[1]-field_of_view[0]/sensor_spacing_in_mm
ydim = field_of_view[3]-field_of_view[2]/sensor_spacing_in_mm
zdim = field_of_view[5]-field_of_view[4]/sensor_spacing_in_mm

As a backup, e.g. if the function returns None or raises an exception one could use the current computation of the reconstruction size.

from simpa.

TomTomRixRix avatar TomTomRixRix commented on May 29, 2024

At the moment some functions use numpy arrays others torch tensors. In particular, pre- and post-processing is done in numpy while functions used during reconstruction require torch tensors. It might be worth providing all functions for both, numpy arrays and torch tensors, if possible.

from simpa.

TomTomRixRix avatar TomTomRixRix commented on May 29, 2024

@jgroehl @kdreher All features except of the field of view are implemented and ready for review on branch T28377-improved-DAS (still having the old naming convention 😕). There are also some small design questions that may be discussed, so having a short meeting would be cool.

from simpa.

kdreher avatar kdreher commented on May 29, 2024

I had a look at the code and I have only minor comments:

PyTorchDASAdapter.py:

  • l88 It should be checked for the device position in the settings and only if it is not given by the user, set it to the default value
  • l167 remove redundant parentheses
  • l178 we should only get an apodization factor if it is specified in the settings -> move this code block to l188 when the apodization is used and only multiply with the values if it is given in the settings. Thus, we can save one matrix multiplication with only ones (output of get_apodization_factor if no apodization is given)
  • l207 function names should be lowercase

signal_processing.py:

  • l95 variable names should be lowercase

Finally, also add the TestProcessing.py file to the framework tests in do_coverage.py

from simpa.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.