Thesite is secure.
The ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
The aggregate germline classification for this variant, typically for a monogenic or Mendelian disorder as in the ACMG/AMP guidelines, or for response to a drug. This value is calculated by NCBI based on data from submitters. Read our rules for calculating the aggregate classification.
Stars represent the aggregate review status, or the level of review supporting the aggregate germline classification for this VCV record. This value is calculated by NCBI based on data from submitters. Read our rules for calculating the review status. The number of submissions which contribute to this review status is shown in parentheses.
The global minor allele frequency calculated by the 1000 Genomes Project. The minor allele at this location is indicated in parentheses and may be different from the allele represented by this VCV record.
The condition for the classification, provided by the submitter for this submitted (SCV) record. This column also includes the affected status and allele origin of individuals observed with this variant.
The submitting organization for this submitted (SCV) record. This column also includes the SCV accession and version number, the date this SCV first appeared in ClinVar, and the date that this SCV was last updated in ClinVar.
This column includes more information supporting the classification, including citations, the comment on classification, and detailed evidence provided as observations of the variant by the submitter.
The front fins of the NH-D15 generally protrude over the RAM slots. Due to the recessed lower fins, it is still possible to use RAM modules with up to 65mm height in single fan mode. In dual fan mode, the front fan will sit above the RAM slots as well. In this case, Noctua recommends using standard height RAM (up to 32mm). However, in chassis with more than 165mm CPU cooler clearance, the front fan can be moved upwards to make room for memory modules taller than 32mm (e.g. moving the fan 5mm up will increase the total height from 165 to 170mm and make room for 37mm tall modules).
Our case compatibility list helps you to quickly identify which PC cases offer sufficient clearance for which Noctua CPU coolers. The compatibility indication is based on the height of the coolers (including fans) as well as the maximum CPU cooler height specification given by the chassis manufacturer.
Caution: Please note that the fans of some tower coolers (especially larger models with 140mm fans, e.g. NH-D15 or NH-U14S TR4-SP3) may overhang the RAM slots and that this can cause compatibility issues if RAM modules taller than 32mm are used. While the fans can be moved upwards to increase RAM clearance, this will increase the total height of the cooler and thus requires additional clearance inside the chassis. As a rule of thumb, if the fan overhangs the RAM, the maximum CPU cooler height specification of the case must be at least the size of the fan plus the height of the RAM minus 7mm (accounting for the height of the socket and CPU). For example, if a cooler uses a 140mm fan that overhangs the RAM and 46mm tall RAM modules are used, the max. CPU cooler height specification should be at least 179mm (140+46-7=179). For further information and instructions on how to move up the fan for each cooler model, please click the height specification link.
Disclaimer: We create and update our compatibility lists with utmost care. However, case manufacturers sometimes change parts or details of their products without prior notice or explicitly indicating a revision. Therefore, Noctua cannot accept any liability, nor in any other way be held responsible, for the following compatibility information.
Can't find the case you're looking for? Please don't hesitate to contact our support team at
sup...@noctua.at in order to obtain compatibility information for cases that aren't listed above.
We do declare the average weight on nearly all of our products and we were doing the manual weight check by sampling 10 breads hour or per run (if run was shorter than 1hr). we then check the average per every 5 breads and do the rolling average for the next checks.
Following the bakers standard and EU weight legislation I have decided the weight checks must be increased to minimum 20 per run or 10 per 15 min (if run is longer). However, my staff is now struggling with manual weight calculations, because there is more to calculate than to pack. We have assessed the weeks worth documentation and we know that there is nearly no product which falls under declared weight. they happen occasionally once or twice within 24hr or not at all. I wonder then if I have to do the average check if all my checked weights are above the declared weight? the only thing i have found was:
The short answer is yes, because the overall average is what the regulatory body would take into consideration. If 9/10 make weight then the 1/10 is clearly an outlier and if say all weighed 10 kg (and 10 kg is your control limit) but the one was 9.9 kg you would be compliant. Of course make sure to take action when your set average checks consistently fail, which sounds rare.
1) How much "under" would make a difference to whether this is or isn't acceptable, as even if the average remains above the nominal weight, if the one errant result is too low then you'll potentially fall foul of the T2 limit.
2) There is a potential risk with fewer samples that one anomalous figure skews things in a direction that does not work in your favour. One T1 result out of ten samples gives you 10% T1s, which exceeds the 2.5% limit...
If it's the calculating rather than the physical act of weighing that is taking too much time, can you not make a simple Excel spreadsheet to do this for them, so they just need to enter the weight of each checked item and it does the rest?
Thank you for all comments. @pHfruit, yes, i did not consider the that 1 oos sample would give me 10% of t1s. I will incorporate this into the sampling procedure and if my runs are shorter (sometimes we pack 70 items of one product), we will have to check more if one falls under T1. . Looks like 40 products checked per hour permit 1 being T1. to stay compliant i must have max 2.5% T1 for the whole run of one product, which i am sure, I can provide.
I am also planning to take the average if at least one sample falls under declared weight, so I do not exclude averages totally. This exercise would be the assurance, that we provide stock above the average.
You may feel comfortable reducing the sampling frequency once you have plenty of data that demonstrates your process is routinely above the declared average - just expect it to be something that Trading Standards ask about as it's an easy one to get caught out on!
With the greatest respect, this is most definitely not the case for the EU/UK position.
I do not know what the equivalent regulatory requirement is in the US, but here it is intended to consider both the average and the distribution, or at least the part thereof that sits below the nominal average value.
Consider an example where one packs 1000 units of a product with a nominal weight of 1kg. If 999 of them have a mass of 1.01kg and one has a mass of 0.005kg, the arithmetic mean of the batch is 1.009kg, and thus it exceeds the nominal figure. Is the unlucky consumer that buys the pack labelled as 1kg but only actually contains 5g likely to be happy about this?
I would set up a specific weight parameter for each product. Each loaf, boule, etc. would only be allowed to be under weight by a certain percentage. Anything under the minimum weight would be rejected, and a larger sample size taken if multiple samples are under weight. If the product is underweight, but still within the allowable limit, then a specific number based on the sample size for the average weight.
So when the staff is taking samples, they can look at the chart, see that if the loaves should weight 1 kg and you take 20 samples, only 2 of them can be below 1kg, but still must be within 980g to pass the lot. (this was just easy math, you'll have to set up your own parameters based on regulations and a risk analysis for sample size)
3a8082e126