Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

performances issues in the plant editor #121

Open
chmouton opened this issue Oct 10, 2013 · 2 comments
Open

performances issues in the plant editor #121

chmouton opened this issue Oct 10, 2013 · 2 comments

Comments

@chmouton
Copy link

Dear All,

We met performances issues in the plant editor : the left part contains components and occurrences of components, it works nicely when there are only a few of them but when all the items of the catalogs are loaded, the browser fails and crashes.

Thomas proposes the following leads:

  • not loading all the components and occurrences of components in the tree but only the ones corresponding to a result of the search tool: is it possible to add a "search" button close to the text field at the right-bottom and then send back the value of the text filed to the uri /occurences_de_composant?search=value
  • this URI answers with a JSON dictionary with the idFonct of the search results and the associated URI.
  • for each occurrence of component, it's possible to obtain the x3d mesh with
    /get_x3dmesh_for_occurrence?uri=....... with the uri of the occurrence.

Is it also possible to update the "store" function which will store all the occurrences in the 3D scene with their location and orientation?

  • il faut de plus que l'IGD mette à jour la fonction "Store" qui doit sortir l'ensemble des occurrences placées, leur position et leur rotation.

Thomas will send his code this evening.

Is it possible to help us on those issues?
Kind regards

@tpaviot
Copy link
Contributor

tpaviot commented Oct 11, 2013

Related code pushed to the bitbucket repos. Three updates :

http://192.168.1.1:8080/component_editor?idFonct=LL400V.S.Realim.F1.ProtAvion : edit the occurrence de composant with idFonct

http://192.168.1.1:8080/get_x3dmesh_for_occurrence?uri=http://localhost:9000/rest/composant/582
Get the x3dmesh for the occurrence with the given uri.

http://192.168.1.1:8080/occurrences_de_composant?search=Rob2V : returns the occurrences uri and composant type uris for the matching occurrences.

@mlimper
Copy link
Contributor

mlimper commented Oct 11, 2013

Thanks!
The search function already works now in my current state of the plant editor, I have inserted a button next to the search bar.

In the second call, should there be a URI to a "composant" provided? Or to an "occurence"? Or does both work? :-)

I guess it also doesn't work because my database does not contain the respective links to example 3D meshes, here's what I get:

Traceback (most recent call last):
[...]
get_x3d_from_occurrence_de_composant
geom_mpa_uri = occurrence.find('representationsGeometriques3D').text
AttributeError: 'NoneType' object has no attribute 'text'

Do you have some small test data which also contains 3D meshes? Otherwise, I guess I'd need to use REST PUT commands to connect my geometrietesselee example meshes to the server, but I'm not really sure where to do this (the relation between "occurenceDeComposant", "geometrietesselee" and "representationsGeometrique" is not fully clear to me). A small test set (database file?) would probably be of great help, we could then also compare our results in a more consistent way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants