Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Eponymous

Pages: [1]
General / Re: Beginner's question: photo vs camera alignment
« on: June 08, 2020, 07:07:51 PM »
Touché! too long story. I do it a lot, sorry.
Just to top it off. I like the indistinct use of several words for the same as a sort of, literary license. Like when you write about a cathedral and try to use other words to avoid repetition: the temple...., the building..., the monument...

I hear you. As a new user though, I was confused.

Feature Requests / Website and tutorial English language improvements
« on: June 07, 2020, 12:01:37 PM »
As an inexperienced user, I’m trying to use the website and various tutorials, which can be super helpful. I notice though that sometimes there are some infelicities in the English used. Is there a good way to give feedback on those, or ask for someone better experienced to clarify what’s being said? Thanks.

General / Re: Beginner's question: photo vs camera alignment
« on: June 07, 2020, 11:14:43 AM »
Thanks for the reply, which I read as a long way to say “yes”.  ;)

I am simply interested in the software’s use of the two terms which I think is confusing. Where’s the best place to put in a feature request?

Hello Eponymous:
Photo and camera can be used to mean the same thing, but  if you want to make a distinction, when it comes to photogrammetry, a photo is a two dimensional thing while a camera means here a photo linked to the lens and camera body together forming a complex thing which is three dimensional, that is called camera for language economy, just for the same reason we say "photo" instead of "photography".
So in the program they use indistinctly the two words because a photo without lens parameters associated is not even something you would be able to use. Just imagine that you remove your lens from your camera and press the trigger button.  The light will hit the sensor and you will get something you can call photo even if it is a blurred likely burnt mess or perhaps an invaluable piece of art that someone could even pay for, but that photo would never be called a camera here.
So "photo" is not enough word while calling "camera" to a photo is like to borrowing the name of the device that produces it. Well it is perhaps something you can dislike metonymy, but what if I remind you that "camera" means actually "room" in latin?

General / Beginner's question: photo vs camera alignment
« on: June 04, 2020, 06:08:10 PM »
Do I understand correctly that the terms "photo alignment" and "camera alignment" mean the same thing?

An example: using the Workflow menu, I align photos. That process shows up in the log with that phrase. Some of my photos are unaligned. These now have "NA" next to them in the workspace pane, which I take to stand for "not aligned". This corresponds to not having a checkmark in the Photos pane. However in the workspace, they are not referred to as "photos", but as "cameras". The alert box that pops up at the end of alignment tells me: "Some photos failed to align. Please resent alignment for incorrectly aligned photos and rerun photo alignment.

In both the workspace and photo pane, there is no option for resetting photo alignment, only camera alignment. I take these to be the same thing. If I do choose that option, the log reports "Camera alignment", as if it were not the same thing as photo alignment.

If these two things are identical, it would be less confusing if the same term were used consistently.

Relatedly, if I run Align Photos from the Workflow menu and don't have "reset current alignment" checked, is that the same as choosing "align selected cameras" from the contextual menu? (Also note that that checkbox doesn't say either "photo" or "camera" alignment, just "alignment".)


Bug Reports / Re: Version 0.9.1 Build 1703 Crashes on Generating Mesh
« on: August 08, 2013, 03:49:24 AM »
Hello Eponymous,

You can refer to memory requirements section on our Wiki pages:

The main questions are:
what is the typical number and resolution of images in your projects?
what reconstruction settings will you be commonly using (geometry quality, object type)?
what is the object or scene type you are planning to reconstruct with PhotoScan?
Having answers for these will help you to estimate the amount of RAM required for your tasks.

Ah, there it is.

I have a few dozen (so, 20-50) 15Mpixel images and am trying to do high resolution, which suggests that I need more than the 8GB of RAM I now have.

Bug Reports / Re: Version 0.9.1 Build 1703 Crashes on Generating Mesh
« on: August 07, 2013, 04:01:50 PM »
Thanks, Alexy. Is there a good way to estimate the needed amount of RAM, so I can see whether it's worthwhile to upgrade?

Bug Reports / Re: Version 0.9.1 Build 1703 Crashes on Generating Mesh
« on: August 07, 2013, 12:10:39 AM »
I'm having a similar problem with high "Build Geometry" and the 1714 build on OS X 10.7.5. Hangs at 10% of "generating mesh" though the cpu usage is low. I have to force-quit it, since it ignores the click on "cancel" even though the button responds to the mouse action. "Minimize" works however.

RAM is also maxed out, and PS seems to be using about 11GB of disk space, which is freed up upon quitting. Free space is 8GB when it gets stuck.

I'll try overnight tonight (it's a 9-hr run) and generate a log file if I can.

(I notice that it seems like the problem reported on this thread: Was this just due to low RAM and very slow swapping? I'll try to create more drive space before running it tonight.)

Feature Requests / Re: Cosmetics..
« on: December 03, 2012, 05:53:45 AM »
And maybe some buttons or commands to jump to fixed views like "all points visible"?

Pages: [1]