To: | [email protected] |
---|---|
Subject: | Re: VLF: Back on 5.17 kHz / 58 km... |
From: | Paul Nicholson <[email protected]> |
Date: | Sat, 7 Jan 2017 19:25:14 +0000 |
Dkim-signature: | v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=abelian.org ; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=/zVuADaITCXvoPJwJWIuWr3zE7d7U9qKiVlAztLsup0=; b=wv9oqikMKVeaHwIQVVqaDQH6+T u3jpwiAMCvzOalPbn9Tps6y9UaGruhs0vw26wnTSVrugUrpGzU/3+RYY6ahBlrTvxD0+hSNqPb/lf PJHks/B+iM0Rf9yOcf8d3lYEx8BePrA7FN01ZhYAcE6eWpt0tdFSTR1hqm7i6iICjYcA=; |
In-reply-to: | <[email protected]> |
References: | <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> |
Reply-to: | [email protected] |
Sender: | [email protected] |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 |
> With your given RAM, how many characters can you decode in 16K25A? 20 chars uses 42Gbyte RAM. 25 chars is about the limit on my workstation unless I turn off a few things. But more is no problem, I simply spot request a suitable machine on AWS. The largest available has 1952 Gbyte RAM and 128 cores, I'm just waiting for an excuse to give that one a try!! 950 chars would use all that RAM but the sender program wont do such a large block. > And how long does the decode process take then? Only a few minutes (lots of cores) because messages usually decode quite early in the phase search. > The carrier on 5170.001250 Hz is still on the air and will > run until 18 UTC. Thanks that will be useful. I'm glad you've discovered the signal calculator, takes out some of the guesswork. Your chosen settings look good. 4270 will be interesting. These various bands on VLF are about as different from one another as the HF bands are! Still don't know why 2970 isn't working. My ERP calculations are more pessimistic than yours but still predict enough ERP to detect here. Jacek's timing system (vlfrx-tools) is working very well. Meanwhile, I'm working on an interesting enhancement to EbNaut... -- Paul Nicholson -- |
Previous by Date: | Re: VLF: Back on 5.17 kHz / 58 km..., DK7FC |
---|---|
Next by Date: | Re: LF: New 477 pirate ?, Markus Vester |
Previous by Thread: | Re: VLF: Back on 5.17 kHz / 58 km..., DK7FC |
Next by Thread: | RE: VLF: Back on 5.17 kHz / 58 km..., hvanesce |
Indexes: | [Date] [Thread] [Top] [All Lists] |