Computer Vision

Can anyone recommend/update me with the latest/best method for 3D object recognition from 2D images?
Thanks

sooo and now think a second about it and guess which kind of variable they use in the database...could it be a short integer?^^
and btw 11111111 (binary) is 511 (decimal) and not 255
but u can only go to 255 coz its a signed integer, so one bit is used for the sign --> values form -255 - +255 r possible...

//Hahahahahaha, smart asses at their best.

i c

>>2
Traceback (most recent call last):
  File "<http://dis.chan.org/prog>";, line 1464, in 4chan BBS - Programming
SenseError: does not make sense

>>4
ON ERROR RESUME NEXT

>>5
I'll tell you what sir; now everybody faps to exceptions and how good and modern are they, but it was good old, shitty old Basic, that fugly piece of crap, the first widely available language to introduce them, and it even has features which I'd like to have in decent langauges like RESUME NEXT (where's my RESUME NEXT in Python?)

BASIC to English Translator
Version 1.2
Input: ON ERROR RESUME NEXT
Translation:
Computer: OH SHIT ERRORS ARE TEH HAPPENING
Programmer: pass me another doobie.

>>7
Version 1.3
Input: ON ERROR RESUME NEXT
Translation:
Computer: DO NOT WANT at module xyz line 1234
Programmer: Shut up and continue, I know part of it will fail and it's ok to go on

Just think of MySQL's INSERT IGNORE, for example.

>>6
(where's my RESUME NEXT in Python?)

try:
    raise Exception #replace with code expected to raise an exception
except Exception: #replace 'Exception' with exception expected to be raised
    pass

>>9
For that to be equivalent to ON ERROR RESUME NEXT through a code block, you'd have to go like:

try: statement1
except: pass
try: statement2
except: pass
try: statement3
except: pass
...
I'd like to have something like:

try:
    statement1
    statement2
    statement3
    ...
except:
    quit bellyaching and continue you fucking moron! #<--Pythonic

READ THE PROCEEDINGS OF THE PAST 5 YEARS OF COMPUTER VISION CONFERENCES AND STOP BEING A FAGGOT.

>>10

If you have an entire block of code where you expect each line to throw an exception, YOU ARE DOING IT WRONG. Anyway, here's how to get that behavior, stupid as it is.

def begin():
    import sys
    sys.excepthook = lambda type, value, traceback: None

def end():
    import sys
    sys.excepthook = sys.__excepthook__
Example usage:

>>> raise Exception
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
Exception
>>> begin()
>>> raise Exception
>>> end()
>>> raise Exception
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
Exception

>>10
Stroustrup says you fail:
http://www.research.att.com/~bs/bs_faq2.html#resume

>>11
I shove "visions" up my ass, then shit them down the toilet

>>12
Awesome

>>13
I say he fails; I may have a block of code of shit to try knowing that many may fail, knowing that nothing depends on each other's success (or, if it does, it'll just fail again and go on without side effects).

>>14
I say he fails
Stroustrup is the guy who invented C++. Enjoy being unemployed, because nobody's going to hire you with such horrible programming practices.

I may have a block of code of shit to try knowing that many may fail
As >>12 said, YOU'RE DOING IT WRONG. There is no excuse for having a block of code like that. What could you possibly be doing to have an entire block of code that could fail at any line?

>>15
any block of code could fail at any line.

>>16
Not if the code is proven safe.

>>17
    $ while ( == )
    while? /usr/bin/true
    while? end
    ^Z
    Suspended
    $ ps|grep true
    53484  p2  T      0:00.00 /usr/bin/true
    53496  p2  R+     0:00.00 grep true
    $ kill -FPE 53484
    $ fg
    /usr/bin/true
    Floating exception (core dumped)

>>15
Stroustrup is the guy who invented C++
I know. If I were asked for a clean, nice language, I probably wouldn't think of C++.

Enjoy being unemployed
I'm not, how about you?

As >>12 said, YOU'RE DOING IT WRONG. There is no excuse for having a block of code like that. What could you possibly be doing to have an entire block of code that could fail at any line?
The first example that comes to my mind is a quick shell-like uninstall script which has to remove files, registry keys, directories, links, etc. and ignores everything it cannot do.

>>17
In dreamland, code can be proven safe.

Stroustrup is the guy who invented C++
KILL HIM WITH FIRE

>>19
In dreamland, code can be proven safe.

What?  I thought code verification was a well known technique...  I guess I stumbled into /prog/ again.

>>19
The first example that comes to my mind is a quick shell-like uninstall script which has to remove files, registry keys, directories, links, etc. and ignores everything it cannot do.

Oh wow. Yes, an uninstaller is JUST the thing I want to ignore all the shit it leaves lying around my hard drive and registry.

You're a fucking idiot. I hate programmers like you. Thanks for leaving my hard disk filled with garbage.

>>22
If the program can't delete it, what do you want it to do, pray to god? Alright, if it's nice it can at least tell you that shit sux about a certain resource it can't get rid of, but that's all.

>>22

I think you're missing the bigger problem:
WHY THE FUCK WOULD YOU HAVE A SEPARATE "REMOVE SHIT" CALL FOR EACH ITEM? DEAR GOD, WHY?!

1. Put each item in a list.
2. Do a for loop over the list calling your "remove shit" function on each item.
3. Wrap the call to "remove shit" in a try/except block.
4. ???
5. SANE CODE!

>>24
Cause it's different kinds of shit

>>23
Yes, exactly. I want it to TELL ME, so I can go unlock and remove them myself. I don't want it to be like "UNINSTALL SUCCESSFUL HURR HURR HURRRRRRRRRR" only to find my harddrive and registery littered in shit.

>>24
While I agree, that's probably not what he meant. He probably just meant sticking an "On Error Remove Next" in front of the entire loop so he doesn't have to worry about handling the files that can't be removed.

>>25
So you have one for files, and you have one for registry keys genius. You should NOT be wrapping the loops in try blocks, but rather only the two remove calls in between. This way you can write different messages to a log file about what went wrong.

>>26
Why the fuck would you have to unlock a file?  Are you using some piece-of-shit deprecated OS like MS Vista?

>>26
Nah, I'd print "UNINSTALL MAY HAVE BEEN SUCCESSFUL... OR IT MAY NOT DURRRR... The thrill of life."

LISP

ur gay

my homework is to read the first chapter of SICP: Can someone do that for me please so I don't have to??

beware the army of 12 year old autistics

Bringing /prog/ back to its people
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy