Git Product home page Git Product logo

Comments (6)

dweemx avatar dweemx commented on May 24, 2024

I think srcCoordinatesID and destCoordinatesID can be kept on the front-end and does not have to be sent to the backend. As we know the cell indexes (from cellList) we will be able to send back the corresponding cell indexes for destLoomFile?

from scope.

dweemx avatar dweemx commented on May 24, 2024

Fixed in commit 3a00faa.
This function should give back the indices in destLoomFile of the selected cells from srcLoomFile identified by the indices stored in cellList.

from scope.

kreftl avatar kreftl commented on May 24, 2024

i think i found a bug with relative/absolute paths....
for query
image
i get an error

ERROR:root:Exception calling application: [Errno 2] No such file or directory: 'data\\my-looms\\'
Traceback (most recent call last):
  File "C:\Program Files (x86)\Python36-32\lib\site-packages\grpc\_server.py", line 385, in _call_behavior
    return behavior(argument, context), True
  File "d:\projects\scope\scope-server\scopeserver\modules\gserver\GServer.py", line 407, in getCoordinates
    annotation=request.annotation)
  File "d:\projects\scope\scope-server\scopeserver\modules\gserver\GServer.py", line 209, in get_coordinates
    loom = self.get_loom_connection(loom_file_path)
  File "d:\projects\scope\scope-server\scopeserver\modules\gserver\GServer.py", line 81, in get_loom_connection
    loom_file_path, 10000)
  File "d:\projects\scope\scope-server\scopeserver\modules\gserver\GServer.py", line 60, in get_partial_md5_hash
    with open(file_path, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'data\\my-looms\\'

both are in the same directory

from scope.

kreftl avatar kreftl commented on May 24, 2024

you can test it via f64020b

from scope.

kreftl avatar kreftl commented on May 24, 2024

still no go, this time no error at all, just null
76879bf

from scope.

dweemx avatar dweemx commented on May 24, 2024

You get a null back because you are comparing 2 loom files that do not have any cell IDs in common. Currently the 56k_v6 loom file and 157k_v1 loom file (both build with SCopeLoomPy) do not share the same cell IDs while actually they should (this will be fixed in the future). If you use the 56k_v3_Rbased loom file and the 157k_v3_Rbased loom file (build with SCopeLoomR), translateLassoSelection will work because for these files I updated the cell IDs so that they match. Here is what I get:

screenshot from 2018-03-14 01-41-34

from scope.

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.