3D camera constraints

Hi all,
A bit of maths...
I have a virtual camera (due to portability of code etc. I cannot use the standard 3D transformations from Flash...) which moves through a space. Size (and position) of the objects are calculated by the pretty standard:
scale = focalLength / ( focalLength + zpos )
(larded with some code to show all at scale == 1 when camera.z == 0)
The space is 'sealed' off by a background image of which the sides should not be visible, therefore the camera has constraints set; no moving past certain x- and y-values so the view frustum does not exceed the edges of the image.
Now the problem is that an object pretty close to the edge of the cube more or less defined by the background image is visible when the camera is at z == 0. However, when the camera moves forward, the view frustum kind of moves away from the edge of the box therefore making it impossible to see the edges of the box or anything present there when constraints are maintained. (see image below).
Does anyone have a smart, and preferably not to crazy on the maths part, solution for this at hand? (can't be the first I suppose )
Thanks in advance,
Manno

The 3D camera tracker is unpredictable. It tends to work best if the video is fairly sharp with clearly defined areas which represent movement of the environment. It seems to need this to calculate parallax and the camera field of view. If you have objects or people moving in the footage, it can through the camera tracker off. Experiment with the various settings on a small section of the video clip. Once you have settings that work, expand the time range you want to track and re-try it.
I have gotten very mixed results, and find that its simple controls and interface may limit some of its power. When it works, it usually works very well. When it doesn't, the results are useless. Keep trying and good luck.

Similar Messages

Capture Web Cam image in APEX and Upload into the Database

Overview
By using a flash object, you should be able to interface with a usb web cam connected to the client machine. Their are a couple of open source ones that I know about, but the one I chose to go with is by Taboca Labs and is called CamCanvas. This is released under the MIT license, and it is at version 0.2, so not very mature - but in saying that it seems to do the trick. The next part is to upload a snapshot into the database - in this particular implementation, it is achieved by taking a snapshot, and putting that data into the canvas object. This is a new HTML5 element, so I am not certain what the IE support would be like. Once you have the image into the canvas, you can then use the provided function convertToDataURL() to convert the image into a Base64 encoded string, which you can then use to convert into to a BLOB. There is however one problem with the Base64 string - APEX has a limitation of 32k for and item value, so can't be submitted by normal means, and a workaround (AJAX) has to be implemented.
Part 1. Capturing the Image from the Flash Object into the Canvas element
Set up the Page
Required Files
Download the tarball of the webcam library from: https://github.com/taboca/CamCanvas-API-/tarball/master
Upload the necessary components to your application. (The flash swf file can be got from one of the samples in the Samples folder. In the root of the tarball, there is actually a swf file, but this seems to be a different file than of what is in the samples - so I just stick with the one from the samples)
Page Body
Create a HTML region, and add the following:
    <div class="container">
     <object id="iembedflash" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000"
codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,0,0" width="320" height="240">
          <param name="movie" value="#APP_IMAGES#camcanvas.swf" />
          <param name="quality" value="high" />
          <param name="allowScriptAccess" value="always" />
          <embed allowScriptAccess="always" id="embedflash" src="#APP_IMAGES#camcanvas.swf" quality="high" width="320" height="240"
type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" mayscript="true" />
    </object>
    </div>
<p><a href="javascript:captureToCanvas()">Capture</a></p>
<canvas style="border:1px solid yellow" id="canvas" width="320" height="240"></canvas>That will create the webcam container, and an empty canvas element for the captured image to go into.
Also, have a hidden unprotected page item to store the Base64 code into - I called mine P2_IMAGE_BASE64
HTML Header and Body Attribute
Add the Page HTML Body Attribute as:
onload="init(320,240)"
JavaScript
Add the following in the Function and Global Variable Declarations for the page (mostly taken out of the samples provided)
//Camera relations functions
var gCtx = null;
var gCanvas = null;
var imageData = null;
var ii=0;
var jj=0;
var c=0;
function init(ww,hh){
     gCanvas = document.getElementById("canvas");
     var w = ww;
     var h = hh;
     gCanvas.style.width = w + "px";
     gCanvas.style.height = h + "px";
     gCanvas.width = w;
     gCanvas.height = h;
     gCtx = gCanvas.getContext("2d");
     gCtx.clearRect(0, 0, w, h);
     imageData = gCtx.getImageData( 0,0,320,240);
function passLine(stringPixels) {
     //a = (intVal >> 24) & 0xff;
     var coll = stringPixels.split("-");
     for(var i=0;i<320;i++) {
          var intVal = parseInt(coll);
          r = (intVal >> 16) & 0xff;
          g = (intVal >> 8) & 0xff;
          b = (intVal ) & 0xff;
          imageData.data[c+0]=r;
          imageData.data[c+1]=g;
          imageData.data[c+2]=b;
          imageData.data[c+3]=255;
          c+=4;
     if(c>=320*240*4) {
          c=0;
          gCtx.putImageData(imageData, 0,0);
function captureToCanvas() {
     flash = document.getElementById("embedflash");
     flash.ccCapture();
     var canvEle = document.getElementById('canvas');
     $s('P2_IMAGE_BASE64', canvEle.toDataURL());//Assumes hidden item name is P2_IMAGE_BASE64
     clob_Submit();//this is a part of part (AJAX submit value to a collection) two
}In the footer region of the page (which is just a loading image to show whilst the data is being submitted to the collection [hidden by default]) :<img src="#IMAGE_PREFIX#processing3.gif" id="AjaxLoading"
style="display:none;position:absolute;left:45%;top:45%;padding:10px;border:2px solid black;background:#FFF;" />If you give it a quick test, you should be able to see the webcam feed and capture it into the canvas element by clicking the capture link, in between the two elements - it might through a JS error since the clob_Submit() function does not exist yet.
*Part 2. Upload the image into the Database*
As mentioned in the overview, the main limitation is that APEX can't submit values larger than 32k, which I hope the APEX development team will be fixing this limitation in a future release, the workaround isn't really good from a maintainability perspective.
In the sample applications, there is one that demonstrates saving values to the database that are over 32k, which uses an AJAX technique: see http://www.oracle.com/technetwork/developer-tools/apex/application-express/packaged-apps-090453.html#LARGE.
*Required Files*
From the sample application, there is a script you need to upload, and reference in your page. So you can either install the sample application I linked to, or grab the script from the demonstration I have provided - its called apex_save_large.js.
*Create a New Page*
Create a page to Post the large value to (I created mine as 1000), and create the following process, with the condition that Request = SAVE. (All this is in the sample application for saving large values).declare
     l_code clob := empty_clob;
begin
     dbms_lob.createtemporary( l_code, false, dbms_lob.SESSION );
     for i in 1..wwv_flow.g_f01.count loop
          dbms_lob.writeappend(l_code,length(wwv_flow.g_f01(i)),wwv_flow.g_f01(i));
     end loop;
     apex_collection.create_or_truncate_collection(p_collection_name => wc_pkg_globals.g_base64_collection);
     apex_collection.add_member(p_collection_name => wc_pkg_globals.g_base64_collection,p_clob001 => l_code);
     htmldb_application.g_unrecoverable_error := TRUE;
end;I also created a package for storing the collection name, which is referred to in the process, for the collection name:create or replace
package
wc_pkg_globals
as
g_base64_collection constant varchar2(40) := 'BASE64_IMAGE';
end wc_pkg_globals;That is all that needs to be done for page 1000. You don't use this for anything else, *so go back to edit the camera page*.
*Modify the Function and Global Variable Declarations* (to be able to submit large values.)
The below again assumes the item that you want to submit has an item name of 'P2_IMAGE_BASE64', the condition of the process on the POST page is request = SAVE, and the post page is page 1000. This has been taken srtaight from the sample application for saving large values.//32K Limit workaround functions
function clob_Submit(){
          $x_Show('AjaxLoading')
          $a_PostClob('P2_IMAGE_BASE64','SAVE','1000',clob_SubmitReturn);
function clob_SubmitReturn(){
          if(p.readyState == 4){
                         $x_Hide('AjaxLoading');
                         $x('P2_IMAGE_BASE64').value = '';
          }else{return false;}
function doSubmit(r){
$x('P2_IMAGE_BASE64').value = ''
     flowSelectAll();
     document.wwv_flow.p_request.value = r;
     document.wwv_flow.submit();
}Also, reference the script that the above code makes use of, in the page header<script type="text/javascript" src="#WORKSPACE_IMAGES#apex_save_large.js"></script>Assuming the script is located in workspace images, and not associated to a specific app. Other wise reference #APP_IMAGES#
*Set up the table to store the images*CREATE TABLE "WC_SNAPSHOT"
"WC_SNAPSHOT_ID" NUMBER NOT NULL ENABLE,
"BINARY" BLOB,
CONSTRAINT "WC_SNAPSHOT_PK" PRIMARY KEY ("WC_SNAPSHOT_ID")
create sequence seq_wc_snapshot start with 1 increment by 1;
CREATE OR REPLACE TRIGGER "BI_WC_SNAPSHOT" BEFORE
INSERT ON WC_SNAPSHOT FOR EACH ROW BEGIN
SELECT seq_wc_snapshot.nextval INTO :NEW.wc_snapshot_id FROM dual;
END;
Then finally, create a page process to save the image:declare
v_image_input CLOB;
v_image_output BLOB;
v_buffer NUMBER := 64;
v_start_index NUMBER := 1;
v_raw_temp raw(64);
begin
--discard the bit of the string we dont need
select substr(clob001, instr(clob001, ',')+1, length(clob001)) into v_image_input
from apex_collections
where collection_name = wc_pkg_globals.g_base64_collection;
dbms_lob.createtemporary(v_image_output, true);
for i in 1..ceil(dbms_lob.getlength(v_image_input)/v_buffer) loop
v_raw_temp := utl_encode.base64_decode(utl_raw.cast_to_raw(dbms_lob.substr(v_image_input, v_buffer, v_start_index)));
dbms_lob.writeappend(v_image_output, utl_raw.length(v_raw_temp),v_raw_temp);
v_start_index := v_start_index + v_buffer;
end loop;
insert into WC_SNAPSHOT (binary) values (v_image_output); commit;
end;Create a save button - add some sort of validation to make sure the hidden item has a value (i.e. image has been captured). Make the above conditional for request = button name so it only runs when you click Save (you probably want to disable this button until the data has been completely submitted to the collection - I haven't done this in the demonstration).
Voila, you should have now be able to capture the image from a webcam. Take a look at the samples from the CamCanvas API for extra effects if you wanted to do something special.
And of course, all the above assumed you want a resolution of 320 x 240 for the image.
Disclaimer: At time of writing, this worked with a logitech something or rather webcam, and is completely untested on IE.
Check out a demo: http://apex.oracle.com/pls/apex/f?p=trents_demos:webcam_i (my image is a bit blocky, but i think its just my webcam. I've seen others that are much more crisp using this) Also, just be sure to wait for the progress bar to dissappear before clicking Save.
Feedback welcomed.

Hmm, maybe for some reason you aren't getting the base64 version of the saved image? Is the collection getting the full base64 string? Seems like its not getting any if its no data found.
The javascript console is your friend.
Also, in the example i used an extra page, from what one of the examples on apex packages apps had. But since then, I found this post by Carl: http://carlback.blogspot.com/2008/04/new-stuff-4-over-head-with-clob.html - I would use this technique for submitting the clob, over what I have done - as its less hacky. Just sayin.

How to apply the constraint ONLY to new rows

Hi, Gurus:
   I have one question as follows:
   We need to migrate a legacy system to a new production server. I am required to add two columns to every table in order to record who updates the row most recently through triggers, and I should apply not null constraint to the columns . However, since legacy system already has data for every table, and old data does not have value for the 2 new columns. If we apply the constraint, all of existing rows will raise exception. I wonder if there is possibility to apply the constraint ONLY to new rows to come in future.
Thanks.
Sam

   We need to migrate a legacy system to a new production server. I am required to add two columns to every table in order to record who updates the row most recently through triggers, and I should apply not null constraint to the columns .
The best suggestion I can give you is that you make sure management documents the name of the person that came up with that hair-brained requirement so they can be sufficiently punished in the future for the tremendous waste of human and database resources they caused for which they got virtually NOTHING in return.
I have seen many systems over the past 25+years that have added columns such as those: CREATED_DATE, CREATED_BY, MODIFIED_DATE, MODIFIED_BY.
I have yet to see even ONE system where that information is actually useful for any real purpose. Many systems have application/schema users and those users can modify the data. Also, any DBA can modify the data and many of them can connect as the schema owner to do that.
Many tables also get updated by other applications or bulk load processes and those processes use generic connections that can NOT be tied back to any particular system.
The net result is that those columns will be populated by user names that are utterly useless for any auditing purposes.
If a user is allowed to modify a table they are allowed to modify a table. If you want to track that you should implement a proper security strategy using Oracle's AUDIT functionality.
Cluttering up ALL, or even many, of your tables with such columns is a TERRIBLE idea. Worse is adding triggers that server no other purpose but capture useless infomation but, because they are PL/SQL cause performance impacts just aggravates the total impact.
It is certainly appropriate to be concerned about the security and auditability of your important data. But adding columns and triggers such as those proposed is NOT the proper solution to achieve that security.
Before your organization makes such an idiotic decision you should propose that the same steps be taken before adding that functionality that you should take before the addition of ANY MAJOR structural or application changes:
1. document the actual requirement
2. document and justify the business reasons for that requirement
3. perform testing that shows the impact of that requirement on the production system
4. determine the resource cost (people, storage, etc) of implementing that requirement
5. demonstrate how that information will actually be used EFFECTIVELY for some business purpose
As regards items #1 and #2 above the requirement should be stated in terms of the PROBLEM to be solved, not some preconceived notion of the solution that should be used.
Your org should also talk to other orgs or other depts in your same org that have used your proposed solution and find out how useful it has been for them. If you do this research you will likely find that it hasn't met their needs at all.
And in your own org there are likely some applications with tables that already have such columns. Has anyone there EVER used those columns and found them invaluable for identifying and resolving any actual problem?
If you can't use them and their data for some important process why add them to begin with?
IMHO it is a total waste of time and resources to add such columns to ALL of your tables. Any such approach to auditing or security should, at most, be limited to those tables with key data that needs to be protected and only then when you cannot implement the proper 'best practices' auditing.
A migration is difficult enough without adding useless additional requirements like those. You have FAR more important things you can do with the resources you have available:
1. Capture ALL DDL for the existing system into a version control system
2. Train your developers on using the version control system
3. Determining the proper configuration of the new server and system. It is almost a CERTAINTY that settings will get changed and performance will suffer even though you don't think you have changed anything at all.
4. Validating that the data has been migrated successfully. That can involve extensive querying and comparison to make sure data has not been altered during the migration. The process of validating a SINGLE TABLE is more difficult if the table structures are not the same. And they won't be if you add two columns to every table; every single query you do will have to specify the columns by name in order to EXCLUDE your two new columns.
5. Validating the performance of the app on the new system. There WILL BE problems where things don't work like they used to. You need to find those problems and fix them
6. Capturing the proper statistics after the data has been migrated and all of the indexes have been rebuilt.
7. Capturing the new execution plans to use a a baseline for when things go wrong in the future.
If it is worth doing it is worth doing right.

Uniques constraint violation error while executing statspack.snap

Hi,
I have configured a job to run the statspack snap at a interval of 20 min from 6:00 PM to 3:00 AM . Do perform this task , I have crontab 2 scripts : one to execute the job at 6 PM and another to break the job at 3 AM. My Oracle version is 9.2.0.7 and OS env is AIX 5.3
My execute scripts look like:
sqlplus perfstat/perfstat <<EOF
exec dbms_job.broken(341,FALSE);
exec dbms_job.run(341);
The problem is , that the job work fine for weekdays but on weekend get aborted with the error :
ORA-12012: error on auto execute of job 341
ORA-00001: unique constraint (PERFSTAT.STATS$SQL_SUMMARY_PK) violated
ORA-06512: at "PERFSTAT.STATSPACK", line 1361
ORA-06512: at "PERFSTAT.STATSPACK", line 2471
ORA-06512: at "PERFSTAT.STATSPACK", line 91
ORA-06512: at line 1
After looking on to metalink , I came to know that this is one listed bug 2784796 which was fixed in 10g.
My question is , why there is no issue on weekdays using the same script. There is no activity on the db on weekend and online backup start quite late at night.
Thanks
Anky

The reasons for hitting this bug are explained in Metalink, "...cursors with same sql text (at least 31 first characters), same hash_value but a different parent cursor...", you can also find the workaround in Note:393300.1.
Enrique

Use Camera RAW with Sony Nex-3

Hey Guys!
I want to get out more details from my photos.
Im using Adobe Photoshop CS5
Sony NEX-3 Compact Camera (listed in the camera raw compatibility list)
First i changed the cameras picture format from jpg to RAW & made some photos.
At home i tried to open the files with Camera Raw. Doesnt work. The sony camera saved the pictures as an ARW File.
So i downloaded Adobe DNG Converter. I converted the ARW into a RAW file and opened it with camera raw.
So far so good! I opended the RAW picture with Photoshop. Just for testing with 8 & also 16 bit. Does my camera support 16bit?
I compared the RAW File with the new created jpg.
Normaly the quality of the raw file should be much better than the compressed jpg i think.
I took a look at some other jpg pictures (i shot them in JPG Mode) & compared them with the RAW Images (RAW Mode).
I saw absolutely no difference between RAW & JPG.
I also tried a exact tonal value correction at both images.
Same with other picture corrections. Details, Noise, Sharpness.... same.
With the Sony NEX-3 there also was a RAW Program included which opens the ARW Files.
I cant see some differences between RAW & jpg here too.
What I am doing wrong?
I have to say that i am an camera raw beginner. I tried this for the first time. I thought this would be easier!
At the screenshot below you see a JPG picture on the left & a 16bit DNG on the right.
I found no differences!
I would be very happy about your help and some good advices.
Best regards Andi

Andi265 wrote:
Basicly i understand how RAW works. But im still wondering why i cant see just only a very little difference to my jpg Images.
The image of the Mountain Railway Station i postet has a lot of dark shadow areas & details.
I´m also wondering why these chromatic aberrations are shown in the RAW file? I thought its only in the jpg images because of the compression.
Your raw file may be 12 or 14 bit, and have no output colour space - it is only limited by its physical characteristics and analogue-to-digital converters. You should set Camera Raw for the biggest workspace necessary, which in my case is 16 bit AdobeRGB. Others work in ProPhotoRGB—it's a personal choice. This has the effect of constraining the raw data, and you will learn to use the sliders to work within those constraints.
Using normal processing settings there will only be subtle differences between the conversion preview and the camera JPEG. The tonal response will be slightly different, seeming slightly lighter or darker, and the colours' hue/saturation will be slightly different too. Also, depending on the camera, automatic distortion/vignette/aberration correction will be missing. This is all to be expected, and your expectations have been misplaced.
However, this is only a starting point. Whilst JPEG shooters can go on to process their images, the resulting quality will be inferior; JPEG is a finished image format. Raw shooters have much more to play with, and can manipulate the conversion's parameters to boost shadows, recover highlights, adjust mean exposure, increase/reduce/localise sharpening and noise control, apply processing gradients and masks, apply local contrast and selective saturation boosts, and correct your camera's colour response, as well as apply lens defect corrections—all before the conversion to JPEG.
So, you won't start to see the difference until you start to push these adjustments. You have been given a second (and a third and a fourth...) chance to create your JPEG using your own set of picture parameters, and the ability to change these parameters for each photo after taking the photo.
In your photo above, you can bring out detail in the shadows by boosting Fill and Blacks. As you shot in Raw, you will have a good amount of tonal resolution recorded in the shadows (assuming you didn't underexpose in the first place), which would be absent from a JPEG. You also have the ability to change the sharpening to suit the image, and even apply local sharpening where it's needed most (and less where it's not needed).
You also have the ability to modify Camera Raw's default settings how you like it. You can enable automatic lens defect corrections (like chromatic aberration—make sure you're on ACR 6.7). You can change the default camera profile (which dictates how tone, hue and saturation is translated) to a preset, or make your own using a calibrator. Do this and your starting point will be how you want it, not how Sony wants it.
I could go on, but I think you have probably heard much of this before. The main point I'm making is that you shouldn't expect to see a big difference straight away, but the possibilities you have created are much greater.
Message was edited by: Yammer P

Why Camera Raw Needs Larger Size Choices

The upsampling provided in Camera Raw as part of the conversion process is excellent. I know of no better way to extract the maximum possible detail from a raw image than to convert to an upsampled resolution.
Trouble is, the biggest value one can select from the list is 6144 x 4096 pixels.
Some cameras, e.g., the Nikon D800, already deliver images with more pixels that this, so there are no upsampled resolutions to choose from in the Workflow Options dialog. There need to be!
There is a way to "trick" Camera Raw into providing a larger image - one can set a custom crop, then drag the crop tool around the entire image, then finish the conversion.
Just to illustrate the utility in doing this, I used the "trick" to get a 9000 x 6000 pixel conversion from a Nikon D800 image, which can be found here:
http://movies.dpreview.com.s3.amazonaws.com/nikon_d800/DSC_0241.NEF.zip
Once I opened this image at 54 megapixels (up from the camera's native 36.2 MP) I sharpened it. You can see how well that came out here (11 megabyte JPEG file):
http://Noel.ProDigitalSoftware.com/ForumPosts/DSC_0241_Upsampled_and_Sharpened.jpg
I've made this request before, and it was ignored. Here's hoping the Camera Raw team will reconsider offering some upsampled sizes based on the native size (e.g., 125%, 150%, etc.). No matter how many megapixels you've got, more is better.
-Noel

Jeff Schewe wrote:
You need to make a use case argument that carries enough weight for the engineers to go into the sizing options and do additional work–which appearently you've not successfully done yet.
if enough users ask for it
You're advocating design by public popularity contest over technical leadership? Really? LOL, I mean no disrespect but that sounds like something out of Dilbert's world.
Someone on the Camera Raw design staff has ALREADY made the case for providing both up- and down-sampling options for all the cameras available at the time, or those options would not have been implemented in the first place! That they were implemented as fixed values rather than a formula based on the native resolution may have been because of constraints that are no longer there now (based on our current ability to arbitrarily choose sizes via the Crop trick).
RASouthworth wrote:
I've always read (and practiced) remaining at native camera res until edit completion, and then going thru an upsampling and sharpening phase for print. Why run it up early?
Ah, so now it becomes clear we're discussing something that goes against long-standing beliefs you have been running on.
1. No one is trying to force you to abandon anything you like to do and which nets you good results already.
2. No one is proposing anything radical here, but do always try to keep an open mind, because there might still be people in the world who are just as smart as those who have sold you books in the past.
-Noel

Best camera for low light and sports

have the sx200is
looking for a newer camera for sports and low light shots

The challenge with sports is that you are REALLY pushing the camera gear to it's limits. Fast action requires fast shutter speeds. But fast shutter speeds demand a lot of light and only outdoor games played during the daytime have that. Indoor games or games played under field lighting at night generally do not have the kind of lighting needed to shoot with fast shutter speeds -- not the kind of shutter speeds needed to freeze action. So this ends up demanding a camera with excellent ISO performance and lenses with very low focal ratios so they can collect a LOT more light when the shutter is open. This gear is expensive.
You will want to consider a reasonable budget depending on what you can afford and the needs of the specific sports.
Are these indoor or outdoor sports? If outdoors, are these played during the day or are they night games?
The "best" camera for sports and low light is the EOS-1D X. It has phenominal low-light performance, has an amazing focus system, and can shoot at 12 frames per second. But it's about $6800 for the "body only" and then you still need lenses. I'm guessing this is probably not what you had in mind. But if money were not a constraint... this would be the one to go for.
The 5D III is another amazing camera for low light performance and and also has an amazing focusing system (largely the same as the 1D X) can shoot at 6 frames per second, and only costs $3500... again, that's the "body only". Still probably not what you had in mind.
The 70D has an extremely good focus system (though not as good as the 5D III and 1D X), not quite as good as low light (but pretty good and much better than a point & shoot camera) and shoots at 7 frames per second (1 fps faster than 5D III) and it only costs $1200 for the body only.
The T5i will be noticeably less expensive than the 70D... a good (but not extremely good) focusing system and 5 frames per second, but the body and 1 kit lens combined is about $850 but that wont a lens suitable for use shooting sports so you'll still need to invest in more appropriate lenses.
When shooting action photography in low light, what you _really_ want is a lens that can collect a lot more light than the average lens for that very brief moment when the shutter is open. Such a lens can allow you to use a faster shutter speed to help freeze those action shots. But *which* lens you use depends on the sport.
For low-light sports, these would ideally be f/2.8 zoom lenses... but f/2.8 zoom lenses are not cheap. Canon's EF 70-200 f/2.8L IS USM (ideal for most indoor sports and outdoor sports IF the action is happening close to you) is about $2500. Sigma's lens is about half that price. But if you're covering action on a large athletic field and the players are far away, they'll still be small. Sigma makes a 120-300mm f/2.8 zoom for sports... for the low low price of only $3600.
Scott Kelby does a video to talk about sports photography and he discusses the equipment used and why... and basically says if you want the gear for shooting sports, you basically need a suitcase full of money.
Tim Campbell
5D II, 5D III, 60Da

One problem with constraints missing in source and target database....

DB Gurus,
In my database I am going to export and import data using datapump but dont specify CONTENT clause.
so when I start working on my application, I came to know there are some constraints are missing. now how to check what are the constraints are missing from Source database and how to create those missing constraints on Target database?
Suggest me if you have any idea.

Create a database link between source and target schema.
Use all_/dba_/_user_constraints to generate the difference using MINUS operator.
something like this:
select owner,constraint_name,constraint_type from dba_constraints@source
MINUS
select owner,constraint_name,constraint_type from dba_constraints

Primary Key Constraint missing in Oracle Standard Tables OE_ORDER_HEADERS_ALL

Dear Legends,
In our Production and Test Environment R12.1.3 HP-UX 64bit While checking some of the constraints and doing for an ALTER Table add foreign key we came to know that the HEADER_ID primary constraint(OE_ORDER_HEADERS_ALL_PK) is missing for the table OE_ORDER_HEADERS_ALL. May I know the ways that I can check how and when this change could be happened? and How to prevent this in future?
Thanks,
Karthik

Please log a SR with Oracle support since this is concerning your production instance.
http://etrm.oracle.com/pls/et1211d9/etrm_pnav.show_object?c_name=OE_ORDER_HEADERS_ALL&c_owner=ONT&c_type=TABLE
May I know the ways that I can check how and when this change could be happened?
If audit is enabled you can find out, otherwise it may not be easy to tell how/when (search the forum for auditing docs) -- Ask Oracle support for their feedback on this as well.
and How to prevent this in future?
- Establish auditing options (you would also need to consider the impact on the performance then)
- Access to the database should be limited to the DBAs only.
- If you don't trust your DBA, fire him/her
Thanks,
Hussein

Jpeg camera setting for Lightroom inport

Hi, I have a Canon s3is that I use to shoot maybe 1,000 pictures a week. I have been trying out the Lightroom demo and really love the way it help me process all the pictures. Most of the pictures are used to document processes, so gallery level images are not required. But for about 5% of the pictures I need to get the best possible resulting image within the constraints of the capabilities of the s3is. Ideally I would like the camera to support a raw format which would give me the most flexibility to get those perfect final images in lightroom, but the s3is only supports jpeg image output. Are there optimum camera setting for minimizing the processing the camera will do and then do any processing in lightroom. Or is it better to just let camera try and optimize the image and then do any remaining work in lightroom.
Getting a new camera is not an option at this time.
Thanks in advance for any help.
Jay

You have two choices.
I have an S3 and have come up with the settings I feel are best for post-processing. They are:
Contrast -2
Sharpness -2
Saturation -1
Green -1
Of course, always shoot at maximum resolution.
The other option is to get the CHDK hack for the S3, which gives it RAW mode. You can use a DNG converter to convert the resulting images to a Lightroom-readable format. http://chdk.wikia.com/wiki/FAQ

Please Help - Avoid default name when creating constraints

Here I am creating two very simple tables:
create table supplier
     id number not null,
     constraint pk_supplier primary key (id)
create table product
id number not null,
supplier_id number not null,
constraint pk_product primary key (id),
constraint fk_product_supplier_id
foreign key (supplier_id) references supplier(id)
After done while I choose to view table constraint information by using:
select table_name, constraint_name
from user_cons_columns
where lower(table_name) = 'product';
I get result:
TABLE_NAME                     CONSTRAINT_NAME
PRODUCT                        SYS_C005441
PRODUCT                        SYS_C005442
PRODUCT                        PK_PRODUCT
PRODUCT                        FK_PRODUCT_SUPPLIER_ID
What is the "SYS_C005441" and "SYS_C005442" for? Can I avoid creating them?
Thanks

Justin Cave wrote:
Are you suggest not explicitly naming all your constraints? Or just the NOT NULL ones?No, not at all. Did not even thought that far when I responded. Bit of foot in mouth as I only thought of not null constraints. Blame it on a lack of coffee. :-)
I usually name primary & foreign key and check constraints. But not null constraints - too much of an effort to name them IMO.
But you do raise an interesting topic. Why bother naming some constraints (e.g. PK and FK) and not others (e.g. not null)? So playing devil's advocate, why should we be naming constraints at all?
It sounds like you're suggesting that all constraints should get system default names. Well, one can argue that the same effort of naming other constraints is not worth it - why have null constraints as the exception to implicit naming? I would think that the issue I raised also applies to all constraints.
You have multiple foreign key constraints for INVOICE_ID - how do you name these? I would like both the table and column names as this will provide the meaning needed when seeing the constraint being violated. But with 30 chars only, that is a problem. So invariable one needs to start to abbreviate table and column names in order to make it meaningful constraint name. Been there many times - disliked the constraint name I came up with every time, as it was a compromise and not the actual naming format I would have preferred.
If that's what you're suggesting, doesn't that create problems for you when different environments have different constraint names? I know personally that I'd much rather have named constraints so that when there are constraint violation errors in production, I can start troubleshooting the problem in my local environment without first determining how to map the production constraint name to my local database's constraint name. Understand your point - and yes, it can be an issue. But by the same token, why should an application user ever see a default Oracle exception? With the exception of system-type exceptions (e.g. no more tablespace space, eof on communcation channel), all other exceptions should be custom application exceptions.
Showing for example a "+ORA-00001: unique constraint (xxx.xxxxx) violated+" is wrong IMO. The app code should trap that exception and raise a meaningful and unique application exception for that. The user seeing anything other than a custom app exception, should itself be an exception.
And I'd much rather be able to put the constraint name in a script that is to be promoted through the environments rather than coming up with a process that uses dynamic SQL to figure out the name of the constraint I want to do something to. Well, I would not rely on a constraint name itself to determine what it is. Just because it says fk_invoiceid_invoices does not mean that is is a foreign key on column invoice_id and references the invoices table. The safe/proper thing to do would be to query the data dictionary and confirm just what that constraint is.
I suppose if you know that all the lower environments are very recent clones of production rather than running all the scripts in source control that these problems may not be particularly large. But I'm curious if you have some better approach to handling them (or if I'm completely misinterpreting what you're suggesting).Not sure if you recall some feature discussion with Tom and others (was on asktom?) when someone came up with this core issue and suggested it be addressed by allowing one to define an exception message with the definition of the constraint. Cannot recall the exact syntax proposed, but I do remember thinking that it was not a shabby idea - as this solves the problem of having to invent a meaningful name using 30 chars only. And it also removes the need for trapping that constraint violation in all app code that may cause the exception and raising a custom and meaningful app exception instead. Not too mention that plain and direct SQL access will show the same exception message.
Perhaps in Oracle 12c? I assume the c as it seems that The Next Big Thing is cloud computing and surely Oracle 12 will somehow try to exploit that buzzword - as it has with i (Internet) and g (Grid) versions. ;-)

FK constraint violations

Hi,
I'm experiencing FK constraint violations in spite of having set
kodo.jdbc.ForeignKeyConstraints:true.
I've got a table that stores queued elements like this:
TABLE QUEUED_ELEMENTS (
ID NUMBER,
NAME VARCHAR2,
NEXT_ELEMENT_ID NUMBER
There is a FK defined:
FOREIGN KEY (NEXT_ELEMENT_ID) REFERENCES QUEUED_ELEMENTS(ID).
The reflexive relation of the JDO class is mapped as one-one relation.
Deleting queued elements leads quite consistently to a FK constraint
violation.
I investigated kodo bug reports and came across bug #900. Does bug #900 also
explain FK constraint violations in this context? When will this bug be
fixed? If this scenario is supposed to work, do you need a test case?
Thanks,
Florian

Deleting queued elements leads quite consistently to a FK constraint
violation.
I investigated kodo bug reports and came across bug #900. Does bug #900 also
explain FK constraint violations in this context?
Bug 900 would not apply in this case. Everything should work fine with
a reflexive relation. One thing to watch out for is to make sure you do
not null the relation when deleting instances. If you null the
relation, Kodo can't "see" the dependency on commit, and so won't order
the SQL appropriately. If you are not nulling the relation, then yes,
we'd need a test case. Please send it to [email protected]

Using Constraints on my optimization problem (currently implemented in Unconstrained Nonlinear Opt.VI)

I have an function f(x) that I minimize to find parameters for an algorithm. The algorithm consists of a coordinate transformation matrix. The transformation matrix parameters are currently found using the Unconstrained Optimization VI (simplex). I have had quite a bit of success using this VI and defining my algorithm as an objective function. I previously used Excel Solver for this application. The data set changes over time and certain parameters are tracked.
Whenever I perform an optimization, I move the minimum parameters found to the initial guess parameters. I am finding that my initial guess parameters will remain stable for a while but at times will guess incorrectly. This can happen if I feed the algorithm bad data. It is difficult to determine that the data is bad initially, but it causes the minimization to trail off in some crazy direction that is inconsistent with the real world. This happens after repetitive minimizations and is a result of using my found results for the next iteration. However, in an ideal world, my last found results would be the best initial guess for the next optimization I perform.
One major improvement would be to constrain my initial guess parameters. In particular, I would like to constrain the parameters I use in finding the transformation matrix (in my objective function) with lower and upper limits: 9 < R < 12, for example. Can anyone with experience using the optimization VIs, knowing the information above, help point me in the right direction? I came across the Constrained Nonlinear Optimization VI but it appears to work much different than the Simplex method; so I am not sure if this would work. I will try this next. Any thoughts?
Chris Walker
Certified Labview Developer

I tried using the Constrained Nonlinear Optimization VI. I first tried it without any constraints (min or max constraints) on my parameters and it appeared to work. I could change the initial guess parameters and they would eventually end up the same minimization each time (with the same set of data). Once I add the parameter constraints, however, the VI freezes on the first iteration and I have to abort. I am not sure why and I do not get any errors.
After some testing, it appears that the cno_isisubopt.vi subvi inside the Constrained Nonlinear Optmiziation VI is locking up. The code is attached. If I had to guess, this probably has to do with the input L advancing to Infinity and never allowing the while loop to stop. I am not sure what the internal workings of this VI are so this appears rather difficult to debug!
This is an error that is not tracked or handled by the Constrained Nonlinear Opt Labview VI; thus freezing my program.
Chris Walker
Certified Labview Developer
Attachments:
4-4-2012 9-36-53 PM.jpg ‏158 KB

Dropping constraints

Hi all,
I have to insert schema A into schema B.I dropped the constraints from schema A.I checked from user_constraints,user_cons_columns and it returned zero rows.
But when try to insert schema A into B,it fails for some tables throwing errors like unique constraint violated,etc.
Since i have dropped the constraints then how come it is throwing error.
The insert statement I use inside the loop is:
insert into schema b select * from schema a;

I think you are inserting data using insert statement and through exp/imp, so from where constarints=n and indexes=N came?
Please use below scripts to disable and enable constraints on Schema B and try inserting data:
---- disable constrains ----------
set feedback off
set verify off
set echo off
prompt Finding constraints to disable...
set termout off
set pages 80
set heading off
set linesize 120
spool tmp_disable.sql
select 'spool igen_disable.log;' from dual;
select 'ALTER TABLE '||substr(c.table_name,1,35)||
' DISABLE CONSTRAINT '||constraint_name||' ;'
from user_constraints c, user_tables u
where c.table_name = u.table_name;
select 'exit;' from dual;
set termout on
prompt Disabling constraints now...
set termout off
@tmp_disable.sql;
exit
---- Enable constraints after loading data -----------
set feedback off
set verify off
set wrap off
set echo off
prompt Finding constraints to enable...
set termout off
set lines 120
set heading off
spool tmp_enable.sql
select 'spool igen_enable.log;' from dual;
select 'ALTER TABLE '||substr(c.table_name,1,35)||
' ENABLE CONSTRAINT '||constraint_name||' ;'
from user_constraints c, user_tables u
where c.table_name = u.table_name;
select 'exit;' from dual;
set termout on
prompt Enabling constraints now...
set termout off
@tmp_enable;
!rm -i tmp_enable.sql;
exit
/

CS3 Camera Raw Too Many Files Open at the Same time alert!!!

Please help me. I keep getting this error message in Camera Raw that says there are too many files open at the same time - but I only have 100 open:( Please help - I was getting this error with CS2 and thought upgrading to CS3 would fix it and it didn't!!!

> "10 or 100 - you can quickly go through a stack of images in ACR and make any desired changes you want. Whether making the same or similar adjustment to similar files, or making radically different adjustments to different images as appropriate".
I've done this with far more than 100! I think my maximum is 425 raw files, invoking ACR from Bridge without Photoshop even loaded, and it worked well. (I've also done 115 JPEGs in order to crop them under extreme time constraints).
It can be very slick. For example, if I use a ColorChecker a number of times in a shoot, it is easy to select just the set (perhaps 100 or so) that a particular ColorChecker shot applies to and set the WB for all of them.
Furthermore, in case people don't know, you can set ratings on raw images while many of them are open in ACR. (Just click under the thumbnail). It isn't as powerful as Lightroom, but it is not to be dismissed.
I suspect that it is possible to apply sensor-dust-healing to lots of images in the same way, and certainly it is easy to apply presets based on various selections.
Perhaps with AMG (Adobe Media Gallery) it will be sensible to use the above capability to process 100s of raw files, then create a set of web pages for the best of them, in not much more time than it would have taken in Lightroom. I judge that Lightroom is the "proper" tool for the job (perhaps after 1.1!), but Bridge+ACR can go a long way.

3D camera constraints

Similar Messages

Maybe you are looking for