-
-
Notifications
You must be signed in to change notification settings - Fork 432
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
3d vectors do not plot correctly in threejs #29206
Comments
comment:1
REPORTED BY: Ingo Dahn ingodahn@gmail.com The following code prints in sage-9.0 blue lines instead of colored vectors (with tips). In sage-8.9 the presentation is correct:
|
Attachment: 2020-02-15 10_10_25-Support and Testing - CoCalc.png Attachment: 2020-02-15 10_10_37-.png |
comment:4
For what it's worth viewer="tachyon" continues to seem to be okay, and viewer="jmol" (i.e. jsmol) seems to be slightly better (though still weird) on the Sage cell server. See this Sage cell to try out all three. |
comment:5
Could this be a bug in the newest threejs we included (r110)? I'm not suggesting it is, but it would be worth checking out and comparing both versions in all three viewers (or any others I have forgotten existed). |
comment:6
Replying to @kcrisman:
This is not an issue with Three.js itself. Most objects in Sage do not have a standard JSON representation like surfaces. For points, lines, texts and vector fields I had to choose some other attribute to distinguish their types. Mathematical vectors, as opposed to |
comment:7
That makes sense.
When you say, "I had to choose", I assume you mean you implemented some of the code for this - can you point to some tickets or code where you think this might have shown up? Maybe it's just as simple a problem as the move to threejs for plotting? Thanks for any useful pointers. William, the images you posted show which version of Sage was involved, but can you tell us whether you can see which "viewer" was involved? (I can't remember when threejs became a default option for 3d viewing.) |
comment:8
Scratch all that - I have now been able to confirm the problem is threejs, as paulmasson's comment implied. Changing title appropriately. |
comment:9
What I don't understand is that
is in Okay, the real problem is that
If someone can give me a pointer to where |
comment:10
Will be fixed by #29227 |
Dependencies: #29227 |
comment:11
Agreed, this is now a dup. If you agree (as I think you do) then hit the button. |
Reviewer: Paul Masson |
comment:13
Great. Glad someone worked on it too - that is awesome. Thank you for building the infrastructure. |
Changed reviewer from Paul Masson to Paul Masson, Karl-Dieter Crisman |
Depends on #29227
CC: @paulmasson @kcrisman
Component: graphics
Reviewer: Paul Masson, Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/29206
The text was updated successfully, but these errors were encountered: