The peaks I saw in the visit data were caused by R.M. posting links to mma.se on Reddit. In the meantime this earned him/her 4 golden badges. This is almost too easy...
I'll play a bit with it :-) Also, Heike put a nice camera cone there, which might contribute to slowing things down (and I don't need it). Perhaps performance wouldn't be a problem after all.
Under More Information in the help page of ViewMatrix the following entry can be found
With the setting ViewMatrix->Automatic, explicit forms for the matrix m can be found using AbsoluteOptions[g,ViewMatrix].
Trying this with a basic example
gr = Plot3D[Sin[x + y^2], {x, -3, 3}, {y, -2,...
It's funny how the deletion of this question has given is more attention than it would have had if it had been left alone.
@halirutan It should be possible to construct the projection matrices from ViewVector, ViewVertical, and ViewAngle, but I haven't managed to get it working so far.
If memory serves, the documentation never bothered to explain how all those View* options all fit together from the 3D objects to the 2D representation we see...
Do you know how to control the aspect ratio of the viewport for Graphics3D without changing the aspect ratio of the graphics? Say, I want a viewport that is rectangular with aspect ratio 1/2, not a square
It seems that an explicit ViewVector setting gives me a square
@EliLansey I'm very familiar with that condition. Prior to kids, I thought I understood sleep deprivation. After kids, I understand now how wrong I was. Grad school doesn't help, either.
Hi guys, I have a quick question that is probably me not seeing something obvious... I hope you can see it
Why s[[1]] /. s -> {a} warns me that "Part::partd: Part specification s[[1]] is longer than depth of object. >>", and s /. s -> {a} followed by %[[1]] doesn't?
@JM Ah, but you out answer me in terms of volume, consistently.
@agravier At issue is the order of operations. At this stage s[[1]] /. s -> {a}, s has no depth that Part (shorthand: [[1]]) can access, so it throws an warning. But, that is all it is, once the substitution occurs, s[[1]] has meaning.
If you know such an error is going to occur, you can suppress is via Quiet[expr, msg], which in this case would be Quiet[s[[1]] /. s -> {a}, Part::partd].
@JM maybe. It is still a jumble. But, the level of indentation has meaning! :P
Here's a case for its use as the function emits a message and returns $Failed. Since messages can be slow, suppressing it and just testing for $Failed seems like the way to go.
In that case, I don't think you're "breaking" it so much as ignoring the unwanted behavior. In that case, it is like catching a thrown exception and handling it without the user ever being aware.
(Meta: My browser can't seem to be able to stay on this chat, I get "There seems to be a problem connecting to the server. Please check your internet connection and reload this page." every ~10min. Is it normal?)
Ok, I was using substitution rules as an equivalent of "let" in other functional languages, but I was having big problems in recursive functions, with this error message from Part + the funciton not working. Now I've discovered the wonders of Block. Yay. Progress.
@Heike on a different note, you mentioned you write applescript so you'll feel my pain: I have spent almost an hour trying to remember how to add a string to the end of a list
@acl It is also old-fashioned, and primarily it was found in the South/rural areas. You occasionally here it used in old (1950's and 1960's era) TV shows.
transfer some tags from Media Pro to Lightroom (these are media cataloging applications that I use for my photography); media pro has fields for people, lightroom hasn't, so I am writing a script to add keywords with the names (which do get transferred between them)
although I could have done it by hand faster (view all the photos tagged "john", add a keyword "john" to them). I don't have that many different people there...
@Heike right, every time I switch from media pro to lightroom!
hooray!
@Heike well, I have been using media pro and capture one for years, and now am switching to lightroom. I like its interface much better than aperture and better than capture one, the quality is fine, its cataloguing features almost as good as media pro.
all in all, with lightroom I have it all in one place, with no random crashes like media pro, and with a more versatile raw converter (c1 is not so good at higher ISO and I have a fairly old camera--c1 is fantastic at low iso, not so goot at higher sensitivities). and a nice set of controls too
@Heike well, that's one approach. the general idea is simple enough that I doubt you'll have any trouble once you have a think about what is being done
but, I find lightroom's controls really much easier (and actually pleasurable) to use than anything else's, even after years of using capture 1. so it's doing something right
@acl The course is supposed to focus more on artistic aspects of photography but there isn't really a strict schedule and the teacher is willing to discuss any questions that come up including those on postprocessing.
@Heike well, an interesting exercise is to extract the unscaled channels (ie the raw numbers) and attempt to write a simple demosaicing algorithm in mma. it's not so trivial to get good results
but not so hard to get something...
(extracting the channels can be done using dcraw)
although I am not sure this teaches much that's useful for artistic purposes!
(come to think of it, it is not trivial for me, but judging from what I see here, some of us here would probably find it childishly simple)
@acl The only time I had to deal with raw data directly was when I was imaging parasites using a fast speed camera, but that was black and white and the artistic quality of the images was at the bottom of the list.
Have you noticed at wolfram.com/events/technology-conference/2012, that the old MathModelica (if I may say so) has an official new name "Wolfram SystemModeler" (I'm guessing the relation from its name). I'm very disappointed that this is coming as a separate product. Lately, Wolfram "all integrated" strategy has failed me on both the Finance Platform and now on this one...
What do you think? (for those that did not sign a NDA)
@SjoerdCdeVries It doesn't. But if not, why a different name for something that would be a simple (or rather complex) extension of the interface functionality (and new function...). I just hope I'm wrong on my deductions...
I'm still living badly the second Mathematica version that goes with the name of Finance Platform. I can understand the fact that some functionality of the FP has a cost for WR (some sort of DB interface and access service paying). But, for example the Excel link that is "offered" with the FP should already exist on standard Mathematica, for a long time...
Excel is the standard in almost any production company. A strong standard interface with it, would mean a lot.
In this small details, we can see clearly which is the typical use of Mathematica...