Beste lezers,
Af en toe doe ik wel eens een paar uurtjes voor de lol met een contest mee, voor te loggen gebruik ik het programma van N1MM.
Morgen wil ik met de Black Sea Cup International contest meedoen, echter ik kan de contest in
N1MM niet vinden, als ik "new log in database" open zie ik deze contest er niet bij staan,
of kijk ik verkeerd.
Corné PA1CM
N1MM logger
Re: N1MM logger
6. I'm Missing My Contest! What To Do?
If the contest is not directly supported by the program there are two options:
1.Use a 'general' contest like DXSERIAL, DX etc. Run the contest and do the log creation after the contest using notepad or so. When Cabrillo is the log requested, create the Cabrillo log and update the header. The contest sponsor will calculate the multipliers and points.This is the way to go for the many small, mostly local, contests around.
2.Request that the contest becomes one of the supported contests by the program.
1.First, it would be good, whenever someone requests support for a particular contest, to have an indication of the number of entries the contest received during the previous year's running. I'm not suggesting a threshold below which contests will not be supported, but that knowing this is helpful in prioritizing for the people who do the work. In the past we have had requests to support contests that had fewer than 10 entries the previous year.
2.Second, it is part of the nature of the N1MM Logger project that users, and particularly those users requesting support for a particular contest, are the people who are relied upon to test and be sure the contest module does what it is supposed to do. It is particularly important in this context to test far enough in advance of the running of a contest so that any problems can be identified and fixed. So users will do well to check each contest as it is coming up.
3.And of course only when the programmer has time to create it! So do not ask days but better many weeks or months before the contest runs to have it implemented so there is time to create it and test it thoroughly.
If you identify bugs or propose contest-specific features during the running of a contest, don't expect them to be fixed immediately. Contest-specific things are on a calendar to be addressed before the next running. Of course, defects in Cabrillo output are an exception, since they need to be fixed for score submission and are can be done in the weeks after the contest.
If the contest is not directly supported by the program there are two options:
1.Use a 'general' contest like DXSERIAL, DX etc. Run the contest and do the log creation after the contest using notepad or so. When Cabrillo is the log requested, create the Cabrillo log and update the header. The contest sponsor will calculate the multipliers and points.This is the way to go for the many small, mostly local, contests around.
2.Request that the contest becomes one of the supported contests by the program.
1.First, it would be good, whenever someone requests support for a particular contest, to have an indication of the number of entries the contest received during the previous year's running. I'm not suggesting a threshold below which contests will not be supported, but that knowing this is helpful in prioritizing for the people who do the work. In the past we have had requests to support contests that had fewer than 10 entries the previous year.
2.Second, it is part of the nature of the N1MM Logger project that users, and particularly those users requesting support for a particular contest, are the people who are relied upon to test and be sure the contest module does what it is supposed to do. It is particularly important in this context to test far enough in advance of the running of a contest so that any problems can be identified and fixed. So users will do well to check each contest as it is coming up.
3.And of course only when the programmer has time to create it! So do not ask days but better many weeks or months before the contest runs to have it implemented so there is time to create it and test it thoroughly.
If you identify bugs or propose contest-specific features during the running of a contest, don't expect them to be fixed immediately. Contest-specific things are on a calendar to be addressed before the next running. Of course, defects in Cabrillo output are an exception, since they need to be fixed for score submission and are can be done in the weeks after the contest.
Wie praat luistert niet