Since the vast majority of the insulating value of an IGU comes from the gas fill between the panes, and not the glass itself, I doubt iron free glass would make any difference in terms of energy efficiency. Thermal performance should be pretty much the same either way, unless the low-E coatings were affected in some way (which I think is probably unlikely).
I'm not sure you gain much for the extra cost here though. I'm used to iron free glass (Starfire) being used in aquariums where the glass is 1/2"+ thick, where you notice the greenish tint more. With the much thinner glass typically used for residential windows, I don't think there'd be much noticeable difference. I recommend you compare the two materials yourself before making the investment, to make sure you really do see enough of a difference to warrant the cost premium for iron free.
That 4% difference will affect the VT when using LowE coatings. Take for example a low iron glass coated with a triple silver LowE coating. While that coating would normally have a 66% VT when applied to standard float (in an IG unit), that same coating would have a 70% VT when using low iron glass. However even with the VT improvement when using low iron glass, that IGU would have slightly lower VT than an IGU using a dual silver layer with 72% VT. Granted the 72% would improve to 76% when using low iron glass.
The slightly greenish tint of standard glass is much more noticeable when the glass is viewed from the edge rather than the face, and as Bill Wichers pointed out, the slight green hue is more noticeable in thicker glass than thinner - thus the popularity of low iron in shower door and other more aesthetic applications that require glass that is thicker, but also clearer, than required in windows.
From a manufacturing standpoint there are reasons for either choosing sand with a higher iron content or adding small amounts of iron to sand that doesn't have the level of iron desired when producing glass. The primary reason is because standard higher-iron glass sand melts at a lower temperature than does low iron mix. Basically low iron glass takes more energy to produce making it a little less environmentally friendly and more expensive to produce than standard iron glass.
The window period refers to the time after infection and before seroconversion, during which markers of infection (p24 antigen and antibodies) are still absent or too scarce to be detectable. Tests cannot always detect HIV infection during the window period.
All tests have a window period, which varies from test to test. It also depends on the specimen that is being tested: window periods are usually reported based on a sample of blood plasma, but are longer when the specimen tested is fingerprick blood or oral fluid.
(Plasma is the colourless fluid part of blood, separated from whole blood using laboratory equipment. Fingerprick blood is produced by pricking the finger with a lancet, whereas oral fluid is obtained by swabbing the gums.)
It is hard to say exactly how long the window period lasts, as there are variations between individuals and it is a difficult topic to research (recently infected people would need to know exactly when they were exposed to HIV and then give multiple blood samples over the following days and weeks).
Nonetheless, a study by Dr Kevin Delaney and colleagues calculated window periods for a range of HIV testing assays. All these analyses were based on plasma samples. Window periods are likely to be several days longer when testing samples of fingerprick blood or of oral fluid, as will be normal when using rapid, point-of-care tests and self-testing devices. Unfortunately, precise figures for how much longer the window periods are have not yet been published.
A fourth-generation laboratory test is recommended in UK and US guidelines. It uses a sample of blood plasma or serum and can detect immunoglobulin G (IgG) antibodies, immunoglobulin M (IgM) antibodies and p24 viral antigen (a protein contained in HIV's viral core that can be detected sooner than antibodies). Commonly used tests of this type include Abbott Architect HIV Ag/Ab, GS Combo Ag/Ab EIA and Siemens Combo HIV Ag-Ab.
A fourth-generation rapid test is available (Determine HIV Early Detect or Determine HIV-1/2). While results for this assay when testing plasma were broadly similar to those of equivalent laboratory tests, the window period is likely to be several days longer when testing fingerprick blood, as the test is normally used.
A few third-generation rapid, point-of-care tests are available. They can detect immunoglobulin G (IgG) antibodies and immunoglobulin M (IgM) antibodies. Examples include the INSTI HIV-1/HIV-2 and Uni-Gold Recombigen HIV tests. The estimated window period for INSTI when testing plasma are as follows:
Third-generation laboratory tests are no longer recommended for use. They can detect immunoglobulin G (IgG) antibodies and immunoglobulin M (IgM) antibodies, but not p24 viral antigen. Their window periods are similar to those of the INSTI third generation rapid test (plasma samples), but a little shorter (median 23 days).
In HIV testing, the period of time after infection and before seroconversion during which markers of infection are still absent or too scarce to be detectable. All tests have a window period, the length of which depends on the marker of infection (HIV RNA, p24 antigen or HIV antibodies) and the specific test used. During the window period, a person can have a negative result on an HIV test despite having HIV.
No self-testing devices were included in this study. However, most self-tests are modified versions of rapid, point-of-care test kits that were originally designed for healthcare professionals. Most are based on second- generation tests, so are likely to have relatively long window periods. A few, including the INSTI HIV Self Test, are based on a third-generation test.
Similarly, self-sampling was not included. In the UK, this usually involve the user sending a sample of fingerprick blood to be tested in a laboratory with a fourth-generation antibody/antigen test. Plasma is extracted from the sample using centrifugation. In theory, the test will be as accurate with plasma from a self-collected sample of fingerprick blood as from venous blood, including in relation to acute (recent) infection.
Delaney KP et al. Time Until Emergence of HIV Test Reactivity Following Infection With HIV-1: Implications for Interpreting Test Results and Retesting After Exposure. Clinical Infectious Diseases 64: 53-59, 2017.
NAM Publications (known as aidsmap) is a charity based in the United Kingdom. We work to change lives by sharing information about HIV & AIDS. We believe independent, clear and accurate information is vital in the fight against HIV & AIDS.
Our information is intended to support, rather than replace, consultation with a healthcare professional. Talk to your doctor or another member of your healthcare team for advice tailored to your situation.
Every time I start up windows vista lately, I see a random floating window. It is a tiny little window with no title, and only the resize, maximize and restore buttons. I'd post an image, but I don't have reputation here yet.
I can close it, and it does indeed go away, but I would love to figure out what it is and stop it from popping up at all. I used Autohotkey's window spy on it and all I learned is that it is a swing window, which doesn't help me out a whole lot.
Use Process Explorer, it allows you to identify the window and then you can check the properties of the process to figure out the command line used. This command line will help you determine what exactly has been launched, this helps to figure out where Java applications and scripts are located...
Swing seems it belongs to JAVA. Look for a java(w).exe. You can also see what process it belongs to by using the task manager. Go to "tasks", right click the window and choose "switch to process", it'll show you what process it is.
I'm not too sure if this works for Java applications, but you can call up Task Manager, under the Applications tab, right-click Go to process, which highlights the offending process in the Processes tab. You can then kill it.
I have a popup taking the space & not reacting clicks, so ProcessExplorer was useless. WinLister listed all the windows with status (active/minimized), size, location - based on that info you could identify an offending app.
Google does not appear to have any authoritative links on the subject. Searching for the exact phrase + Javascript gives many results related to iframes and postMessage, but no precise description of what window.origin actually is.
Calling postMessage from a child iframe appears to result in the parent window receiving a message with the origin property matching the window.origin of the child frame - without allow-same-origin, it's null, otherwise it looks like it's the same as the window.location.origin of the child.
So here it has been determined that origin of the new browsing context is invocationOrigin, i.e the origin of the browsing context that did create frame, while url, used by location, is "about:blank".
Now the case of StackSnippets sandboxed frames is a bit particular in that they do have an src and thus a tuple-origin url, but since their sandbox attribute makes their origin opaque, they'll behave at the inverse of what is exposed in the previous example, making self.origin return "null" and location return the iframe's src's URL.
That file is quite big... The Window interface represents a window containing a DOM document; the document property points to the DOM document loaded in that window and describes several features common to the Window and WorkerGlobalScope.
You also saw that the window.location is less boring... as it contains some more data to it as the Location interface represents the location (URL) of the object it is linked to and the cool thing is that any changes done on it are reflected on the object it relates to. So that is why we don't get a null in here.
c80f0f1006