Using :
VStar 2.15.1 (svn revision 984)
Mac Os 10.8.3
Java 7 update 21
Vstar works fine with New star From AAVSO Database.
But.
I can not open Apass or Bsm Epoch Potometry database files from Vstar/File (Plugins)
I get this error message from java consol:
-------------------------------------------------------------------------------------------------------------------------------
network: Cachepost not found [url: http://tombstone.physics.mcmaster.ca/BSM/conesearch_filter_cr.php?radeg…, version: null]
network: Connecting http://tombstone.physics.mcmaster.ca/BSM/conesearch_filter_cr.php?radeg… with proxy DIRECT
network: Connecting socket://tombstone.physics.mcmaster.ca:80 with proxy DIRECT
cache: http://tombstone.physics.mcmaster.ca/BSM/conesearch_filter_cr.php?radeg… is not cacheable.
java.lang.NumberFormatException: For input string: "The 'radeg' argument must be a valid number.<br />"
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have tried diffrent formats and diffrent Ra/Dec (in Deg) but the "The 'radeg' argument must be a valid number.<br />" pops up always.
I have tried to download direct from http://www.aavso.org/search-bright-star-monitor-epoch-photometry-databa…
and by saving cvs (Simle format) i can show that file in Vstar (using Open File) (i use same coordinates as accsess Bsm/Apass epoch database )
If i download APASS data from http://www.aavso.org/download-apass-data there is no simple format to download filedataas and they can not be shown.
So why cant I accsess Apass/Bsm Epoch Potometry database ?
Firewall on my MAc is WideOpen :) and i do get a socet connection in Java Consol too.
//Pierre
Hi Pierre,
You have been "caught" in the usual American-European formatting problem. Use periods in your numbers rather than commas.
Arne
Arne.
I already tried using . notation too.
If i look for ex R Leo in BSM database and put in these coo:
146.88954 11.42881
The output from java consol using . notation becomes
..................................................................................
network: Cachepost not found [url: http tombstone.physics.mcmaster.ca/BSM/conesearch_filter_cr.php?radeg=146,000000&decdeg=11,000000&raddeg=0,001000&filter=B, version: null]
network: connected http://tombstone.physics.mcmaster.ca/BSM/conesearch_filter_cr.php?radeg… med proxy DIRECT
network: socket://tombstone.physics.mcmaster.ca:80 med proxy DIRECT
network: Cachepostnot found [url: http tombstone.physics.mcmaster.ca/BSM/conesearch_filter_cr.php?radeg=146,000000&decdeg=11,000000&raddeg=0,001000&filter=B, version: null]
network: Ansluter http://tombstone.physics.mcmaster.ca/BSM/conesearch_filter_cr.php?radeg… med proxy DIRECT
network: Ansluter socket://tombstone.physics.mcmaster.ca:80 med proxy DIRECT
cache: http://tombstone.physics.mcmaster.ca/BSM/conesearch_filter_cr.php?radeg… is not cacheable.
cache: MemoryCache: removed entry http://www.aavso.org/files/vstar/vstar.jnlp
java.lang.NumberFormatException: For input string: "The 'radeg' argument must be a valid number.<br />"
..............................................................................................................................
Seems like my coo input gets trunkated.
And there is the , notation still in the output even that i am using . notaion
Strange.
I have tried to change the keyboard settings to American Keyboard too without any luck.
Pierre
Well I finally got it working.
I changed the system settings to use American Region
I then tried to input 146.88954 +11.42881 -no luck with american .
but using
146,88954 +11,42881 - works with , and American Region set.
So with European region set it doesnt matter whatever , or . you use - dosnt work
With American region set it works with european , but not with american .
So my bug report is to check the code (plugins for BSM/APASS ?) for using both american/European decimal.
/Pierre
Hi Pierre, Arne
Apologies for missing this one. Localisation is something I've paid a lot of attention to in the past. This is a somewhat different case. I have created a SourceForge ticket that describes the problem and the solution:
https://sourceforge.net/p/vstar/bugs-and-features/373/
As mentioned there, it will require a new VStar release (along with a rebuild and re-release of the 2 plugins).
Let me know if you can't view the ticket or if you have questions.
More later.
David
This bug has been fixed now and will be in a new release, early next week at the latest.
Thanks to Pierre for reporting and helping to confirm the fix.
David