AN APPARATUS AND A METHOD FOR GENERATING DATA REPRESENTING A PIXEL BEAM

Abstract

There are several types of plenoptic devices and camera arrays available on the market, and all these light field acquisition devices have their proprietary file format. However, there is no standard supporting the acquisition and transmission of multi-dimensional information. It is interesting to obtain information related to a correspondence between pixels of a sensor of said optical acquisition system and an object space of said 10 optical acquisition system. Indeed, knowing which portion of the object space of an optical acquisition system a pixel belonging to the sensor of said optical acquisition system is sensing enables the improvement of signal processing operations. The notion of pixel beam, which represents a volume occupied by a set of rays of light in an object space of an optical system of a camera along with a compact format for storing such information is thus introduce.

Description

TECHNICAL FIELD

The present invention relates to generation of data representing a light field.

BACKGROUND

The acquisition of four-dimensional or 4D light-field data, which can be viewed as a sampling of a 4D light field, i.e. the recording of light rays, is explained in the article “Understanding camera trade-offs through a Bayesian analysis of light field projections” by Anat Levin and al., published in the conference proceedings of ECCV 2008 is an hectic research subject.

Compared to classical two-dimensional or 2D images obtained from a camera, 4D light-field data enable a user to have access to more post-processing features that enhance the rendering of images and the interactivity with the user. For example, with 4D light-field data, it is possible to perform refocusing of images with freely selected distances of focalization meaning that the position of a focal plane can be specified/selected a posteriori, as well as changing slightly the point of view in the scene of an image. In order to acquire 4D light-field data, several techniques can be used. For example, a plenoptic camera is able to acquire 4D light-field data. Details of the architecture of a plenoptic camera are provided in FIG. 1A. FIG. 1A is a diagram schematically representing a plenoptic camera 100. The plenoptic camera 100 comprises a main lens 101, a microlens array 102 comprising a plurality of micro-lenses 103 arranged in a two-dimensional array and an image sensor 104.

Another way to acquire 4D light-field data is to use a camera array as depicted in FIG. 1B. FIG. 1B represents a multi-array camera 110. The multi-array camera 110 comprises a lens array 112 and an image sensor 114.

In the example of the plenoptic camera 100 as shown in FIG. 1A, the main lens 101 receives light from an object (not shown on the figure) in an object field of the main lens 101 and passes the light through an image field of the main lens 101.

At last, another way of acquiring a 4D light field is to use a conventional camera that is configured to capture a sequence of 2D images of a same scene at different focal planes. For example, the technique described in the document “Light ray field capture using focal plane sweeping and its optical reconstruction using 3D displays” by J.-H. Park et al., published in OPTICS EXPRESS, Vol. 22, No. 21, in October 2014, may be used to achieve the acquisition of 4D light field data by means of a conventional camera.

There are several ways to represent 4D light-field data. Indeed, in the Chapter 3.3 of the Ph.D dissertation thesis entitled “Digital Light Field Photography” by Ren Ng, published in July 2006, three different ways to represent 4D light-field data are described. Firstly, 4D light-field data can be represented, when recorded by a plenoptic camera by a collection of micro-lens images. 4D light-field data in this representation are named raw images or raw 4D light-field data. Secondly, 4D light-field data can be represented, either when recorded by a plenoptic camera or by a camera array, by a set of sub-aperture images. A sub-aperture image corresponds to a captured image of a scene from a point of view, the point of view being slightly different between two sub-aperture images. These sub-aperture images give information about the parallax and depth of the imaged scene. Thirdly, 4D light-field data can be represented by a set of epipolar images see for example the article entitled: “Generating EPI Representation of a 4D Light Fields with a Single Lens Focused Plenoptic Camera”, by S. Wanner and al., published in the conference proceedings of ISVC 2011.

Light-field data can take up large amounts of storage space which can make storage cumbersome and processing less efficient. In addition light-field acquisition devices are extremely heterogeneous. Light-field cameras are of different types for example plenoptic or camera arrays. Within each type there are many differences such as different optical arrangements, or micro-lenses of different focal lengths. Each camera has its own proprietary file format. At present here is no standard supporting the acquisition and transmission of multi-dimensional information for an exhaustive over-view of the different parameters upon which a light-field depends. As such acquired light-field data for different cameras have a diversity of formats. The present invention has been devised with the foregoing in mind.

SUMMARY OF INVENTION

According to a first aspect of the invention there is provided a computer implemented method for generating data representative of a volume, in an object space of an optical acquisition system, occupied by a set of rays of light passing through a pupil of said optical acquisition system and a conjugate of at least one pixel of a sensor of said optical acquisition system said volume occupied by said set of rays of light being called a pixel beam, the method comprising:

• • acquiring a collection of rays of light, each rays of light of said collection being representative of a pixel beam, and at least a first parameter defining the conjugate of the pixel;
  • obtaining intersection data defining intersections of a ray representative of the pixel beam with a plurality of given reference planes, said reference planes being parallel to one another and corresponding to different depths in the object space;
  • obtaining ray diagram parameters defining the graphical representation of the intersection data in a 2D ray diagram, and
  • associating said ray diagram parameters with the at least first parameter defining the conjugate of the pixel to provide data representative of said pixel beam.

According to an embodiment of the invention, the method further comprises:

• • encoding a difference between a first value and a second value of the first parameter defining the conjugate of the pixel, said difference being associated with said ray diagram parameters to provide data representative of said pixel beam.

According to an embodiment of the invention, the interception data corresponding to the ray representative of the pixel beam is graphically represented in the ray diagram as datalines and the ray diagram parameters include data representative of at least one of:

• • the slope of a dataline; and
  • an interception of a dataline with an axis of the ray diagram.

According to an embodiment of the invention, the datalines are detected in the 2D ray diagram by applying a Radon transform.

According to an embodiment of the invention, the graphical representation is provided as an matrix of cells to provide a digital dataline, each digital dataline format being defined by a plurality of cells, at least one first cell representative of the interception of the line with an axis and at least one second cell from which the slope of the line may be determined.

According to an embodiment of the invention, each digital dataline is generated by application of Bresenham's algorithm.

According to an embodiment of the invention, the data representative of the pixel beam further comprises colour data representing the colour of the corresponding ray representative of the pixel beam.

According to an embodiment of the invention, the data representative of the pixel beam is provided as meta data, the header of meta data comprising the ray diagram parameters defining the graphical representation of the intersection data in a 2D ray diagram and the body of the metadata comprising data representative of colour of the ray and the parameters defining a position and a size of the conjugate of the pixel in the object space.

Another object of the invention concerns a device for generating data representative of a volume, in an object space of an optical acquisition system, occupied by a set of rays of light passing through a pupil of said optical acquisition system and a conjugate of at least one pixel of a sensor of said optical acquisition system said volume occupied by said set of rays of light being called a pixel beam, the device comprising a processor configured to:

• • acquire a collection of rays of light, each rays of light of said collection being representative of a pixel beam, and at least a first parameter defining the conjugate of the pixel;
  • obtain intersection data defining intersections of a ray representative of the pixel beam with a plurality of given reference planes, said reference planes being parallel to one another and corresponding to different depths in the object space;
  • obtain ray diagram parameters defining the graphical representation of the intersection data in a 2D ray diagram, and
  • associate said ray diagram parameters with the at least first parameter defining the conjugate of the pixel to provide data representative of said pixel beam.

According to an embodiment of the invention, the processor of the device is further configured to:

• • encode a difference between a first value and a second value of the first parameter defining the conjugate of the pixel, said difference being associated with said ray diagram parameters to provide data representative of said pixel beam.11. A light field imaging device comprising:
    • an array of micro lenses arranged in a regular lattice structure;
    • a photosensor configured to capture light projected on the photosensor from the array of micro lenses, the photosensor comprising sets of pixels, each set of pixels being optically associated with a respective micro lens of the array of micro lenses; and
    • a device for providing metadata in accordance with claim 11.

Another object of the invention concerns a digital file comprising data representative of a volume, in an object space of an optical acquisition system, occupied by a set of rays of light passing through a pupil of said optical acquisition system and a conjugate of at least one pixel of a sensor of said optical acquisition system said volume occupied by said set of rays of light being called a pixel beam, said data comprising:

• • a ray diagram parameters defining the graphical representation in a 2D ray diagram of intersection data of the ray representative of the pixel beam, the intersection data defining intersections of the light field ray representative of the pixel beam with a plurality of given reference planes, said reference planes being parallel to one another and corresponding to different depths in the object space;
  • color data defining colors of the light field ray representative of the pixel beam, and
  • parameters defining a position and a size of a conjugate of the pixel in the object space of the optical acquisition system. Some processes implemented by elements of the invention may be computer implemented. Accordingly, such elements may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit”, “module” or “system”. Furthermore, such elements may take the form of a computer program product embodied in any tangible medium of expression having computer usable program code embodied in the medium.

Since elements of the present invention can be implemented in software, the present invention can be embodied as computer readable code for provision to a programmable apparatus on any suitable carrier medium. A tangible carrier medium may comprise a storage medium such as a floppy disk, a CD-ROM, a hard disk drive, a magnetic tape device or a solid state memory device and the like. A transient carrier medium may include a signal such as an electrical signal, an electronic signal, an optical signal, an acoustic signal, a magnetic signal or an electromagnetic signal, e.g. a microwave or RF signal.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention will now be described, by way of example only, and with reference to the following drawings in which:

FIG. 1A is a diagram schematically representing a plenoptic camera;

FIG. 1B represents a multi-array camera;

FIG. 2A is a functional diagram of a light-field camera according to an embodiment of the invention;

FIG. 2B is a functional diagram of a light-field data formator and light-field data processor according to an embodiment of the invention;

FIG. 3 is an example of a 2D light-field image formed on a photosensor array;

FIG. 4 represents a volume occupied by a set of rays of light in an object space of an optical system of a camera or optical acquisition system;

FIG. 5 represents a hyperboloid of one sheet;

FIGS. 6A and 6B graphically illustrate the use of reference planes for parameterisation of light-field data in accordance with one or more embodiments of the invention;

FIG. 7 schematically illustrates representation of light-field rays with respect to reference planes in accordance with embodiments of the invention;

FIG. 8A is a flow chart illustrating steps of a method in accordance with one or more embodiments of the invention;

FIG. 8B is a functional block diagram illustrating modules of a device for providing a light data format in accordance with one or more embodiments of the invention;

FIG. 9 schematically illustrates parameters for representation of light-field rays in accordance with embodiments of the invention;

FIG. 10 is a 2D ray diagram graphically illustrating intersection data in accordance with embodiments of the invention;

FIG. 11 graphically illustrates a digital line generated in accordance with embodiments of the invention;

FIG. 12 graphically illustrates digitals line generated in accordance with embodiments of the invention;

FIG. 13-13C graphically illustrate Radon transforms applied to a digital line in accordance with embodiments of the invention; and

FIG. 14 is a 2D ray diagram graphically illustrating intersection data for a plurality of cameras in accordance with embodiments of the invention;

FIGS. 15A and 15B are a flow charts illustrating steps of a method in accordance with one or more embodiments of the invention;

FIG. 16 represents the geometric shape of a Gaussian beam.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the present principles can be embodied as a system, method or computer readable medium. Accordingly, aspects of the present principles can take the form of an entirely hardware embodiment, an entirely software embodiment, (including firmware, resident software, micro-code, and so forth) or an embodiment combining software and hardware aspects that can all generally be referred to herein as a “circuit”, “module”, or “system”. Furthermore, aspects of the present principles can take the form of a computer readable storage medium. Any combination of one or more computer readable storage medium(a) may be utilized.

Embodiments of the invention provide formatting of light-field data for further processing applications such as format conversion, refocusing, viewpoint change and 3D image generation.

FIG. 2A is a block diagram of a light-field camera device in accordance with an embodiment of the invention. The light-field camera comprises an aperture/shutter 202, a main (objective) lens 201, a micro lens array 210 and a photosensor array 220 in accordance with the light-field camera of FIG. 1A. In some embodiments the light-field camera includes a shutter release that is activated to capture a light-field image of a subject or scene. It will be appreciated that the functional features may also be applied to the light-field camera of FIG. 1B.

The photosensor array 220 provides light-field image data which is acquired by LF Data acquisition module 240 for generation of a light-field data format by light-field data formatting module 250 and/or for processing by light-field data processor 255. Light-field data may be stored, after acquisition and after processing, in memory 290 in a raw data format, as sub aperture images or focal stacks, or in a light-field data format in accordance with embodiments of the invention.

In the illustrated example, the light-field data formatting module 150 and the light-field data processor 255 are disposed in or integrated into the light-field camera 200. In other embodiments of the invention the light-field data formatting module 250 and/or the light-field data processor 255 may be provided in a separate component external to the light-field capture camera. The separate component may be local or remote with respect to the light-field image capture device. It will be appreciated that any suitable wired or wireless protocol may be used for transmitting light-field image data to the formatting module 250 or light-field data processor 255; for example the light-field data processor may transfer captured light-field image data and/or other data via the Internet, a cellular data network, a WiFi network, a BlueTooth communication protocol, and/or any other suitable means.

The light-field data formatting module 250 is configured to generate data representative of the acquired light-field, in accordance with embodiments of the invention. The light-field data formatting module 250 may be implemented in software, hardware or a combination thereof.

The light-field data processor 255 is configured to operate on raw light-field image data received directly from the LF data acquisition module 240 for example to generate focal stacks or a matrix of views in accordance with embodiments of the invention. Output data, such as, for example, still images, 2D video streams, and the like of the captured scene may be generated. The light-field data processor may be implemented in software, hardware or a combination thereof.

In at least one embodiment, the light-field camera 200 may also include a user interface 260 for enabling a user to provide user input to control operation of camera 100 by controller 270. Control of the camera may include one or more of control of optical parameters of the camera such as shutter speed, or in the case of an adjustable light-field camera, control of the relative distance between the microlens array and the photosensor, or the relative distance between the objective lens and the microlens array. In some embodiments the relative distances between optical elements of the light-field camera may be manually adjusted. Control of the camera may also include control of other light-field data acquisition parameters, light-field data formatting parameters or light-field processing parameters of the camera. The user interface 260 may comprise any suitable user input device(s) such as a touchscreen, buttons, keyboard, pointing device, and/or the like. In this way, input received by the user interface can be used to control and/or configure the LF data formatting module 250 for controlling the data formatting, the LF data processor 255 for controlling the processing of the acquired light-field data and controller 270 for controlling the light-field camera 200.

The light-field camera includes a power source 280, such as one or more replaceable or rechargeable batteries. The light-field camera comprises memory 290 for storing captured light-field data and/or rendered final images or other data such as software for implementing methods of embodiments of the invention. The memory can include external and/or internal memory. In at least one embodiment, the memory can be provided at a separate device and/or location from camera 200. In one embodiment, the memory includes a removable/swappable storage device such as a memory stick.

The light-field camera may also include a display unit 265 (e.g., an LCD screen) for viewing scenes in front of the camera prior to capture and/or for viewing previously captured and/or rendered images. The screen 265 may also be used to display one or more menus or other information to the user. The light-field camera may further include one or more I/O interfaces 295, such as FireWire or Universal Serial Bus (USB) interfaces, or wired or wireless communication interfaces for data communication via the Internet, a cellular data network, a WiFi network, a BlueTooth communication protocol, and/or any other suitable means. The I/O interface 295 may be used for transferring data, such as light-field representative data generated by LF data formatting module in accordance with embodiments of the invention and light-field data such as raw light-field data or data processed by LF data processor 255, to and from external devices such as computer systems or display units, for rendering applications.

FIG. 2B is a block diagram illustrating a particular embodiment of a potential implementation of light-field data formatting module 250 and the light-field data processor 253.

The circuit 2000 includes memory 2090, a memory controller 2045 and processing circuitry 2040 comprising one or more processing units (CPU(s)). The one or more processing units 2040 are configured to run various software programs and/or sets of instructions stored in the memory 2090 to perform various functions including light-field data formatting and light-field data processing. Software components stored in the memory include a data formatting module (or set of instructions) 2050 for generating data representative of acquired light data in accordance with embodiments of the invention and a light-field data processing module (or set of instructions) 2055 for processing light-field data in accordance with embodiments of the invention. Other modules may be included in the memory for applications of the light-field camera device such as an operating system module 2051 for controlling general system tasks (e.g. power management, memory management) and for facilitating communication between the various hardware and software components of the device 2000, and an interface module 2052 for controlling and managing communication with other devices via I/O interface ports.

FIG. 3 illustrates an example of a 2D image formed on the photosensor array 104 of FIG. 1A or the photosensor array 114 of FIG. 1B. The 2D image, often referred to as a raw 4D light-field image, is composed of an array of micro images MI, each micro image being produced by the respective micro lens (i,j) of the microlens array 102,112. The micro images are arranged in the array in a rectangular lattice structure defined by axes i and j. A micro lens image may be referenced by the respective micro lens coordinates (i, j). A pixel PI of the photosensor 104, 114 may be referenced by its spatial coordinates (x, y). 4D light-field data associated with a given pixel may be referenced as (x, y, i, j).

There are several ways of representing (or defining) a 4D light-field image. For example, a 4D light-field image can be represented, by a collection of micro-lens images as previously described with reference to FIG. 3. A 4D light-field image may also be represented, when recorded by a plenoptic camera by a set of sub-aperture images. Each sub-aperture image of composed of pixels of the same position selected from each microlens image. Furthermore, a 4D light-field image may be represented by a set of epipolar images, which is not the case of the pixel beam.

Embodiments of the invention provide a representation of light-field data based on the notion of pixel beam. In this way the diversity in formats and light-field devices may be taken into account. Indeed, one drawback of ray based formats, is that the parametrization planes have to be sampled to reflect the pixel formats and sizes. Therefore, the sampling needs to be defined along other data in order to recover physical meaningful information.

A pixel beam 40, as shown on FIG. 4, represents a volume occupied by a set of rays of light in an object space of an optical system 41 of a camera. The set of rays of light is sensed by a pixel 42 of a sensor 43 of the camera through a pupil 44 of said optical system 41 Contrary to rays, pixel beams 40 may be sample at will since they convey per se the “etendue” which corresponds to the preservation of the energy across sections of the physical light rays.

A pupil of an optical system is defined as the image of an aperture stop as seen through said optical system, i.e. the lenses of the camera, which precedes said aperture stop. An aperture stop is an opening which limits the amount of light which passes through the optical system of the camera. For example, an adjustable diaphragm located near the front of a camera lens is the aperture stop for the lens. The amount of light admitted through the diaphragm is controlled by the diameter of the diaphragm opening which may be adapted depending of the amount of light a user of the camera wishes to admit. For example, making the aperture smaller reduces the amount of light admitted through the diaphragm, but increases the depth of focus. The effective size of a stop may be larger or smaller than its physical size because of the refractive action of a lens. Formally, a pupil is the image of the aperture stop through the optical system of the camera.

A pixel beam 40 is defined as a pencil of rays of light that reach a given pixel 42 when propagating through the optical system 41 via an entrance pupil 44. As light travel on straight lines in free space, the shape of such a pixel beam 40 can be defined by two sections, one being the conjugate 45 of the pixel 42, and the other being the entrance pupil 44. The pixel 42 is defined by its non-null surface and its sensitivity map.

Thus, a pixel beam may be represented by an hyperboloid of one sheet 50, as shown on FIG. 5, supported by two elements: the pupil 54 and the conjugate 55 of the pixel 42 in the object space of the camera.

A hyperboloid of one sheet is a ruled surface that can support the notion of pencil of rays of light and is compatible with the notion of “etendue” of physical light beams.

A hyperboloid of one sheet corresponds to the geometry of a Gaussian beam. Indeed, in optics, a Gaussian beam is a beam of monochromatic electromagnetic radiation whose transverse magnetic and electric field amplitude profiles are given by a Gaussian function; this also implies a Gaussian intensity profile. This fundamental transverse Gaussian mode describes an intended output of most lasers, since such a beam of light can be focused into the most concentrated spot.

The equations below assume a beam with a circular cross-section at all values of this can be seen by noting that a single transverse dimension, r, appears.

At a position z along the beam (measured from the focus), the spot size parameter w is given by¹

$w\left(z\right)=w_0\sqrt{1+{\left(\frac{z}{z_R}\right)}^2}$

where w₀ is the waist size.

As represented on FIG. 16, at a distance from the waist equal to the width w of the beam is equal to √{square root over (2)}w₀.

Although the tails of a Gaussian function never actually reach zero, for. This means that far from the waist, the beam “edge” is cone-shaped. The angle between lines along that cone (whose r=w(z)) and the central axis of the beam (r=0) is called the divergence of the beam.

The total angular spread of the beam far from the waist is then given by Θ=2θ. In an embodiment of the invention, a pixel beam 40, 50 is defined by four independent parameters: z_p, θ_x, θ_y, α defining the position and size of the pixel conjugate 45, 55, in front of the pupil 44, 54.

A hyperboloid of one sheet representing a pixel beam may be defined by the following equation:

$\begin{array}{cc}\frac{{\left(x-z·t_x\right)}^2}{a^2}+\frac{{\left(y-z·t_y\right)}^2}{a^2}-\frac{{\left(z-z_p\right)}^2}{c^2}=1& \left(1\right)\end{array}$

where t_x=tan θx and t_y=tan θy.

An origin O of a coordinate system (x, y, z) in which the parameters of the pixel beam 40, 50 are defined corresponds to the centre of the conjugate of the pixel as shown on FIG. 4, a, b, c are homologous to the length of semi-axes along Ox, Oy, Oz respectively, where a represents the radius of the of waist along Ox; b represents the radius of the waist along Oy and c defines an angular aperture of the pixel beam. In some embodiments of the invention, a and b have identical values, in these cases, the waist has a circular shape.

The parameters θ_x, θ_y, define a chief ray directions relative to the entrance of the pupil 44 centre. They depend on the pixel 42 position on the sensor 43 and on the optical elements of the optical system 41. More precisely, the parameters θ_x, θ_y represent shear angles defining a direction of the conjugate 45 of the pixel 42 from the centre of the pupil 44.

The parameter z_p represents a distance of the waist 55 of the pixel beam 40, 50, or the conjugate 45 of the pixel 42, along the z axis.

The parameter a represents the radius of the waist 55 of the pixel beam 40, 50, and c is given by the following equation:

$\begin{array}{cc}{c}^2=\frac{a^2z_P^2}{r^2-a^2}& \left(2\right)\end{array}$

where r is the radius of the pupil 44, 54.

The computation of the values of the parameters z_p, a and c is realized for each pixel beam of a given camera during a calibration phase of said camera. This calibration phase consists, for example, in running a program capable of modelling a propagation of rays of light through the optical system of the camera. Such a program is for example an optical design program such as Zemax, ©, ASAP © or Code V ©. An optical design program is used to design and analyze optical systems. An optical design program models the propagation of rays of light through the optical system; and can model the effect of optical elements such as simple lenses, aspheric lenses, gradient index lenses, mirrors, and diffractive optical elements, etc.

Thus, a pixel beam 40, 50 may be defined by its chief ray and the parameters z_p, a and c.

However, such a representation of a pixel beam 40, 50 takes up large amounts of storage space since the classical file format for storing rays consists in storing a position and a direction in a 3D space.

In order to propose a file format for storing rays which needs less storage space, a method for parametrizing the four dimensions of light-field radiance may be with reference to the cube illustrated in FIG. 6A. All six faces of the cube may be used to parameterize the light-field. In order to parameterize direction, a second set of planes parallel to the cube faces, may be added. In this way the light-field may be defined with respect to six pairs of planes with normals along the axis directions as:

{right arrow over (i)},−{right arrow over (i)},,−,{right arrow over (k)},−{right arrow over (k)}

FIG. 6B illustrates a light-field ray passing through two reference planes P1 and P2 used for parameterization positioned parallel to one another and located at known depths z₁ and z₂ respectively. The light-field ray intersects the first reference plane P₁ at depth at intersection point (x₁, y₁) and intersects the second reference plane P₂ at depth at intersection point (x₂, y₂). In this way the light-field ray may be identified by four coordinates (x₁, y₁, x₂, y₂). The light-field can thus be parameterized by a pair of reference planes for parameterization P₁, P₂ also referred herein as parametrization planes, with each light-field ray being represented as a point (x₁,y₁, x₂,x₂) ∈R⁴ in 4D ray space.

For example an origin of the reference co-ordinate system may be placed at the center of a plane P₁ generated by the basis vectors of the coordinate axis system {right arrow over (l₁)}, {right arrow over (J₁)}. The {right arrow over (k)} axis is normal to the generated plane P₁ and the second plane P₂ can be placed for the sake of simplicity at a distance =Δ from plane P₁ along the {right arrow over (k)} axis. In order to take into account the six different directions of propagation the entire light-field may be characterized by six pairs of such planes. A pair of planes, often referred to as a light slab characterizes the light-field interacting with the sensor or sensor array of the light-field camera along a direction of propagation.

The position of a reference plane for parameterization can be given as:

{right arrow over (x₀)}=d{right arrow over (n)} where {right arrow over (n)} is the normal and d is an offset from the origin of the 3D coordinate system along the direction of the normal.

A Cartesian equation of a reference plane for parameterization can be given as:

{right arrow over (n)}({right arrow over (x)}−{right arrow over (x)}₀)=0

If a light-field ray has a known position:

• • {right arrow over (x_l)}(x_i, y_i, z_i) and a normalised propagation vector:
  • {right arrow over (u)}(u₁, u₂, u₃) the general parametric equation of a ray in 3D may be given as:

{right arrow over (x)}=t{right arrow over (u)}+{right arrow over (x_l)}

The co-ordinates of the intersection {right arrow over (x1)} between the light-field ray and a reference plane are given as:

$\begin{array}{cc}\overrightarrow{x_1}=\overrightarrow{x_i}+\overrightarrow{u}\frac{\overrightarrow{n}\left(\overrightarrow{x_0}-\overrightarrow{x_i}\right)}{\overrightarrow{u}\overrightarrow{n}}& \left(A\right)\end{array}$

There is no intersection between the light-field rays and the reference parameterization if the following condition is not satisfied:

({right arrow over (x₁)}−{right arrow over (x₀)}){right arrow over (u)}>0

Due to the perpendicularity with one of the axes of the system of the pair of reference planes used to parameterize the light-field, one of the components of the ray intersection is always constant for each plane. Hence if there is an intersection of a light-field ray {right arrow over (x1)} with the first reference plane, and the intersection {right arrow over (x2)} of the said light-field with the second reference plane, four coordinates vary and equation A can be used to calculate the four parameters of a light-field ray. These four parameters can be used to build up a 4D ray diagram of the light-field.

Assuming parameterization of the light-field with reference to two parameterization reference planes, data representing the light-field may be obtained as follows. If a reference system is set as pictured in FIG. 7 a first parametrization plane P1 is perpendicular to z axis at z=z1, a second parametrization plane P2 is arranged perpendicular to the z axis at z=z2 and a ray whose light-field parameters are L(x1; y1; x2; y2) are to be rendered at a location z=z3 where a photosensor array of a light-field camera is positioned. From equation (A):

$\overrightarrow{x_3}=\overrightarrow{x_2}+\overrightarrow{u}\frac{\overrightarrow{n}\left(z_3\overrightarrow{n}-\overrightarrow{x_2}\right)}{\overrightarrow{u}n}$ $\overrightarrow{x_3}=\overrightarrow{x_1}+\overrightarrow{u}\frac{\overrightarrow{n}\left(z_3\overrightarrow{n}-\overrightarrow{x_1}\right)}{\overrightarrow{u}\overrightarrow{n}}$ $\mathrm{with}$ $\overrightarrow{u}=\frac{\overrightarrow{x_2}-\overrightarrow{x_1}}{\overrightarrow{x_2}-\overrightarrow{x_1}}=\left(u_x,u_y,u_z\right)$ $\overrightarrow{n}\left(0,0,1\right)$

Developing the Above Expression Gives:

$x_3=x_2+\frac{u_x}{u_z}\left(z_3-z_2\right)$ $y_3=y_2+\frac{u_y}{u_z}\left(z_3-z_2\right)$ $z_3=z_3$ $x_3=x_1+\frac{u_x}{u_z}\left(z_3-z_1\right)$ $y_3=y_1+\frac{u_y}{u_z}\left(z_3-z_1\right)$ $z_3=z_3$

Both sets of equation should deliver the same point {right arrow over (x3)} as the rendered light-field ray at the new location. By replacing u_x; u_y; u_z with their corresponding expression as functions of {right arrow over (x1)} and {right arrow over (x2)}, if the second set of equation from the previous block is used and x3 and y3 are added together:

$x_1+\frac{z_3-z_1}{z_2-z_1}\left(x_2-x_1\right)+y_1+\frac{z_3-z_1}{z_2-z_1}\left(y_2-y_1\right)=x_3+y_3$

Leading to the Expression:

(z₂−z₂)(x₁−y₁)+(z₃−z₁)(x₂+y₂)=(z₂−z₁)(x₃+y₃)

Co-ordinates with a subscript ₃ relate to a known point (x₃, y₃, ) where the light-field is rendered. All depth co-ordinates z_i are known. The parameterisation planes are in the direction of propagation or rendering. The light-field data parameters L are (x₁, y₁, x₂, y₂)

The light-field rays that form an image at point (x₃, y₃, z₃) are linked by expression (B) which defines a hyper plane in .

This signifies that if images are to be rendered from a two-plane parametrized light-field, only the rays in the vicinity of hyperplanes need to be rendered, there is no need to trace them. FIG. 8A is a flow chart illustrating the steps of a method for generating data representative of a light-field according to one or more embodiments of the invention. FIG. 8B is a block diagram schematically illustrating the main modules of a system for generating data representative of a light-field according to one or more embodiments of the invention.

In a preliminary step S801 of the method parameters defining the different pixel beams associated to the pixels of the sensor of the camera are acquired either by calibrating the camera of by retrieving such parameters from a data file stored in a remote server or on a local storage unit such as the memory 290 of the camera or a flash disk connected to the camera.

Such parameters are the coordinates of the chief rays of the different pixel beams and the parameters z_p and a defining the position and size of the pixel conjugate in front of the pupil obtained for each pixel beam during the calibration of the camera. A chief ray of a pixel beam is a straight line passing through the centre of the waist and the centre of the pupil supporting the pixel beam. In another preliminary step S802 raw light-field data is acquired by a light-field camera 801. The raw light-field data may for example be in the form of micro images as described with reference to FIG. 3. The light-field camera may be a light-field camera device such as shown in FIG. 1A or 1B and 2A and 2B.

In step S803 the acquired light-field data is processed by ray parameter module 802 to provide intersection data (x₁, y₁, x₂, y₂) defining intersection of captured light-field rays, which correspond to chief rays of pixel beams 40, 50, with a pair of reference planes for parameterization P₁, P₂ at respective depths

From calibration of the camera the following parameters can be determined: the centre of projection (x₃, y₃,) the orientation of the optical axis of the camera and the distance f from the pinhole of the camera to the plane of the photosensor. The light-field camera parameters are illustrated in FIG. 9. The photosensor plane is located at depth . The pixel output of the photosensor is converted into geometrical representation of light-field rays. A light-slab comprising the two reference planes P₁ and P₂ is located at depths and , respectively, beyond , at the other side of the centre of projection of the camera to the photosensor. By applying a triangle principle to the light rays, pixel coordinates (x_p, y_p,) recording the light projected from the array of microlenses can be mapped to ray parameters i.e. reference plane intersection points (x₁, y₁, x₂, y₂) by applying the following expression:

$x_1=\frac{z_3-z_1}{z_3-z_p}x_p+\frac{z_1-z_p}{z_3-z_{p}}x_3$ $y_1=\frac{z_3-z_1}{z_3-z_p}y_p+\frac{z_1-z_p}{z_3-z_p}y_3$ $x_2=\frac{z_3-z_2}{z_3-z_p}x_p+\frac{z_1-z_p}{z_3-z_p}x_3$ $y_2=\frac{z_3-z_2}{z_3-z_p}y_p+\frac{z_1-z_p}{z_3-z_p}y_3$

The above calculation may be extended to multiple cameras with different pairs of triplets (x_p, y_p, )(x₃, x₃, ):

In the case of a plenoptic camera, a camera model with an aperture is used and a light-field ray is described in the phase space as having an origin (x_p, y_p, ) and a direction (x′₃, y′₃, 1). Its propagation unto the plane (x₃, y₃) at depth z₃ can be described as a matrix transform. The lens will act as an ABCD matrix to refract the ray and another ABCD propagation matrix will bring the ray onto the light-slab reference planes P₁ and P₂.

From this step intersection data (x₁, y₁, x₂, y₂) geometrically defining intersection of light-field rays with reference planes P₁, P₂ is obtained.

In step S804 2D ray a diagram graphically representing the intersection data (x₁, y₁, x₂, y₂) is obtained by ray diagram generator module 803.

FIG. 10 is a 2D ray diagram graphically representing intersection data (x₁, x₂) of light-field rays captured by a camera at location x₃=2 and depth =2 with an aperture |A|<0.5. The data lines of the ray diagram used to parameterise are sampled by 256 cells providing an image of 256×256 pixels.

If the ray diagram illustrated in FIG. 10 is interpreted as a matrix, it can be seen that it is sparsely populated. If the rays were to be saved individually in a file instead of the 4D phase space matrix, this would require saving for each ray, at least 2 bytes (int16) for each position x_i or x₃ plus 3 bytes for the color, i.e. 7 bytes per ray for a 2D slice light-field, and 11 bytes per ray for its full 4D representation. Even then, the rays would be stored randomly in the file which might be unsuitable for applications that need to manipulate the representation. The inventors of the present invention have determined how to extract only the representative data from the ray diagram matrix and to store the data in a file in a structured manner.

Since the light-field rays are mapped along data lines of the 2D ray diagram, it is more efficient to store parameters defining the data line rather than the line values themselves. Parameters defining the data line such as, for example, a slope defining parameter s and an axis intercept d may be stored with the set of light-field rays belonging to that data line.

This could require for example as little as 2 bytes for slope parameter s, 2 bytes for slope parameter d and then only 3 bytes per ray, Moreover, the rays may be ordered along lines in the file. In order to set lines through matrix cells so called digital lines are generated which approximate the ray lines with minimum error.

To locate the data lines and to obtain slope parameter s and intercept parameter d step S805 a Radon transform is performed by line detection module 804 on the ray diagram generated in step S804.

From the obtained slope parameter s and intercept parameter d a representative digital line is generated by digital line generation module 805 in step S806. In this step digital lines are generated by approximating an analytical line to its nearest grid point, for example by applying Bresenham's algorithm. Indeed Bresenham's algorithm provides a way to provide a digital line with minimal operation. Other methods may apply a fast discrete Radon transform calculation. An example of Bresenham application is one adapted from the following reference: hap.//www.cs.helsinki.fi/group/goa/mallinnus/lines/bresenh.html.

The digital format defines the data line by two points of a grid (0,d) and (N−1, s) d being the interception corresponding to the value of x₂ when x₁=0 and s being the slope parameter corresponding to the value of x₂ when x₁=N−1. From the digital format generated the slope a of each individual line may be expressed as a function of, and s, as:

$a=\frac{s-d}{N-1}$

where:

s∈{0,1, . . . N−1} and d∈{0,1, . . . N−1}

FIG. 11 illustrates an example of a digital line generated by application of Bresenham's algorithm.

FIG. 12 illustrates a group of digital lines having the same slope a (or s−d) but different intercepts d, the group of data lines being contiguous. The group of data lines is referred to herein as a bundle of lines and corresponds to a beam resulting from the camera not being ideally pinpoint. Each line addresses different pixels. In other words, one pixel belongs only to a unique line of a bundle with the same slope but different intercepts. The upper and lower boundaries of the axis interceptions dare given as d_max and d_min respectively.

Ray data parameterized by a sampled pair of lines (in 2D) and belonging to one camera, belong to a family of digital lines (beam) in the phase space used for representing the data. The header of the beam can simply contain the slope a and the thickness of the beam defined by the upper and lower boundaries of the axis interceptions d_max−d_min. The ray values will be stored as RGB colors along digital lines whose header can be d and s. Void cells of the ray diagram in the sampled space do not need to be stored. Coordinates x1; x2 of the rays can be deduced from the parameters d, s and from the position of the cell along the digital line.

Parameters to be estimated from the lightfield or from camera's geometry are the slope a the lower and upper bounds of the digital line intercepts (d_min, d_max), and the digital line parameters (d_i, s_i). The discrete Radon transform has already been discussed as a tool to measure the support location of the light-field in the ray diagram.

FIG. 13B shows the discrete Radon transform in the digital line parameter space (d, s) of the datalines of FIG. 13A. FIG. 13C is a zoom of the region of interest comprised in FIG. 12B. The beam of digital lines is located by the search for the maximum value parameters. There could be some offset between the geometrical center of symmetry of the DRT and the actual position of the maximum due to image content so that later on, an algorithm is used to pin-point the center of symmetry instead of the maximum. Then, the waist of the beam transform as shown on FIG. 13C is easy to find to give the values (d_min, d_max). Point (d_min=74, s=201) is the lower envelope of the beam of digital lines from FIG. 12A, and point (d_max=81, s=208) is the upper envelope of the beam of digital lines.

The equations of two orthogonal 2D sliced spaces from equation B is given as.

(z₂−z₃)(x₁+y₁)+(z₃−z₁)(x₂+y₂)=(z₂−z₁)(x₃+y₃)  (C)

If a 2D slice for x_i coordinates is taken, the equation of the beam of lines where ray data through an aperture of size A at (x₃, y₃, z₃) will map is given as:

$\begin{array}{cc}{x}_2=\frac{\left(z_3-z_2\right)}{\left(z_3-z_1\right)}x_1+\frac{\left(z_2-z_1\right)}{\left(z_3-z_1\right)}\left(x_3\pm A\right)={\mathrm{mx}}_1+\left(d_{m{\mathrm{ax}}_x}-d_{min_x}\right)& \left(D\right)\end{array}$

Similarly, if a 2D slice is taken for y_i coordinates:

$\begin{array}{cc}{y}_2=\frac{\left(z_3-z_2\right)}{\left(z_3-z_1\right)}y_1+\frac{\left(z_2-z_1\right)}{\left(z_3-z_1\right)}\left(y_3\pm A\right)={\mathrm{my}}_1+\left(d_{\mathrm{ma}x_y}-d_{min_y}\right)& \left(E\right)\end{array}$

As previously described, the values of m and d_maxx, d_minx, d_maxy, d_miny may be evaluated in the discrete domain to localize the characteristics of a light-field as defined by the format discussed previously, there is no need to perform a 4D discrete Radon transform. If two orthogonal 2D DRT are obtained, measurements can be performed of the slope m of the hyper-plane and the beam width of the digital hyper-planes where all data concentrates in the 4D ray-diagram.

This simpler procedure of location assumes a circular entrance pupil A so that d_maxx d_minx, d_maxy, d_miny will encompass all hyper-planes intercepts, some values written in the format will contain no values.

It would be interesting to obtain a format for the 4D case which is similar to what was proposed for the 2D case. To do so, it would be interesting to associate the 2D lines found on the Π(x₁, x₂), plane with the lines found on the Π(y₁, y₂) place, i.e., the lines that are the results of the intersection of the corresponding hyper plane with the two orthogonal slices of Π(x₁, x₂), and Π(y₁, y₂), From expressions D and E, it is known that the corresponding lines have the same slope m. This is the first parameter that associates each line in Π(x₁, x₂) to a line in Π(y₁, y₂), for a camera at a certain depth. If there are multiple cameras at the same depth (i.e., the case of FIG. 13A), thereare three lines in Π(x₁, x₂), and three lines in Π(y₁, y₂), with the same estimated slope of m. The correspondences in the line offsets between the lines in these two planes are then determined. To do this, the formulation of the lines in expressions D and E are exploited. In particular, denoting

$k=\frac{z_2-z_1}{z_3-z_1},$

the offsets are as follows:

$\begin{array}{cc}\{\begin{array}{c}{\mathrm{kx}}_3+\mathrm{kA}=d_{\mathrm{ma}x_x}\\ {\mathrm{kx}}_3-\mathrm{kA}=d_{min_x}\end{array}\mathrm{and}& \left(F\right)\\ \{\begin{array}{c}{\mathrm{ky}}_3+\mathrm{kA}=d_{\mathrm{ma}x_y}\\ {\mathrm{ky}}_3-\mathrm{kA}=d_{min_y}\end{array}& \left(G\right)\end{array}$

The sets of the equations may be solved for k, x₃ and y₃. Note that (x₃, y₃, z₃) correspond to the coordinates of the camera, or in other words the voxel where the corresponding bundle of light is focused into a circle of the radius A. We have supposed that the aperture on the plane positioned at z₃ is circular, so that d_maxx−d_minx=d_maxy−d_miny=2 kA, and by solving the previous sets of equations:

$\begin{array}{cc}k=\frac{d_{m{\mathrm{ax}}_x}-d_{min_x}}{2A}& \left(G\right)\\ x_3=A\frac{d_{m{\mathrm{ax}}_x}+d_{min_x}}{d_{\mathrm{ma}x_x}-d_{min_x}}& \left(H\right)\\ y_3=A\frac{d_{\mathrm{ma}x_y}+d_{min_y}}{d_{\mathrm{ma}x_y}-d_{min_y}}& \left(I\right)\\ z_3=\frac{z_2+\left(k-1\right)z_1}{k}& \left(J\right)\end{array}$

The digital lines may be scanned as before on Π(x₁, x₂) using the Bresenham digital lines; For each individual (x₁, x₂), value, the corresponding (y₁, y₂) values captured in the light-field are stored. To find such values, expression C is exploited. All the following are either known or estimated from expressions F and G x3; y3; z3; z1; z2

Moving on each line in Π(x₁, x₂), for each (x₁^q, x₂^q), the following relationship in (y₁, y₂) is obtained:

$y_2=\frac{z_3-z_2}{z_3-z_1}y_1+\frac{z_3-z_2}{z_3-z_1}x_1^q+\frac{z_2-z_1}{z_3-z_1}\left(x_3+y_3\right)-x_2^q$ Or,

y ₂ =my ₁ +mx ₁ ^q +k(x₃+y₃*)−x₂^q=my₁+d_off(x₁^q,x₂^q,x₃,y₃*)

For each point in Π(x₁, x₂), a collection of lines in Π(y₁, y₂) is saved. d_off corresponds to the offset of the lines scanned and saved for (x₁^q, x₂^q). It is noted that:

d _off(x₁^q,x₂^q)=mx₁^q+k(x₃+y₃*)−x₂^q

With reference to FIG. 12 each square is a (x₁^q, x₂^q), point, and for each one of these points, there is a set of Bresenham digital lines running out of the plane of the figure along a digital bundle defined by equation:

y ₂ =my ₁ +d _off(x₁^q,x₂^q,x₃,y₃*)  (K)

perpendicular to the depicted datalines, but in a 4D space.

An exemplary data format for a bundle of data lines per camera is illustrated in Table 1.

Table 1

Firstly general metadata of the 4D space is provided: including boundaries of the 4 axes x₁, x₂,y₁, y₂ and their corresponding sampling. The number of cameras (bundles) is also provided. For each camera j the following parameters are saved:

the size of the aperture: A_j, which corresponds to the diameter of the pupil of a pixel beam,

the focus point of the camera: cam, focusPoint=(u₃, u₃, w₃)

lowest d intercept in (x1_x,2)=d_j

steepness=m_j

number of digital lines in (x₁, x₂)=l_j^x

number of digital lines in (y₁, y₂)=l_j^xy

On each camera, for each (x^q₁; x^q₂), scanning is started on (y₁, y₂) with respect to expression (K) using the Bresenham digital lines, and the RGB values of each light-filed rays are saved. In particular y₃*−A to y₃*+A and the corresponding d_off is calculated according to expression (K).

Since the light-field rays correspond to the chief rays of the pixel beams, the values of the parameters z_p, a of a given pixel beam are to be stored alongside the RGB values of the corresponding light-field ray as shown in table 1. Since these two parameters are stored as float numbers, this makes the data format for a bundle of data lines per camera much bigger. Indeed, in table 1, each ray occupies 3 bytes and the parameters z_p, a each occupy 4 bytes. Hence, the parameters z_p, a impact heavily on the global file size.

In order to reduce the amounts of storage space, those two parameters z_p, a are thus encoded according to the following method executed, for example, by the light-field data formatting module 250 and represented on FIGS. 15A and 15B.

A float number is represented with significant digits, also called significand, and a scale using an exponent, the float term comes from that radix or comma sign that can float in the significand.

So in order to reduce the quantity of the float numbers stored in the data format for a bundle of data lines per camera as represented in table 1, it is proposed to encode the increments of the number in reference with a starting value. The variations of the number either positive, either negative are encoded on, for example 512 levels, from −254 to +255. In other embodiments of the invention, the variations of the number may be encoded on 256 or 128 levels. The value of the increments are adjusted according to the values and variations of a given parameter.

Thus, in a step S150, a starting float is used as a reference, it is for example a first value of the parameter for a first pixel beam of the collection of pixel beams of the camera.

In an embodiment of the invention, during a step S151, a difference between a second float representing a second value of the parameter for another pixel beam in the collection of pixel beam and the first value of the parameter , is computed. The second value and the first value of the parameter are consecutive float numbers in a data stream representing the light filed. This difference is stored in the table 1 instead of the second value of the parameter z_p. As the parameters defining the pixel beams are stored in an ordered spatio-angular manner, two consecutive values of the same parameter do vary by very small amounts.

During a step S152, a difference between a third float representing a third value of the parameter for another pixel beam in the collection of pixel beam and the second value of the parameter , is computed. In an embodiment of the invention, the third value and the second value of the parameter are consecutive float numbers in a data stream representing the light filed, i.e. the different values of a same parameter are grouped together in the data stream such as for example RGB, RGB, . . . ,z, z, . . . ,a, a, . . . . In this embodiment of the invention, it is easier to compact the data using methods called “deflate” an example of which is given by https://en.wikipedia.org/wiki/DEFLATE. This difference is stored in the table 1 instead of the third value of the parameter .

Those steps S151, S152 are executed for the values of the parameter representing the collection of pixel beams of the camera. The same steps are executed of the values of the parameter a.

In order to synchronize the stream of data and ensure the encoded values of the different parameters representing a pixel beam are reliable, in a step S153 a fourth value of the parameter is stored as a float number and not as a difference between two consecutive values of the parameter . The step S153 is executed for example every 100 float numbers.

In another embodiment of the invention, in a step S250, a starting float is used as a reference, it is for example a first value of the parameter for a first pixel beam of the collection of pixel beams of the camera.

In a step S251, a difference between a second float representing a second value of the parameter for another pixel beam in the collection of pixel beam and the first value of the parameter , is computed. In an embodiment of the invention, the second value and the first value of the parameter are consecutive float numbers in a data stream representing the light filed, i.e. the different values of a same parameter are grouped together in the data stream such as for example RGB,RGB, . . . ,z,z, . . . ,a,a, . . . . In this embodiment of the invention, it is easier to compact the data using methods called “deflate” an example of which is given by https://en.wikipedia.org/wiki/DEFLATE. This difference is stored in the table 1 instead of the second value of the parameter .

During a step S252, a difference between a third float representing a third value of the parameter for another pixel beam in the collection of pixel beam and the first value of the parameter, is computed. This difference is stored in the table 1 instead of the third value of the parameter .

Those steps S251, S252 are executed for the values of the parameter representing the collection of pixel beams of the camera. Thus, for each value of the parameter , the difference with the first value of parameter , which is the reference value, is calculated and stored in table 1. The same steps are executed of the values of the parameter a.

In order to synchronize the stream of data and ensure the encoded values of the different parameters representing a pixel beam are reliable, in a step S253 a fourth value of the parameter is stored as a float number and not as a difference between two consecutive values of the parameter and is considered the new reference for calculating the differences that are to be stored in table 1 instead of the corresponding values of parameter . The step S253 is executed for example every 100 float numbers.

This method relies on the assertion that two successive float numbers have only a small variation; F_t+1=F_t+ε. This small difference ε is encoded on 8 bits. In other embodiments of the invention, the difference may be encoded on 4, 12 or 16 bits. This enables to optimize the memory used on devices and network bandwidths.

The same calculations are performed in the decoding step using the stored metadata. In particular, k is found using equation (H). Hence the format remains compact. There is no need to store four indexes for each ray in the system and two float numbers for the parameters defining a pixel beam. It is noted that the sampling of the hyper-plane above is the sampling of the 4D ray-space and thus a single x1; y1; x2; y2 location is not missed. This is only one example of a systematic scanning of the 4D ray-space for saving all data in a very compact form. Other processes may of course be applied. The parametric form seems to be adapted to explore the hyper-plane because it permits an inter-leaved space exploration.

In the case of multiple cameras to work on data that contains several bundles of hyper-planes (several maxima in the Radon transform due to multiple cameras), a more complex algorithm may be used. As a pre-processing step, the parameters (in, k) are found for all the peaks in the radon transform of Π(x₁, x₂), and put in one set. The same is done for the peaks in (y₁, y₂) and the parameters are put in another set. Now in each iteration of the greedy algorithm, the maximum peak intensity is found in the 2D radon transform of (x₁, x₂) and the corresponding peak in (y₁, y₂) is found by matching the previously found parameters (m, k). After saving the data as mentioned in the last section, these peaks are cleaned from the radon transforms, and the next iteration is started, until nothing meaningful remains in the light-field.

Although the present invention has been described hereinabove with reference to specific embodiments, the present invention is not limited to the specific embodiments, and modifications will be apparent to a skilled person in the art which lie within the scope of the present invention.

Many further modifications and variations will suggest themselves to those versed in the art upon making reference to the foregoing illustrative embodiments, which are given by way of example only and which are not intended to limit the scope of the invention, that being determined solely by the appended claims. In particular the different features from different embodiments may be interchanged, where appropriate.

Claims

1. A computer implemented method for generating data representative of a volume, in an object space of an optical acquisition system, occupied by a set of rays of light passing through a pupil of said optical acquisition system and a conjugate of at least one pixel of a sensor of said optical acquisition system said volume occupied by said set of rays of light being called a pixel beam, the method comprising: acquiring a collection of rays of light, each rays of light of said collection being representative of a pixel beam, and at least a first parameter defining the conjugate of the pixel;obtaining intersection data defining intersections of a ray representative of the pixel beam with a plurality of given reference planes, said reference planes being parallel to one another and corresponding to different depths in the object space;obtaining ray diagram parameters defining the graphical representation of the intersection data in a 2D ray diagram, andassociating said ray diagram parameters with the at least first parameter defining the conjugate of the pixel to provide data representative of said pixel beam.

2. The method according to claim 1 further comprising: encoding a difference between a first value and a second value of the first parameter defining the conjugate of the pixel, said difference being associated with said ray diagram parameters to provide data representative of said pixel beam.

3. A method according to claim 2 wherein the interception data corresponding to the ray representative of the pixel beam is graphically represented in the ray diagram as datalines and the ray diagram parameters include data representative of at least one of: the slope of a dataline; andan interception of a dataline with an axis of the ray diagram.

4. A method according to claim 3 wherein the datalines are detected in the 2D ray diagram by applying a Radon transform.

5. A method according to claim 4 wherein the graphical representation is provided as a matrix of cells to provide a digital dataline, each digital dataline format being defined by a plurality of cells, at least one first cell representative of the interception of the line with an axis and at least one second cell from which the slope of the line may be determined.

6. A method according to claim 5 wherein each digital dataline is generated by application of Bresenham's algorithm.

7. A method according to claim 6 wherein the data representative of the pixel beam further comprises color data representing the color of the corresponding ray representative of the pixel beam.

8. A method according to claim 7 wherein the data representative of the pixel beam is provided as meta data, the header of meta data comprising the ray diagram parameters defining the graphical representation of the intersection data in a 2D ray diagram and the body of the metadata comprising data representative of color of the ray and the parameters defining a position and a size of the conjugate of the pixel in the object space.

9. A device for generating data representative of a volume, in an object space of an optical acquisition system, occupied by a set of rays of light passing through a pupil of said optical acquisition system and a conjugate of at least one pixel of a sensor of said optical acquisition system said volume occupied by said set of rays of light being called a pixel beam, the device comprising a processor configured to: acquire a collection of rays of light, each rays of light of said collection being representative of a pixel beam, and at least a first parameter defining the conjugate of the pixel;obtain intersection data defining intersections of a ray representative of the pixel beam with a plurality of given reference planes, said reference planes being parallel to one another and corresponding to different depths in the object space;obtain ray diagram parameters defining the graphical representation of the intersection data in a 2D ray diagram, andassociate said ray diagram parameters with the at least first parameter defining the conjugate of the pixel to provide data representative of said pixel beam.

10. The device according to claim 9 wherein the processor is further configured to: encode a difference between a first value and a second value of the first parameter defining the conjugate of the pixel, said difference being associated with said ray diagram parameters to provide data representative of said pixel beam.

11. A light field imaging device comprising: an array of micro lenses arranged in a regular lattice structure;a photosensor configured to capture light projected on the photosensor from the array of micro lenses, the photosensor comprising sets of pixels, each set of pixels being optically associated with a respective micro lens of the array of micro lenses; anda device for providing metadata in accordance with claim 9.

12. A device for rendering an image from light field data using obtained in accordance with the method of claim 1.

13. A digital file comprising data representative of a volume, in an object space of an optical acquisition system, occupied by a set of rays of light passing through a pupil of said optical acquisition system and a conjugate of at least one pixel of a sensor of said optical acquisition system said volume occupied by said set of rays of light being called a pixel beam, said data comprising: a ray diagram parameters defining the graphical representation in a 2D ray diagram of intersection data of the ray representative of the pixel beam, the intersection data defining intersections of the light field ray representative of the pixel beam with a plurality of given reference planes, said reference planes being parallel to one another and corresponding to different depths in the object space;color data defining colors of the light field ray representative of the pixel beam, andparameters defining a position and a size of a conjugate of the pixel in the object space of the optical acquisition system.

14. The digital file according to claim 13 obtained by the method comprising: acquiring a collection of rays of light, each rays of light of said collection being representative of a pixel beam, and at least a first parameter defining the conjugate of the pixel;obtaining intersection data defining intersections of a ray representative of the pixel beam with a plurality of given reference planes, said reference planes being parallel to one another and corresponding to different depths in the object space;obtaining ray diagram parameters defining the graphical representation of the intersection data in a 2D ray diagram, andassociating said ray diagram parameters with the at least first parameter defining the conjugate of the pixel to provide data representative of said pixel beam.

15. (canceled)