Published on

Concloud project general presentation

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. ATMOS based content retrival library. The Concloud project
  2. 2. Preface Content retrival and media indexing systems developing has become a bit of cultwords in the last years. Today we can observe a number of attempts to create some retrival systems, presented as web services, database buildups etc. That can't make us to stand that content retrival problem remains largely unsolved. We hope, we have been heading for right trend to solve some problems while on developing Concloud poject.
  3. 3. Let's combine the trends Cloud computing is an extensive conception in data manipulation for today. It is rather intenseand convinient solution both for storaging andcomputing. Drawing in of cloud computing by some big internet commerce market participant, such as Amazon has shown already opulance of such technology. EMC ATMOS provides all the preferences of cloud computing. Here we have: convinient api, simple system of metadata based retrival and classification, high level of reliability and safety .
  4. 4. Let's combine the trends What would it be alike, if we base our content retrival system on ATMOS? Will we gain some perfection? Firstly, we will chalange many problems with simple data manipulation due to convinient metadata managment. Its simple, it have good performance, its safety. Secondly, we will add more universality in our content retrival. For example: henceforth we are able to build retrival either on machine content indexing or on manual tagging each madia object.
  5. 5. What would it look like? <ul><li>*It's universal. We have wrapped our system in convinient system of libraries, that can be attached to every web services or application </li></ul><ul><li>*It's simple to use. Really simpe, try and make sure! </li></ul><ul><li>*It is on leading edge of algorithms. </li></ul>
  6. 6. Where can I use it right now Ok, if you are developing something for domains that sounds like: <ul><li>* Art collections </li></ul><ul><li>* Photograph archives </li></ul><ul><li>* Retail catalogs </li></ul><ul><li>* Medical diagnosis </li></ul><ul><li>* Crime prevention </li></ul><ul><li>* Intellectual property </li></ul><ul><li>* Architectural and engineering design </li></ul><ul><li>. </li></ul>
  7. 7. Where can I use it right now <ul><li>* Geographical information and remote sensing systems </li></ul><ul><li>* Social networking </li></ul><ul><li>* Media services </li></ul><ul><li>* Something so cool, that you definitly can speak about only to investors. </li></ul>
  8. 8. Where can I use it right now While the advantages of usage of content retrival in projects like remote sensing systems, photograph archieves and social networking is rather evidental, the usage of it in web commerce and Intellectual property can involve some new ideas, that you can observe in other parts of our presentation. See part applications.
  9. 9. How does it look like? <ul><li>All weakly perceptable image noises are ignored. </li></ul><ul><li>The same shape and edges points that images are suspiciously similar. </li></ul>For today we present you a library that provides interface capable to upload picture to ATMOS and retrive images by passing sample picture passed by user. Our system then returns all pictures visually and even cognotively similar to samle. Here we have some requirements our algorithm satisfy:
  10. 10. How does it look like? <ul><li>If shapes are not geometrically same, but we know that they are close, algorithm takes it into account. For example «A» and «А» are really close. </li></ul><ul><li>We may consider knowledges about picture, given by our users. </li></ul><ul><li>The same pictures are... same. </li></ul><ul><li>An amount of ajustments can be provided to user to optimize retrival. If user simply wants </li></ul>
  11. 11. What we are expecting to develop? <ul><li>Video. Retrival of content from video. </li></ul><ul><li>Faces. More flexible work with faces. </li></ul><ul><li>Computation of content difference. </li></ul>