Is it possible to have a floating point representation in an array in LabVIEW?

Could anyone be able to tell me how I would go about creating a part of a Vi that would create a user defined N random arrays of user defined length consisting of floating point representation?
The values in the array cannot be limited to 0 and 1.
Thanks
Alan Homer

Sorry, I don't understand what you want,
N random arrays? You can build an array of required length, bundle it to a cluster and repeat this X times (Depending on how many arrays you need). Each cluster can then in turn be grouped to an array, whereby each array retains its own length.
You can easily define an array as an array of floating point numbers. Is this what you mean? (See picture)
I also don't quite understand what the values 0 and 1 have to do with your question as a whole.....
Trying to help
Shane
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
Attachments:
N random arrays.png ‏5 KB

Similar Messages

Floating Point Representations on SPARC (64-bit architecture)

Hi Reader,
I got hold of "Numerical Computation Guide -2005" by Sun while looking for Floating Point representations on 64 bit Architectures. It gives me nice illustrations of Single and Double formats and the solution for endianness with
two 32-bit words. But it doesn't tell me how it is for 64-bit SPARC or 64-bit x86.
I might be wrong here, but having all integers and pointers of 64-bit length, do we still need to break the floating point numbers and store them in lower / higher order addresses ??
or is it as simple as having a Double Format consistent in the bit-pattern across all the architectures (Intel, SPARC, IBMpowerPC, AMD) with 1 + 11 + 52 bit pattern.
I have tried hard to get hold of a documentation that explains a 64-bit architecture representation of a Floating Point Number. Any suggestion should be very helpful.
Thanks for reading. Hope you have something useful to write back.
Regards,
Regmee

The representation of floating-point numbers is specified by IEEE standard 754. This standard contains the specifications for single-precision (32-bit), and double-precision (64-bit) floating-point numbers (There is also a quad-precision (128-bit) format as well). OpenSPARC T1 supports both single and double precision numbers, and can support quad-precision numbers through emulation (not in hardware). The fact that this is a 64-bit machine does not affect how the numbers are stored in memory.
The only thing that affects how the numbers are stored in memory is endianness. SPARC architecture is big-endian, while x86 is little-endian. But a double-precision floating-point numer in a SPARC register looks the same as a double-precision floating-point number in an x86 register.
formalGuy

Question in floating point operation

Hi,
I have question in java floating point operation.
public class test
     public static void main(String args[])
          double d1 = 243.35 ;
          double d2 = 2.3 ;
          System.out.println(d1 * d2) ;
          System.out.println((float)d1 * (float)d2) ;
The result is,
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)
5.597049999999999E8
5.5970502E8
Though the multiplication does not result irrational number like 1/3, the result of the first statement is not accurate enough. In our project, this multiplication involves with money and we cannot ignore this.
Can anyone suggest why this is happening? Do I need to convert all the numbers to float to avoid this...Or Is it a bug?
~ Sathiya Dhanapal.

The underlying problem is that not all numbers can be represented exactly in a floating point representation. But if you perform all calculations using doubles and then round to two fractional digits at the end you should get a "correct" result UNLESS you have used ill-conditioned formulas introducing other kinds of arithmetic errors.
There's another way around this when it comes to counting money and that's to use integers (long or int). You convert every number to the lowest monetary unit (like a cent or whatever). Every money-amount can now be represented exactly but you still have to be careful because the rounding problem is still there (What do you do with the last cent when you split 100 cents in 3).
In your example the "more correct" you've got from using floats instead of doubles is only an illusion. The result has been implictly rounded becasuse fewer bits have been used. If you round the double result to the same precision as the float result, they're the same.
The important lesson in all this is TO KNOW WHEN TO ROUND.

Converting Floating Point

I am receiving numbers from a Tinius Olsen Model 290 Universal Testing System. I made a little program to send commands to the machine and receive the responses back as strings. For the decimal value 3.7620 I get the floating point number EDC57040. This is obviously not correct. The correct floating point representation is 4070C5ED, which is accomplished by swapping all the bits. I need to know how to do this in labview, basically go from the string representation of the floating point to the correct swapped floating point.

Here is a simple example:
Be aware that if you have an ancient version of LabVIEW, this option (byte order) is not available and you need to swap the bytes manually. No big deal, really.
Message Edited by altenbach on 05-08-2007 01:15 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
LittleEndianSGL.png ‏7 KB

Convert Floating Point Decimal to Hex

In my application I make some calculations using floating point format DBL,and need to write these values to a file in IEEE 754 Floating Point Hex format. Is there any way to do this using LabVIEW?

Mike,
Good news. LabVIEW has a function that does exactly what you want. It is well hidden though...
In the Advanced/Data manipulation palette there is a function called Flatten to String. If you feed this funtion with your DBL precision digital value you get the IEEE-754 hexadecimal floating point representation (64 bit) at the data string terminal (as a text string).
I attached a simple example that shows how it works.
Hope this helps. /Mikael Garcia
Attachments:
ieee754converter.vi ‏10 KB

32 bit Floating Point

Hello,
Running FCP 5.1
Having audio sync issues and was double checking my settings.
Although the sequence presets are at 16 bit, they are showing up in the browser as 32bit Floating Point.
Any thoughts?
I generally capture now at 30 minute increments and actually have always had this issue. FCP 4.5 and 5.1
all settings are where they should be.
although I do notice, obviously when the device is off, the audio output defaults to 'default' not to firewire dv.
thanks
iMac intel Mac OS X (10.4.8)

Some more details please. What hardware device are you sourcing the audio clips from? The likely culprit is your capture settings. What preset are you using? Check Audio/Video Settings-Capture Presets and see if the preset you've selected records audio as 32 bit. It will say in the right column after you've selected your preset.
If it says 32 bit there, click Edit to get the Capture Preset Editor. Under Quicktime Audio Settings, the Format field should give you a selection of sample rates and possibly alternate bit depths. If your only choice is 32 bit, (as it is for me when I capture audio via my RME, 32 bit Integer in my case) then you'd be well served by bringing those files into Peak or Quicktime and saving them as 16 bit Integer files to match your sequence settings.
If you've imported these files into FCP from an audio editor that can create 32 bit floating point audio files, eg Kyma, Sequoia, Nuendo, etc. then the same advice applies. The 32 bit files are much larger than they need to be and may upset the apple cart (he he, pun) when pulled into a sequence with different settings. More cpu overhead for sure.
Let us know what you find.

Floating point precision of "Flatten to XML"

It appears that the "Flatten to XML" function (LV 7.1.1) truncates floating point numbers to 5 decimal places. This is a rather annoying limitation, since I'm trying to store a relative time in hours, accurate to the second (chosen by a previous coder that I have to be compatible with - otherwise I'd just use seconds). Is there a workaround to this? (other than multiplying by some power of 10 before flattening, and dividing after unflattening)
Jaegen

Hi Paul and Jaegen,
I checked our databases and found entries of product suggestions and
corrective action requests for the behavior of the limited precision
when flattening to XML. I found an interesting reply from a LabVIEW
developer on the request for further precision:
The Flatten To XML primitive puposefully cuts off all numbers at 5
digits after the decimal. There are 3 main reasons for this:
Information regarding precision is not propagated on the wire.
Therefore, there is no real way to know how many significant digits or
even places past the decimal point is appropriate when data is
flattened to XML.
Bloat. If all floating point values printed all of the possible
decimal digits all of the time, this would provide for some very large
blocks of XML code.
Given the arbitrarily complex nature of LabVIEW data, it is
difficult to provide a method for specifying precision. For example, if
a user has a cluster of clusters, each of which contain a single,
double and extended representing various measurements of differing
accuracy, how can one precision setting be applied to each of these
values? The user would have to unbundle (and index if an array was
involved), flatten, concatenate, and then the reverse on the unflatten
side.
I suggest that you go ahead and file a new product suggestion by using the "feedback" link on www.ni.com/contact.
It would be best if you could give some detailed information on how you
would like LabVIEW to handle different scenarios while getting around
the above issues.
Thanks for the feedback!
- Philip Courtois, Thinkbot Solutions

Floating Point # in MIDP & CLDC...

What is way of using the floating point numbers in MIDP & CLDC?
MIDP and CLDC has no built in support for it.
Plz help me...

simple.... Don't :P
you've got fixed point libs available, but theyre not exactly fast.
It is possible to recompile the KVM and enable floating point support, but none of the embedded implementations have this support, so its a pointless excercise.
What do you need floating point for?

Floating point image resize?

I can't find any method which allows a floating-point image sizing.
I guess what I need is something like
float x, y, width, height;
g2d.drawImage(image, x, y, 0, width, height, null);
Is such a thing possible in Swing?
I'm animating a shrinking icon and the icon sways slightly from side to size due to inability to resize to n.5 pixels. The alternative I have is to only resize to even numbers of pixels, but this looks very jerky.
Thanks

Thanks, the AffineTransform approach works perfectly, no more wobbling.
The code which works for me is ...
    public static BufferedImage scaleCentered(Image image, float scaleX, float scaleY)
        int type = BufferedImage.TYPE_INT_ARGB;
        int width=image.getWidth(null);
        int height=image.getHeight(null);
        BufferedImage result=new BufferedImage(width, height, type);
        Graphics2D g2d = result.createGraphics();
        g2d.setRenderingHint(RenderingHints.KEY_INTERPOLATION, RenderingHints.VALUE_INTERPOLATION_BICUBIC);
        float centerX=image.getWidth(null) / 2;
        float centerY=image.getHeight(null) / 2;
        AffineTransform transform=new AffineTransform();
        transform.translate(centerX, centerY);
        transform.scale(scaleX, scaleY);
        transform.translate(-centerX, -centerY);
        g2d.setTransform(transform);
        g2d.drawImage(image, 0, 0, width, height, null);
        g2d.dispose();
        return result;
    }

32bit floating point is the audio sync problem

Hi,
just thought I post this solution.
We are working on a HD project (1h), ProRes422(HQ) setting, 48kHz. The footage was shot with EX-3.
When we got the sound back from the mix (WAV, 48kHz) is showed up in the finder as correct duration, but once placed into the timeline is shrunk and ended up too short (about 3sec) and hence the sync was lost.
Next step was getting a AIFF bounced out from the Sound Guys, but same problem.
Changing to other sequence settings didn't help. We tried Sony EX, uncompressed etc. Also looked at all render settings but our system is MacPro with 10GB Ram, so speak isn't the issue.
I then ended up importing it into Soundtrack Pro and output another AIFF 2ith 32bit floating point - problem solved. No its on duration and in Sync.
Cheers Alex

I'll run through it again along the lines you suggest. Hardware should be good enough. 15" Retina, i7, 16GB RAM, discrete graphics, etc, but I like the idea of copying the card completely. The drive I use is a G-RAID Thunderbolt striped as a 0, so yes, it's an external. Optimized media as Apple Prores 422 behaves just the same. When you view the waveform and the picture, single-framing through the clip, you see and hear they are not in sync.
Thanks, Ben. I'll report back. If your friend's works, it may be the camera. I have a case number with Panasonic in case that's possible, and I'll try an import into Premiere CC, though I don't use that personally.
(The DVX100 Audio Sync Tool was a thing, but it was a long time ago in a galaxy buried underneath our own. It came as an optional install on the DVD for FCP 4 for sure, but I may have used it with 3.0.)

Inconsistent Floating Point Math and NaNs on Windows Laptops?

All -
I am seeing some very strange inconsistent floating point calculations on Windows Laptops, and I am wondering if anyone has any ideas. Read on, as (to me!) it's very interesting....
I have attached a segment of our code, along with some sample output. Looking at the code and the output, it seems like it's totally impossible.
With supposedly non-NaN and non-infinite double values, I am seeing unrepeatable and inconsistent math - the below example only illustrates one such case where we're seeing this behavior.
If you look at the code below, you will see that I do things like:
double rhoYo = ... // some math
double rho = ... // exact same mathStrangely enough, I might get rhoYo = 1.51231231 etc and rho = NaN.
If I reverse those lines (vertically), then again, rhoYo comes out good and rho comes out NaN; however, this is unpredictable and inconsistent. If I project a source point, get a destination point with NaNs as a result, and project the source again, the second destination point may be just fine. Matter of fact, i can put a loop in the code such as:
      double rho = Double.NaN;
      for( int i = 0; i < 10; i++ )
        rho = my_earthRad * my_F / Math.pow(Math.tan(Math.PI/4.0 + latRad/2.0), my_n);
        if( ! Double.isNaN( rho ) )
          break;
        System.out.println("NaN'ed rho");
      }and rho will eventually become non-NaN (random # of iterations)!!
How's that possible? Our code might be tromping on memory somewhere, but this sure seems crazy to me, especially considering that
we're only using local variables. Anyone know of floating point errors on Windows Laptops?
With the exact same codebase, this behavior ONLY happens on Windows Laptops, including brand new Dells, old Dells, IBM, Intel and AMD chips (I've tried several ;-). It does NOT happen on Mac or Linux, including the Linux side of a Linux/Windows dual-boot (where it does happen with the Windows side). Even more strangely, it does NOT happen with Windows desktops. I have tried several 1.5.x JVMs, webstart vs no webstart, etc, to no avail. Always and only on Windows Laptops.
Please help.... ;-) and thanks in advance.
Sample code:
public class Projection
protected Point2D.Double _project(Point2D.Double srcPt, Point2D.Double dstPt) {
    final double my_degToRad = Math.PI / 180.0;
    final double my_originLon = -95.0;
    final double my_originLonRad = my_originLon * my_degToRad;
    final double my_originLat = 25.0;
    final double my_originLatRad = my_originLat * my_degToRad;;
    final double my_stdLat1 = 25.0;
    final double my_stdLat1Rad = my_stdLat1 * my_degToRad;
    final double my_earthRad = 6371.2;
    final double my_n = Math.sin( my_stdLat1Rad );
    final double my_F = Math.cos( my_stdLat1Rad ) * Math.pow( Math.tan( Math.PI / 4.0 + my_stdLat1Rad / 2.0 ), my_n ) / my_n;
    final double my_rhoZero = my_earthRad * my_F / Math.pow( Math.tan( Math.PI / 4.0 + my_originLatRad / 2.0 ), my_n );
    if ( Double.isNaN( my_n ) || Double.isNaN( my_F ) || Double.isNaN( my_rhoZero )) {
      return new Point2D.Double(Double.NaN, Double.NaN);
    if( Double.isNaN( srcPt.x ) || Double.isNaN( srcPt.y ) )
        System.out.println("======= _project received a srcPt with NaNs. Returning NaN point.");
        Point2D.Double nanPoint = new Point2D.Double();
        nanPoint.x = nanPoint.y = Double.NaN;
        return nanPoint;
    if( Double.isInfinite( srcPt.x ) || Double.isInfinite( srcPt.y ) )
        System.out.println("======= _project received a srcPt with isInfinite. Returning NaN point.");
        Point2D.Double nanPoint = new Point2D.Double();
        nanPoint.x = nanPoint.y = Double.NaN;
        return nanPoint;
    // Inputs are lon, lat degrees.
    final double lonRad = srcPt.x * my_degToRad;
    final double latRad = srcPt.y * my_degToRad;
    final double theta = my_n * (lonRad - my_originLonRad);
    // One Std lat -- tangential cone.
    final double rhoYo = my_earthRad * my_F / Math.pow(Math.tan(Math.PI/4.0 + latRad/2.0), my_n);
    final double rho   = my_earthRad * my_F / Math.pow(Math.tan(Math.PI/4.0 + latRad/2.0), my_n);
    // Computes kilometers in lambert space.
    dstPt.x = rho * Math.sin(theta);
    dstPt.y = my_rhoZero - (rho * Math.cos(theta));
    // WANK - Here's the problem! These values shouldnt be NaN!
    if( Double.isNaN( dstPt.x ) || Double.isNaN( dstPt.y ) )
        System.out.println("======= A _projected dstPt has NaNs. Dumping...vvvvvvvvvvvvvvvvvvvvvvvvvvvv");
        if( Double.isNaN( dstPt.x ) )
            System.out.println("======= dstPt.x is NaN");
        if( Double.isNaN( dstPt.y ) )
            System.out.println("======= dstPt.y is NaN");
        System.out.println("======= my_stdLat1 = " + my_stdLat1 );
        System.out.println("======= my_n = " + my_n );
        System.out.println("======= my_originLonRad = " + my_originLonRad );
        System.out.println("======= my_F = " + my_F );
        System.out.println("======= my_earthRad = " + my_earthRad );
        System.out.println("======= lonRad = " + lonRad );
        System.out.println("======= latRad = " + latRad );
        System.out.println("======= theta = " + theta );
        System.out.println("======= Math.tan(Math.PI/4.0 + latRad/2.0) = " + Math.tan(Math.PI/4.0 + latRad/2.0) );
        System.out.println("======= Math.pow(Math.tan(Math.PI/4.0 + latRad/2.0), my_n) = " + Math.pow(Math.tan(Math.PI/4.0 + latRad/2.0), my_n) );
        System.out.println("======= rho = " + rho );
        System.out.println("======= rhoYo = " + rhoYo );
        System.out.println("======= Math.sin(theta) = " + Math.sin(theta) );
        System.out.println("======= dstPt.x = " + dstPt.x );
        System.out.println("======= Math.cos(theta) = " + Math.cos(theta) );
        System.out.println("======= my_rhoZero = " + my_rhoZero );
        System.out.println("======= (rhoYo * Math.cos(theta)) = " + (rho * Math.cos(theta)) );
        System.out.println("======= my_rhoZero - (rhoYo * Math.cos(theta)) = " + (my_rhoZero - (rho * Math.cos(theta)) ));
        System.out.println("======= dstPt.y = " + dstPt.y );
        System.out.println("======= A _projected dstPt had NaNs. Done dumping. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^");
    return dstPt;
}And here's the sample output:
======= A _projected dstPt has NaNs. Dumping...vvvvvvvvvvvvvvvvvvvvvvvvvvvv
======= dstPt.x is NaN
======= dstPt.y is NaN
======= my_stdLat1 = 25.0
======= my_n = 0.42261826174069944
======= my_originLonRad = -1.6580627893946132
======= my_F = 2.5946660025799146
======= my_earthRad = 6371.2
======= lonRad = -2.7564670759053924
======= latRad = 0.3730758324037379
======= theta = -0.4642057102537187
======= Math.tan(Math.PI/4.0 + latRad/2.0) = 1.4652768116539785
======= Math.pow(Math.tan(Math.PI/4.0 + latRad/2.0), my_n) = 1.175224090766834
======= rho = NaN
======= rhoYo = 14066.369269924155
======= Math.sin(theta) = -0.44771270676160557
======= dstPt.x = NaN
======= Math.cos(theta) = 0.8941774612481554
======= my_rhoZero = 13663.082491950498
======= (rhoYo * Math.cos(theta)) = NaN
======= my_rhoZero - (rhoYo * Math.cos(theta)) = NaN
======= dstPt.y = NaN
======= A _projected dstPt had NaNs. Done dumping. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

HI JSchell (and others?) -
I have created a simple example attached below, that when run repeatedly, does indeed generate spurious NaNs. I have made it as simple as possible. In the code, I use my own lon/lat binary data file, though I am sure any will do. Let me know if anyone wants that file.
So the deal is that (with my data at least) this program should never generate NaN results. And if one runs it 25432 (eg: random #) times, it wont, but then the 25433th time, it will create NaNs, etc. ie: inconsistent NaN math results.
As I said before, I have run this on old and new Dell laptops under Windows XP, using java 1.5_02, 1.5_04 and 1.5_08. The latest run was on a brand new Dell with a Intel Core Duo T2600 processor, running XP. If this is a result of the Pentium bug, one would think that would be fixed by now. I have NOT yet tested on AMD, though I will do that this afternoon.
Remember, this ONLY happens with Windows Laptops.
Any ideas anyone? Thanks in advance ;-)
Here's the code that produces spurious NaNs:
import java.awt.geom.Point2D;
import java.io.DataInputStream;
import java.io.EOFException;
import java.io.File;
import java.io.FileInputStream;
public class FloatingPointTest2 implements Runnable
private static final int NUM_ITERATIONS = 100000;
private double _degToRad = Math.PI / 180.0;
private double _originLon = -95.0;
private double _originLat = 25.0;
private double _originLonRad = _originLon * _degToRad;
private double _originLatRad = _originLat * _degToRad;;
private double _stdLat1 = 25.0;
private double _stdLat1Rad = _stdLat1 * _degToRad;
private double _earthRad = 6371.2;
private double _n = _n = Math.sin( _stdLat1Rad );
private double _F = Math.cos( _stdLat1Rad ) * Math.pow( Math.tan( Math.PI / 4.0 + _stdLat1Rad / 2.0 ), _n ) / _n;
private double _rhoZero = _earthRad * _F / Math.pow( Math.tan( Math.PI / 4.0 + _originLatRad / 2.0 ), _n );
private Point2D.Double _project( Point2D.Double srcPt, Point2D.Double dstPt )
    if( Double.isNaN( srcPt.x ) || Double.isNaN( srcPt.y ) )
      System.out.println( "FloatingPointTest2: received a NaN srcPt. Skipping." );
      return new Point2D.Double( Double.NaN, Double.NaN );
    // Inputs are lon, lat degrees.
    final double lonRad = srcPt.x * _degToRad;
    final double latRad = srcPt.y * _degToRad;
    final double theta = _n * ( lonRad - _originLonRad );
    double rho = _earthRad * _F / Math.pow( Math.tan( Math.PI / 4.0 + latRad / 2.0 ), _n );
    dstPt.x = rho * Math.sin( theta );
    dstPt.y = _rhoZero - ( rho * Math.cos( theta ) );
    return dstPt;
public void doTest()
    DataInputStream instream = null;
    int thisRunNaNCount = 0;
    Point2D.Double tempPt = new Point2D.Double();
    Point2D.Double dstPt = new Point2D.Double();
    try
      instream = new DataInputStream( new FileInputStream( System.getProperty(
        "user.home" ) + File.separatorChar + "lonLatBinaryData.bin" ) );
      try
        while( true )
          double lon = instream.readDouble();
          double lat = instream.readDouble();
          if( Double.isNaN( lon ) || Double.isNaN( lat ) )
            continue;
          tempPt.x = lon;
          tempPt.y = lat;
          dstPt = _project( tempPt, dstPt );
          if( Double.isNaN( dstPt.x ) || Double.isNaN( dstPt.y ) )
            thisRunNaNCount++;
      catch( EOFException e )
//        System.out.println( "End of file" );
      if( thisRunNaNCount > 0 )
        System.out.println( "thisRunNaNCount = " + thisRunNaNCount );
      instream.close();
    catch( Exception e )
      e.printStackTrace();
      System.exit( 1 );
public void run()
    doTest();
public static void main( String args[] )
    System.out.println( "Executing FloatingPointTest2." );
    for( int i = 0; i < NUM_ITERATIONS; i++ )
      FloatingPointTest2 test = new FloatingPointTest2();
      test.doTest();
}

HT1364 I used these instructions to move my i-tunes library to the external hard drive that two different home pc's access. My playlists do not show on both Is it possible to have one i-pod synch amid two different computers that use the same library?

I have a sole i-pod and two pc's, used the instructions for "iTunes for Windows: Moving your iTunes Media folder" in the hope that I could synch my one i-pod between two different computers that are sharing the same library. Is it possible to have two seperate computers that only share an external hard drive (one wireless, one not) ? When I am looking at a shared library should it appear the same on both machines (ie: playlists/ purchased list etc)?

If it is moved correctly, playlists will display on both computers and it should be possible.
Close iTunes.
Hold <SHIFT> and launch iTunes.
When prompted to create a new or open an existing iTunes library point iTunes to the iTunesLibrary.itl file on the external drive.
The entire library should now show up with all playlists and playcounts.
Do this on both computers.
Keep in mind that only one computer can access iTunes at a time, otherwise errors will occur when each computer attempts to write to or update the iTunesLibrary.itl file.
Syncing may work seemlessly with both computers, but honestly syncing is designed to work with one and only one computer.

Possible to have both HD and SD on same dvd?

Hi there.
I was wondering if it was possible to have both a HD1080i60, and a DVNTSC on the same dvd?
The DVD is a standard def dvd, but i would like to have a "Extras" section, which would include a couple of HD clips.
Is this possible?
Do i just need to make the HD seqeunces 16:9 ?
Any help would be greatly appreciated

rom content? what exactly does that mean,and how would i go about doin it?
I just want to have a bonus section on my dvd, that includes HD versions of edits that are SD letterbox on the actual movie.. So the whole point is to have a the bonus section show that those edits look like in actual HD, not letterboxed...
So is this possible?

PixelBender / possible to have optionals inputs ?

Hi,
i m just testing pixel bender and i 'd like to know if it's possible to set input image4 as optional argument (i didn't see that in pixel bender's doc).
The effect i want to have is to composed an output from multiple sources ( couples of RGB + z-depth corresponding).
If i can't define optional input, i'll need 2 effects, one to compose a bitmap from 2 couples of sources and another to make a new z-depth which will match my new RGB to be able to do mutlipass and i suppose that will be less performant.
If input could be an array of image4 that could do the trick too, but if i've understanded well that's not possible (only array of float available).
Any advices are welcome...
WanH.

thanks for your time ...That 's what I finaly did and it works well.Pixel Bender is a very usefull tool and I wait impatiently for next release.
Wan-H
Date: Mon, 3 May 2010 12:52:27 -0600
From: [email protected]
To: [email protected]
Subject: Re: PixelBender / possible to have optionals inputs ?
Sorry, Pixel Bender doesn't have a notion of optional arguments.
Totally understand what you are trying to do. You could do it as two separate kernels (one with three inputs and one with two inputs), which is how we'd do it, but also hear the request for an input which is an array of image4s.
Cool requests, we'll see what we can do.
thanks!
Kevin
>

SQL Loader and Floating Point Numbers

Hi
I have a problem loading floating point numbers using SQL Loader. If the number has more than 8 significant digits SQL Loader rounds the number i.e. 1100000.69 becomes 1100000.7. The CTL file looks as follows
LOAD DATA
INFILE '../data/test.csv' "str X'0A'"
BADFILE '../bad/test.bad'
APPEND
INTO TABLE test
FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"'
Amount CHAR
and the data file as follows
"100.15 "
"100100.57 "
"1100000.69 "
"-2000000.33"
"-100000.43 "
the table defined as follows
CREATE TABLE test
Amount number(15,4)
) TABLESPACE NNUT050M1;
after loading a select returns the following
100.15
100100.57
1100000.7
-2000000
-100000.4
Thanks in advance
Russell

Actually if you format the field to display as (say) 999,999,999.99, you will see the correct numbers loaded via SQL Loader.
null

Is it possible to have a floating point representation in an array in LabVIEW?

Similar Messages

Maybe you are looking for