Sir, we could use the Sobel operator to accomplish that! And then there was silence in the room. One of the great scientists was at risk of losing his credibility by admitting that he had never heard of the Sobel operator and hence he nodded somewhat sheepishly in agreement. I wouldn't be surprised a bit, if he had rushed to the library as soon as we left the room a few minutes later to find out what I had uttered a few minutes ago was indeed the right solution. This person was our so called senior supervisor during our final year engineering project on imaging. I recently ran into the Sobel operator not too long back while post processing some of the snaps in GIMP, and that's when I remembered this incident. I am pretty sure, the supervisor had some sleepless nights after that.
Just to give you guys a brief insight into the Sobel operator here, it is a matrix that can detect edges while processing a 2D image. I wish we had more time on our hands doing the project as the scope of pre and post image processing is really vast. Imaging is a very interesting field and even though I am currently no where near that stream, it was one of the first things of interest while leaping in to the professional world of software engineering.
Showing posts with label Technical. Show all posts
Showing posts with label Technical. Show all posts
Friday, March 20, 2009
Monday, February 9, 2009
Looking for Whitepapers?
If you are in an IT research field or are a Business Professional looking for technical info or a white paper, this is a very good site to find one.
Find Whitepapers.
Find Whitepapers.
Wednesday, January 7, 2009
CLR Programming
I want to keep this blog as generic as possible and hence the name "Literally No Reservations". Hey, a lot of people will tell you that your blog should focus on a particular topic, but I beleive that should not be the case. So adding to the variety of topics, here is my first technical blog. The topic deals with one of the aspects of my day to day work.
Over the span of my IT experience I have used many different programming languages ranging from Pascal to C# and every step has been a progress towards opening a new door to the possibilities of effective programming. I recently started working with CLR (Common Language Runtime) integration in SQL Server 2005. At first I was skeptical about the design and the purpose of this process, but as complexity increased I could see the benefits. Usually we are only used to programming the database layer using T-SQL and the application layer using .NET. But embedding the .NET code in the SQL Sever does give us a lot of flexibility. e.g. with T-SQL it is cumbersome to do heavy computing and procedural tasks as well as cross server data extraction and manipulation. But working with the extracted data and performing a variety of transformations and computations on the data using a .Net compliant language like C# makes it a lot easier. Recently I have been dealing with a lot of scenarios where I have to deal with cross server databases as the architecture has been widely dispersed, and using CLR to do the work is a great help.
Well there are some restrictions to this process though. e.g. it is not a good idea to use this when the amount of data being worked on is really big. This would really slow down the application. Debugging is also a crucial factor in deciding to use this path, as debugging can be troublesome, like with debugging and re-deploying any other assembly. But overall, for me as a solution developer, the pros out-weigh the cons. I would rather prefer writing a well maintained code than trying to gain a few nano-seconds over the performance of the code.
Below are some of the books that would be a good read on this topic:
Over the span of my IT experience I have used many different programming languages ranging from Pascal to C# and every step has been a progress towards opening a new door to the possibilities of effective programming. I recently started working with CLR (Common Language Runtime) integration in SQL Server 2005. At first I was skeptical about the design and the purpose of this process, but as complexity increased I could see the benefits. Usually we are only used to programming the database layer using T-SQL and the application layer using .NET. But embedding the .NET code in the SQL Sever does give us a lot of flexibility. e.g. with T-SQL it is cumbersome to do heavy computing and procedural tasks as well as cross server data extraction and manipulation. But working with the extracted data and performing a variety of transformations and computations on the data using a .Net compliant language like C# makes it a lot easier. Recently I have been dealing with a lot of scenarios where I have to deal with cross server databases as the architecture has been widely dispersed, and using CLR to do the work is a great help.
Well there are some restrictions to this process though. e.g. it is not a good idea to use this when the amount of data being worked on is really big. This would really slow down the application. Debugging is also a crucial factor in deciding to use this path, as debugging can be troublesome, like with debugging and re-deploying any other assembly. But overall, for me as a solution developer, the pros out-weigh the cons. I would rather prefer writing a well maintained code than trying to gain a few nano-seconds over the performance of the code.
Below are some of the books that would be a good read on this topic:
- CLR via C#, Second Edition. Author : Jeffrey Richter (Wintellect)
- Professional SQL Server 2005 CLR Programming: with Stored Procedures, Functions, Triggers, Aggregates and Types. Author : Derek Comingore, Douglas Hinson
Subscribe to:
Posts (Atom)
Posts
