From 69913a3ecad7c5213012b758bd338c08fcbceafb Mon Sep 17 00:00:00 2001 From: AlexT1983 <126983397+AlexT1983@users.noreply.github.com> Date: Sun, 3 Nov 2024 10:32:16 +0300 Subject: [PATCH 1/3] Update Noise.c MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I think max of two FamTl и FamTu is more correct --- P372/Src/P372/Noise.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P372/Src/P372/Noise.c b/P372/Src/P372/Noise.c index b4c8aaa..24c693e 100644 --- a/P372/Src/P372/Noise.c +++ b/P372/Src/P372/Noise.c @@ -224,7 +224,7 @@ int Noise( noiseP->DlT = 1.282 * sigmaT; - noiseP->FamT = min(FamTu, FamTl); // Worst-case noise. + noiseP->FamT = max(FamTu, FamTl); // Worst-case noise. With the greater noise figure the greater noise power return RTN_NOISEOK; }; From 21e7f68a4e396b893aa1ccea16e1fb0d061eb2ca Mon Sep 17 00:00:00 2001 From: AlexT1983 <126983397+AlexT1983@users.noreply.github.com> Date: Sun, 3 Nov 2024 10:37:27 +0300 Subject: [PATCH 2/3] Update README.md Fixed description of ITURNoise arguments --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d67fee5..e492793 100644 --- a/README.md +++ b/README.md @@ -853,9 +853,10 @@ C:\>ITURNoise 1 14 1.0 40.0 165.0 0 "G:\User\Data\" 0 Argument 1 is an integer that indicates the month (1 to 12) of interest. In the example above the desired month is January. Argument 2 is an integer that indicates the hour (1 to 24) UTC at the receive point. In most cases this will require the calculation of the time UTC from the longitude at that receive point. In the example above the receive point is 11 hours (165? E/(15?/hr) ahead of UTC so to determine the noise for the 12th local time hour the 1st hour UTC is chosen. -Argument 3 is a float that indicates the latitude (degrees). In the example above the latitude desired is 40? N. -Argument 4 is a float that indicates the longitude (degrees). In the example above the longitude desired is 165? E -Argument 5 is a float that indicates the man-made noise which can either be categorical (0-5) or value of man-made noise in dB (represented by a negative number). In the example above the value 1.0 indicates that the noise category residential. The category codes appear below. +Argument 3 is a float that indicates the frequency (MHz). In the example above the frequency is 1.0 MHz. +Argument 4 is a float that indicates the latitude (degrees). In the example above the latitude desired is 40? N. +Argument 5 is a float that indicates the longitude (degrees). In the example above the longitude desired is 165? E +Argument 6 is a float that indicates the man-made noise which can either be categorical (0-5) or value of man-made noise in dB (represented by a negative number). In the example above the value 1.0 indicates that the noise category residential. The category codes appear below. code Noise Category 0.0 City From ca404be4092372fb0a5b2451c663451515f7d563 Mon Sep 17 00:00:00 2001 From: AlexT1983 <126983397+AlexT1983@users.noreply.github.com> Date: Tue, 1 Apr 2025 23:33:35 +0300 Subject: [PATCH 3/3] Update README.md ITURNoise() arguments 6,7,8 -> arguments 7,8,9 --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e492793..52889ca 100644 --- a/README.md +++ b/README.md @@ -866,9 +866,9 @@ code Noise Category 4.0 Noisy 5.0 Quiet -If argument 5 is give as a negative number, the man-made noise will be set to that value where the galactic and atmospheric noise calculations are not performed. This second mode is of little value for this stand-alone program, ITURNoise.exe, running, P533.dll. Overriding the P372 calculation is included here and is consistent with some analyses desired in ITURHFProp which also uses the P372.dll. -Argument 6 indicates the location of the required CCIR data files. The data file path must be given as a string enclosed in double quotes without trailing back slash. In the example above the location of the required CCIR data files are on drive C: in the directory Data, “C:\Data” -Argument 7 allows the program to provide return data from the P.372 calculation is several formats. The table below gibes the integer print flag codes. +If argument 7 is give as a negative number, the man-made noise will be set to that value where the galactic and atmospheric noise calculations are not performed. This second mode is of little value for this stand-alone program, ITURNoise.exe, running, P533.dll. Overriding the P372 calculation is included here and is consistent with some analyses desired in ITURHFProp which also uses the P372.dll. +Argument 8 indicates the location of the required CCIR data files. The data file path must be given as a string enclosed in double quotes without trailing back slash. In the example above the location of the required CCIR data files are on drive C: in the directory Data, “C:\Data” +Argument 9 allows the program to provide return data from the P.372 calculation is several formats. The table below gibes the integer print flag codes. code Print Mode No argument Prints detailed output to stdout 0 No output