Saved file size decreases with time

Hi all, 
I am using Data acquisition system with  rate 10000 and 1000 sample per channel (exist 4 channels) to acquire analog voltage signals to measure the amplitude in each channel.
Moreover the raw signals are saved as TDM file of 1 minute. The system is running continuously for one week. I noticed that after 3 hours the saved file size is decreased as a function of time.
The size starts with 50 MB/min and after 3hours it became 42MB/min, after 1 day became 11MB/min. That indicated the data was lost , please, what is my programing mistake.
Thanks
Solved!
Go to Solution.
Attachments:
Acquisition system.png ‏177 KB

From the State Zero code, there are several things that could be improved here.
1. You only need to create the task once before your main loop.
2. You probably do not even need the outter loop if you use the DAQmx Configure Logging like I have already stated.  And you can use properties to say how many samples to go into a file before moving on, so that part of your code is eliminated.
3. The display can just be a simple chart (it looks like you are probably already using a chart).
What is your chart history set for?  That could be causing your slowdown if there are too many data points.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

  • LPX file size grows every time I save (with almost no changes) - WHY?

    Hi all,
    I am just now starting to move from Logic 9 to Logic Pro X. I first imported a very simple file from logic nine as a folder project and did not import anything except the file.
    - Then, I immediately saved it.  took more than 30 secs on core i7 - why so long?
    - next I "saved a copy as" file 1a - file size 700k - nice and small.
    - that I loaded the first logic X file back in and muted a few things and saved again
    - I made some other very minor changes like muting and re-saved three or four times.
    Here is what is strange –
    Original file = 1 MB
    main LX file was 2 megs and each subsequent save gained about 1 MB each time I hit save! So, the final grew to 6 MB after just a few saves!
    I checked to see if there was some large edit history file I could purge – but it was empty because all I had done was change some mutes…
    Q: what is going on with this large file size growing every time I hit save without any major changes – I would like to know what's going on.

    It has to do with undo history, backups, and autosaves.  You can see these if you right click on the file and show package contents.  Explore in there and you should see these growing in the alternatives folder.  I would imagine there is kind of a limit to how many of these there are, but haven't looked to closely at it.

  • XML DB: As XML file size doubles validate time more than doubles

    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    We have default XMLDB install. I am using schemavalidate() to successfullly validate xml files against a registered xsd. For some reason as the files size doubles the time to validate the file grows at a faster rate than double? We wanted to generate approx 18MB files since they hold 5000 records. But as you can see it appears I would be better off generating six 3MB files instead. What init.ora or xdbconfig.xml parameter might I change to help out with behavior? Any other ideas of why this happening? Is this an example of "doesn't scale"?
    1.5MB 3 Seconds
    3MB 15 Seconds
    6MB 1 Minute
    12MB 6 Minutes
    18MB 16 Minutes
    Code is simple..
    procedure validate_xml_file (p_dir in varchar2, p_file in varchar2) is
    v_xmldoc xmltype;
    begin
    select XMLTYPE(bfilename(p_dir, p_file),NLS_CHARSET_ID('AL32UTF8'))
    into v_xmldoc
    from dual;
    v_xmldoc.schemaValidate();
    end validate_xml_file;

    If I take the clause off the end of the cview table this procedure does not work at all.. It fails at the schemavalidate call...
    Error report:
    ORA-19030: Method invalid for non-schema based XML Documents.
    ORA-06512: at "SYS.XMLTYPE", line 345
    ORA-06512: at line 26
    19030. 00000 - "Method invalid for non-schema based XML Documents."
    *Cause:    The method can be invoked on only schema based xmltype objects.
    *Action:   Don't invoke the method for non schema based xmltype objects.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Why does PDF file size increase each time I "save" tagging tasks?

    Why does PDF file size increase each time I "save" tagging tasks?
    Given:
    1) I'm running Acrobat Pro 11.0.07 (this is most current version)
    2) My file size starts at 750mb and ends up 15mb when finished tagging.
    3) Only certain documents experience this increase, i.e., no visible pattern of document characteristics
    4) PDF's are not full of images...in fact, mostly <H1> <H2> <H3> <P> <Figure> alt text, ect.
    5) Occurs with text PDF's and/or fillable forms (again, does not happen to all documents...only some)
    6) File increase occurs incrementally as tagging tasks are performed; i.e., each new save increases file size a few megabytes.
    7) Occurs whether I "save" or "save as"
    8) Difficult to optimize these files without corruption
    9) I'm running Mac OS 10.9.4 (this is most current version)

    Thank you so much for responding! I've been experimenting with the SAVE AS vs. SAVE for the past few days...and you are correct. It's funny because I've been tagging files for 2 years and never noticed this. Probably b/c I use both methods depending on the tagging tasks...some are more complicated than others and should not be overwritten. In those cases I SAVE AS new file.
    I love this forum...thank you again!

  • Getting adobe form file size at run time

    hi,
    ya i need the adobe form file size at run time. my requirement
    is to get xstring and file size of the adobe form. adobe form format is already in xstring format, but how to get the file size.

    Hi,
    try the following:
      DATA lv_file_content TYPE xstring.
      DATA lv_file_size    TYPE i.
      lv_file_size = XSTRLEN( lv_file_content ).
    This will give you the file size in Byte. For KB, just divide by 1024, and once more for MB.
    Kind regards
    Ole

  • HT1553 i am upgrading my 2008 macbook to an ssd drive and want to save my settings. how do i save then? I have my files backed up with time machine ,but dont want to restore all files ,as there might be some junk backed up too. Help will be appretiated

    i am upgrading my 2008 macbook to an ssd drive and want to save my settings. how do i save then? I have my files backed up with time machine ,but dont want to restore all files ,as there might be some junk backed up too. Help will be appretiated

    When you restore from a Time Machine back up you can pick and chose what is restored. It is not an all or nothing process. Nor do you have to do the partial restores all at the same time. If days after the first partial restore you find something else you want you can restore just that.

  • PDF file size grows each time form is saved (with no data changes). Why?

    I have an SAP Adobe form (PDF) and we are seeing a difference in the Save behavior between when it is viewed in Adobe Reader vs. the adobe plug-in(?) for Internet Explorer.
    When the form is viewed in Internet Explorer, every time the user saves the form the file size grows (even with no data changes in the form - i.e., open the form, hit save).  This is not true if the form is opened in Adobe Reader.
    The form in question has multiple pages but the only fields directly bound to the SAP source are a handful of identifiers (e.g., order number) and a dynamic table.  It appears from our testing that the more entries in the table when the form is created, the greater the size increase each time the file is saved.  The table length is not changed after the form is first generated.
    Is there a known difference in the behavior of Adobe Reader vs. the browser plug-in which would account for this difference?  Our users have Adobe Reader X installed on their machines.

    If this is an XFA form, as opposed to an Acroform, you should ask in the LiveCycle Desiger forum or a more relevant LiveCycle forum.

  • PDF file size grows with each save if .access property set on a field

    We are seeing an odd form behavior and have isolated the apparent trigger to something we are doing in the form script.  I'm hoping someone can confirm they see the same problem, details follow:
    We have a form generated in LiveCycle.  It contains a text field.  In the docReady event for that field we have javascript which sets the field to be readOnly (TextField1.access = "readOnly").  We reader extend the form so we can save it from reader and/or the plug-in/control which is used by a browser when reading PDFs.
    With that simple form, open the form via the browser (we've tested with both IE and Chrome) and without doing anything else, just save the form (with a new name).  When we do that, the saved copy of the form is significantly bigger than the copy we started with.  If we then repeat the process using the newly saved file, the third copy is bigger than the second.
    This file growth does not happen if you open the file in Adobe Reader (instead of in the browser).
    When we look at the file contents via a text editor, what we have found is that each save via the browser is tacking on a chunk of data to the end of the file AFTER the %%EOF mark.  This new section appears to be one or more object definitions and ends with another %%EOF.  The first portion of the file (prior to the first %%EOF) is identical in all versions of the file.
    If you take a copy of the file that has these extra section added, then open and save it in Adobe Reader, it eliminates those extra sections and you get a 'clean', small version of the file again.  So those extra sections are clearly erroneous and unnecessary.
    Another thing worth noting, we took the script for setting the field access property out of the docReady event and put it as the click event on a button added to the form.  If you then open the form, press the button and save it you see the file growth (but not if you don't press the button.)  So it doesn't appear related to the docReady event, or timing of when we set the access property of the field.
    On the small test form described above the growth of the file is around 13KBytes.  But in testing with our real forms we've found that the amount  of growth seems to be tied to the size/complexity of the form and the form data.  In our most complex form with multiple pages with hundreds of fields and a large amount of XML data (form size is 2+MB), we are getting a file size increase of 700KBytes on each save.  This is a therefore, a significant issue for us, particularly since the process in which the form is used requires the users to save it a couple of times a day over the period of a month or more.

    I would start by exporting the XML data from the form before and after it grows to see if it is the underlying data that is growing and where. Did you define a schema and bind your form fields to a data connection created from the schema? That is always my first step when creating a form. It makes for a smaller saved file not including multiple levels of sub forms in the data structure.

  • Fix file size of local time machine backup

    Hi all,
    I'm having an issue where after copying over Backups.backupdb from my 1.5 GB external drive to another iMac, it shows that folder as now being 6.27 TB. The local disk on the iMac is 1 TB.
    The resson I copied over Backups.backupdb to the iMac is that suddenly one day when connecting the external drive to my MacBook, (This external drive was used with the MacBook as a Time Machine backup) I was promted with a warning that there was a problem with the external drive and that I should copy the files over to another location and reformat the external drive. After copying over the files on the external drive to the iMac I then reformatted it.
    So, the issue is that Finder reads that the Backups.backupdb is 6.27 TB and I can't copy it back over to the newly reformatted external drive.
    If anyone has any insight, I would really apreciate it if someone could tell me if it's possible to:
    modify Backups.backupdb and it's contents sitting on the iMac to show it's actual file size, correct the permissions and extended attributes?
    copy over Backups.backupdb to the external dirve in some other way (I tried via Terminal but with no luck)?
    Thanks in advanced!
    Paul

    I had the same problem!
    Time machine folder was using around 230GB on a 1Tb disk space.
    Had to format the disk because Time Machine was stucked at "preparing backup" or something similar after 6 months without using it.
    But after transferring it's main folder to my desktop, it is now showing 1.6Tb size!
    I can't move it back to the 1TB disk after format and I as need to do a clean reinstall to my Macbook Pro HDit seems I will have to trash my Time Machine saved folder an loose all it's contents if I can not find a solution.
    Is there any fix?
    Or I just have to let go this folder?
    Even folders inside it, like documents or desktops from previous backups are huge in size!

  • Saving file size

    When saving a file in Photoshop the file size increases substantially.
    Is there a way to save or an option to turn on/off that would prevent this and save the file as roughly the same size?
    I know about web optimized and different saving methods. That's not really what I want. Often I open a file just to edit some minor detail and save, then I have a file that's 2 to 3 times larger just because it was opened and saved. I tried saving a file without editing it at all and the file size increased so I know it's something I'm doing/not doing in the saving.
    So what's the easy method I missed about saving in PS?

    JPG is a lossy compressed file format. Each save degrades the image. The degraded image will grow to have more and more noise and artifacts. The recompression/reinterpretation of the growing noise and artifacts will cause the file to grow in size with each save.
    Do not resave a JPG. A repeatedly saved JPG just turns to mush. JPG is an ideal storage format for a final image; not a working image.
    Work on a master file saved in a lossless format (TIFF/PSD/etc...) and then save a copy as JPG.

  • File Size - Photoshop With LR or Bridge

    When I open files from LR (Ctrl-E) in Photoshop, LR immediately creates a .tiff file approximately 5 times the size of the original DNG. Then it quadruples in size again when it is converted into a Smart Object.
    Here is what I did:
    From LR Ctrl-E (ProPhoto,.tiff,16-bit). In PS Convert to Smart Object. Save File and the size went from 9.73mb to 175.6mb.
    From Bridge, double click on the same photo. In ACR choose Open Object. In PS Convert to Smart Object. Save File and the size went from 9.73mb to 95.1mb.
    What is going on here? Is there some benefit to having files twice as big for what appears to be the same result in the image?

    I checked, both are 16-bit.
    It appears that an unflattened image processed from LR is much larger than when the same image is processed through Bridge. For example, a 9.5mb DNG becomes a 216.5mb image after Curves, Levels, and Unsharp Mask when processed as a Smart Object in PS. The same file processed with the same adjustments through Bridge is 139.4mb.
    Once the image is flattened, there is little difference in file size whether processed in LR or PS.
    For my work flow, it seems appropriate to commit to the adjustments, flatten, reduce the image size, and convert to 8-bit. The 216.5mb file then becomes a 5mb file. For the rare occasion that I want to reprocess a file, I just have to do it all over again starting from the DNG. This defeats the main benefit of being able to tweak the adjustments using Smart Objects, but my storage demands are greatly reduced.
    For those really rare times when I have a large investment of time adjusting an image, it makes sense to process is through Bridge and save the large file. However, I can see no benefit to opening such an image from LR and ending up with a file twice the size.

  • File size problems with a banner

    I'm working on a banner in Illustrator CS3. It is 2m x .88m (roughly 33.5inches by 79inches) at 300dpi.
    The banner is not complete and I can't save it as a pdf anymore for customer preview- it's too big. It also often reverts to overview and won't redisplay in preview.
    The file has a full size background based on a photographic collage made in photoshop. This was flattened and saved as a pdf to come into Illustrator. There are other photographic objects that have been cut out in photoshop and saved on a transparent background to be placed in Illustrator. All these files are linked not embedded. Some of these have a drop shadow effect. The AI is over 440meg!!
    I'll admit to being inexperienced with developing banners and posters this large. I'm sure I must be handling it all wrong. I know I can merge some layers but I'll lose my ability to move things around. I still need to add some photos over the top.
    I'd really appreciate some advice on handling a project this large. I'm sure it is possible, lots of people are having pop banners this size printed with photgraphic images.
    I'm working on 3.4gig pentium dual processor, 3gig RAM, running Windows XP pro.

    > He says it's probably better to build the whole thing in PS at around 150dpi
    Leonie,
    For future reference, it's a matter of common sense. Generally speaking, the larger the final output format, the lower the raster resolution. Think about it this way:
    Why are things printed big?
    Because they are viewed from a distance.
    Why is 150-300ppi the conventional-wisdom rule-of-thumb?
    Because 150 lpi halftone ruling is a very common halftone screen for process printing viewed at (at most) arm's length. 150ppi means that the square raster pixels are at least as small as the halftone dots, so their square shape won't be evident (in other words, you won't see "the jaggies.")
    Would a 150 lpi halftone screen be sufficient if the page was meant to be read by an ant? No. The ant is much closer. The ant would see a bunch of meaningless large circles. A much higher halftone ruling and therefore a much higher raster ppi would be required--but the page would be much smaller, too.
    So forget this nonsense about 300 ppi raster resolution being needed for everything in print. Consider the optical scaling factor of displays meant to be viewed from a distance. No one makes billboards using 300 ppi raster images printed at 150 lpi halftone rulings.
    JET

  • Saved files take a long time to appear on Server or Desktop

    We have a network of nearly 40 macs, Panther Server, mostly panther clients but the newer machines are on 10.4.
    All of the newer machines exhibit the problem in that files saved to the server or to the desktop take a long time to appear.
    It appears to be a refresh issue, as on the server other clients can see the file straight away and locally the files can be seen on the desktop via the terminal.
    Force quitting the finder forces the files to appear but this is not a solution.
    The clients which have the problem all run 10.4 and the Server is 10.3. The 10.3 clients do not exhibit the same issues.

    I have also seen this issue at one of my larger clients (50+ workstations).
    The issues seems isolated to 10.4.5 or higher. Our workstations with 10.4.2 did not exhibit this problem. It is not an issue with hardware (we have seen this on an iBook G3 and various G5 tower models). Nor does it appear to be server-related: we have seen the issue saving locally with no servers mounted. We have seen the issue when saving from Adobe CS apps, MS Office apps, and from system apps (like TextEdit). Deleting com.apple.finder.plist from the user's home Library and then relaunching the Finder gets relief for a short time but the problem returns soon after. plutil reports the file is OK. The volume directory is fine, the permissions check out, and caches have been purged, to no avail.
    Like you, summersault, I am able to see the saved file on the command line, and when my users Force Quit the Finder, the file appears. Other workarounds, like the Nudge contextual menu, do not work.
    I have submitted the error via apple.com/feedback and would encourage you to do the same.
    Anxiously awaiting 10.4.7...
    -B
      Mac OS X (10.4.6)  

  • Why are Preview saved file sizes so HUGE?

    We have a neat copier at work that will scan in a document and email the pdf to you. So I have a 100 page document that I scanned in 4 chunks that yielded 4 pdf files of about 2.5MB each. I opened the first in Preview and then dragged the remaining 3 files in to create my final 100 page document. When I did the Save command I was shocked to see the resultant file size came in at 27MB! I searched around the menus and tried a Save As and selected the option for just black and white. The file that was created when that command finished ended up being 67MB.
    Anybody know how I can just get the originally expected 10MB file size? Many thanks in advance.

    I just tried the Combine PDFs program and it also yielded a 27MB file size when the sum of all the input files was only 10MB. So now I'm really confused. If I had to take a guess, I'd say the pdf format supports some kind of compression and both Preview and Combine PDFs can read in compressed pdfs but can't write them. I still need to get down to the 10MB size (because I can't email the file 27MB size I ended up with) so I'm still looking for help.

  • Why can I only "Save as Other... Reduce File Size" a single time for an Adobe X file?

    We are struggling with our form editing in that anytime we make a change and save the file size is doubled.  As a work around we started using the ...Reduce File Size save as.   However, we can only use that once per file.    Some of our forms contain several hundred fields that are edited, with the behavior as is we cannot save our work as we go.  
    Reproduction Steps...
    1. Open a file in Acrobat X and note it's file size.
    2. Make any kind of change (our work is focued on View>Forms>Edit)
    3. Go to File > Save as Other... > Reduce Size PDF
    4. Set Version Compatability to 'Retain Existing' and Save
    5. File size should be very close to the original
    6. Open the new file
    7. Rinse and repeat steps 2 and 3
    8. Note  that when you go to try to Save as the new edit, the Save As Reduce size is grayed out and no longer available for seslection.
    Please help!!!!

    Just do a standard Save As. The problem is that Save includes the old and new. Save As deletes the old. Also, if you distribute the form it is locked from editing as I understand it.

Maybe you are looking for