bionhq.blogg.se - Condense log

Condense log archive#

This low steam turbine entry temperature (compared to a gas turbine) is why the Rankine (steam) cycle is often used as a bottoming cycle to recover otherwise rejected heat in combined-cycle gas turbine power stations. This gives a theoretical maximum Carnot efficiency for the turbine alone of about 63.8% compared with an actual overall thermal efficiency of less than 50% for typical power stations. Unless the pressure and temperature reach super critical levels in the boiler, the temperature range that the cycle can operate over is quite small: Steam turbine entry temperatures are typically around 565 ☌ and condenser temperatures are around 30 ☌. The efficiency of the Rankine cycle is limited by the high heat of vaporization of the working fluid. The greater the differential, the more mechanical power can be efficiently extracted out of heat energy, as per Carnot's theorem. The ability of a Rankine engine to harness energy depends on the relative temperature difference between the heat source and heat sink. Common heat sinks include ambient air above or around a facility and bodies of water such as rivers, ponds, and oceans. Possible heat sources include combustion of fossil fuels such as coal, natural gas, and oil, use of mined resources for nuclear fission, renewable fuels like biomass and ethanol, or energy capture of natural sources such as concentrated solar power and geothermal energy. The Rankine cycle closely describes the process by which steam engines commonly found in thermal power generation plants harness the thermal energy of a fuel or other heat source to generate electricity. 6 Variations of the basic Rankine cycle.2 The four processes in the Rankine cycle.#Files that have already been archived will be ignored.

Condense log archive#

Here's the current version of the script - in case GitHub ever becomes unavailable: #Sends $FileSpecs files to a zip archive if they match $Filter - deleting the original if $DeleteAfterArchiving is true. Mark Wragg's script should work if you don't care about these issues and you have Powershell 5, but it creates a zip for every log, which may not be what you want.

Do you want to preserve the relative path? Doing so will partially eliminate the problem of duplicates inside the zip file.

How many archives do you want to keep? I prefer one per run-month, adding new entries to an existing zip.

Will any error leave you with an unusable zip file? You need to Dispose() the archive to finalize it.

If unsuccessful due to a locked/missing file or very long path, should the process continue?.

Do you want to delete the original if it was successfully archived?.

Are the files created in a time zone with Daylight Savings? Zip format doesn't preserve that attribute, and may lose or gain an hour when uncompressed.

My script checks the file path and the archived file time stamp (+/- 2 seconds due to the lost date precision in Zip format) to determine if it's been already archived, and doesn't create a duplicate.

Did you know that you can have multiple copies of the same file in a Zip archive? It's harder to extract them because you can't put them in the same folder.Will any of the files be locked? CreateEntryFromFile may fail if so.

In months of testing a script developed for this purpose, I encountered some issues that have made this small problem more complicated: If you have an older version of Powershell you can use ZipFileExtensions' CreateEntryFromFile method, but there are a lot of considerations if you want a robust script that runs unattended.