\nEach Brewer spectrophotometer communicates with a local PC where the raw data is stored. To upload the raw data from the client PC to the Eubrewnet database, a code written in Python 2.7 has to be set up in the local PC (or any other computer which has access to the Brewer raw data). When this code is executed the local (client) PC connects to Eubrewnet’s data server. Then, the local Brewer files and all related information (file size, modification date, etc) are compared to the data already stored in Eubrewnet. Only the files which are either new or have changed are then submitted. This process should be repeated at regular time intervals (~15 mins). \n<\/p>\n\n
\nThis post explains how to download and setup Eubrewnet’s client software in your local PC. We include here two Sections from Eubrewnet’s User Manual, which is available in full at http:\/\/rbcce.aemet.es\/dokuwiki\/doku.php?id=codes:usermanual&#eubrewnet_user_manual<\/a>. A Quick setup guide is provided in Sec. 1.1<\/strong>, and Sec. 1.3<\/strong> contains a FAQ<\/abbr>.\n<\/p>\n \nEither\n<\/p>\n\n \na)<\/strong> Download the client executable for Windows from http:\/\/rbcce.aemet.es\/eubrewnet\/static\/files\/client_exe.zip<\/a> or the experimental Linux static binary from http:\/\/rbcce.aemet.es\/eubrewnet\/static\/files\/client_linuxstatic.zip<\/a>\n<\/p>\n\n \nor\n<\/p>\n\n \nb)<\/strong> Setup the Python 2.7 interpreter in your computer, and then download the client Python script from http:\/\/rbcce.aemet.es\/eubrewnet\/static\/files\/client_python.zip<\/a>\n<\/p>\n\n \nCreate a new folder anywhere in your system and extract all the contents of the zip file there. Note that a new folder will not<\/strong> be created when you unzip the downloaded file.\n<\/p>\n\n \nDepending on the version of Eubrewnet’s software client, the files extracted will be\n<\/p>\n\n \na)<\/strong> for the client executable for Windows (Linux): \nb)<\/strong> for client Python script: \nOpen the \nWrite your Brewer ID number in the \nIn the \nIs your PC behind a proxy? If the answer is \nOnce you have finished editing the file, save it as \nIn the case of the client executable, in Windows just double click on \nTo execute the Python script, open a console\/terminal, change to your work directory, and use the command \nIn both cases, you should see some information on the screen, but note that the window might open and close quite fast if you double-clicked on \nTo save a log file, if using the client executable, run it from the console with the command \nWe recommend running the client automatically every ~15 minutes. In the case of Windows, look for information on the Windows Task Scheduler<\/em> for your Windows OS<\/abbr> version. For *nix systems, check the crontab<\/em> command.\n<\/p>\n \nQ<\/strong> What are the \u201cold\u201d and \u201cnew\u201d versions of Eubrewnet’s client?\n<\/p>\n\n \nA<\/strong> The first release of the \u201cnew\u201d version was distributed to a small group of beta testers on July 2019, and was then published on Eubrewnet for general use at the end of September of the same year. Compared to the \u201cold\u201d version, it features many improvements, including\n<\/p>\n \nMost important, Eubrewnet’s client will now write a lot of information to screen. This will help the user to understand what is going on and solve errors. This is also the most noticeable difference between the old and new version of the software: if you see a lot of text on the screen, you’re likely using the new client.\n<\/p>\n\n \nDespite all these changes, note that the old and new versions of Eubrewnet’s client software share the same code at their core, so you should be able to use either version to submit your data without making any change to your \nQ<\/strong> Do you plan any further updates to Eubrewnet’s software client?\n<\/p>\n\n \nA<\/strong> Yes, in the near future we expect to release a Python 3-compatible version. Until this version is available, if your running a linux distro which does not include Python 2.7, please try to use the experimental linux static binary.\n<\/p>\n\n \nDown the road, we are also looking into other quality of life improvements, such as automatically writing a log file with all the on-screen information, as suggested by V. Savastiouk. If you have suggestions, remember that you can reach us at eubrewnet@aemet.es<\/a>!\n<\/p>\n \nQ<\/strong> During my trials I\u2019ve got an error: \nA<\/strong> Make sure you’re using Python 2.7 and not 3. A Python 3-compatible version of Eubrewnet’s client software will be provided in the near future. If you can’t install the Python 2.7 distributable in your Windows or Linux system, please try to use the Windows client executable and the experimental linux static binary, respectively.\n<\/p>\n \nQ<\/strong> We are using a unix database ourselves, so one possibility is to transfer the data automatically from that to your database.\n<\/p>\n\n \nA<\/strong> Eubrewnet requires the original Brewer files. Direct communication between databases is not considered at this moment.\n<\/p>\n \nQ<\/strong> What is the best way? Ftp is easy for us to implement via the built-in scheduler in Windows.\n<\/p>\n\n \nA<\/strong> There are no plans to allow submissions via FTP<\/abbr>. Please check the Quick guide above \u2013 we’re sure that you will find that Eubrewnet’s client is very easy to use and automatize. And if you have any problem setting up the software, don’t hesitate to contact us at eubrewnet@aemet.es<\/a>\n<\/p>\n \nQ<\/strong> Do we have to send data in real time or are you planning to start with data files from past years?\n<\/p>\n\n \nA<\/strong> On each execution, Eubrewnet’s client always checks all the files in the directory specified in the \nSo, if you have all your files (new and old) in a single directory, they will all be checked and submitted if they are not already in Eubrewnet’s database (or if they have been modified since they were submitted). \n<\/p>\n\n \nIf you have old files in a subdirectory, you can modify \nNewer versions of Eubrewnet’s client also provide a \nQ<\/strong> In case it would be real time data that you want, what would be the frequency at which we would have to send the data? (daily, weekly, monthly)?\n<\/p>\n\n \nA<\/strong> Eubrewnet’s data server is capable of processing your data in near real time, so you can submit your files as often as you like! We suggest running Eubrewnet’s client every ~15 minutes using an automated task.\n<\/p>\n \nQ<\/strong> We are very cautious with our Brewer computers and we (together with the IT staff from our institute) are not very keen to install something new on these computers.\n<\/p>\n\n \nA<\/strong> You are welcome to check the source code of Eubrewnet’s software client \u2013 just download the Python script version and inspect the \nIf you are worried about the possibility of getting your computer infected by a virus, please note that we run a virus scan on the executable version of Eubrewnet’s client before we publish it on the web. Nevertheless, you also have the option to use the Python script version of Eubrewnet’s client.\n<\/p>\n\n \nFinally, if for some reason you’re still not allowed to run the software directly on the local PC connected to the Brewer, we suggest that you try to share the data with another computer under your full control and run the software on it.\n<\/p>\n \nQ<\/strong> I just sent you data from my computer: did you receive it?\n<\/p>\n\n \nA<\/strong> You can check the data yourself. The easiest way is perhaps to check the color of your Brewer on the map at http:\/\/rbcce.aemet.es\/eubrewnet\/default\/index<\/a> \u2013 Green or yellow is OK.\n<\/p>\n\n \nAnother possibility is to use the \u201cFile Status Check\u201d tool available at http:\/\/rbcce.aemet.es\/eubrewnet\/files\/status<\/a>. A status value of 0 for your file means everything is OK.\n<\/p>\n\n \nAlso, please note that communication errors usually produce some messages in the output of Eubrewnet’s client. If you want to debug these messages, we recommend running the client redirecting the output to a log file: you just have to use \nFinally, please remember that you can always contact us at eubrewnet@aemet.es<\/a>\n<\/p>\n \nQ<\/strong> I have already sent data files. Now, how to send the calibration files that usually are in the \\data\\###\\ folder?\n<\/p>\n\n \nA<\/strong> Newer versions of Eubrewnet’s software client will automatically check all the folders ending in the Brewer ID number and located inside the one specified in the \nIf you’re using an older version of the software, you can temporarily modify your \nNote that Eubrewnet’s data server knows how to parse most files generated or used by Brewer instruments (and, if the file can’t be automatically parsed, it will remain in the server waiting for us to check it manually!), so please don’t hesitate to submit all the files you have!\n<\/p>\n \nQ<\/strong> My first attempt to send Brewer data finished with this error: \nA<\/strong> You can’t connect to Eubrewnet’s submission service.\n<\/p>\n\n \nPlease, try to contact the refresh service from a web browser using the URL<\/abbr> http:\/\/rbcce.aemet.es\/refresh\/xmlrpc\/<\/a> \u2013 you should get a message like this\n<\/p>\n \nIf you don’t get any answer from the refresh service, then your connection might be blocked by a proxy, please check with your sysadmin. Remember that if your computer is behind a proxy, your \nIf you’re not behind a proxy, a firewall might be blocking the connection. Please contact your sysadmin.\n<\/p>\n \nQ<\/strong> There\u2019s an error while running the client: \nA<\/strong> Most likely, the registration of your Brewer in Eubrewnet has not been completed yet. Please, contact us at eubrewnet@aemet.es<\/a>\n<\/p>\n \nQ<\/strong> My Windows computer is very old and I can’t setup the refresh client following the steps in the Quick Setup \u2013 help!!!\n<\/p>\n\n \nA<\/strong> If you have a very old Windows computer which can’t run the compiled .exe of the new version of the client, and furthermore can’t run the official Python2.7 installer to use the python version, try the following options, sorted in order of complexity:\n<\/p>\n\n \nEasiest)<\/strong> Try to use the .exe of the old version of the client, available from http:\/\/rbcce.aemet.es\/eubrewnet\/static\/files\/client_exe_2014.zip<\/a>\n<\/p>\n\n \nNormal)<\/strong> If you have an old setup of Python in your computer, try to use the python version of the old client, available from \nhttp:\/\/rbcce.aemet.es\/eubrewnet\/static\/files\/client_python_2014.zip<\/a>\n<\/p>\n\n \nMost difficult)<\/strong> Download the file \nhttp:\/\/rbcce.aemet.es\/eubrewnet\/static\/files\/Python27_32bits.zip<\/a>\ninstructions in the running_refresh_client.txt file included in the zip. In short, the zip contains a folder with the Python2.7 setup of a WindowsXP 32-bit computer, and you can you use it to run the python version of the new client (available from http:\/\/rbcce.aemet.es\/eubrewnet\/static\/files\/client_python.zip<\/a>)\n<\/p>\n \nQ<\/strong> My Linux distro does no longer include Python 2.7 \u2013 help!!!\n<\/p>\n\n
\n\n\n\n\n1.1. Quick setup guide<\/h2>\n
1.1.1. Download Eubrewnet’s client<\/h3>\n
\n\n<\/div>\n\n1.1.2. Unzip the downloaded file to a pre-existing folder<\/h3>\n
refresh.exe<\/code> (refresh<\/code>) and example_client.ini<\/code>\n<\/p>\n\nrefresh.py<\/code>, example_client.ini<\/code>, refreshdb.py<\/code>, util.py<\/code>, xmlrpcproxy.py<\/code>, log.py<\/code>, alive.py<\/code> (in total, 6 .py<\/code> files and 1 .ini<\/code>) \n<\/p>\n
\n\n<\/div>\n\n\n1.1.3. Configure the client.ini file<\/h3>\n
example_client.ini<\/code> file which was included in the zip. It contains the following lines\n<\/p>\n[global]\nbrewerid=157\nworking_dir=.\ninput=c:\\brewer#157\\bdata157\nservers=iberonesia3\nproxy=proxy.xxx.xxx:port\n\n[iberonesia3]\nurl=http:\/\/rbcce.aemet.es\/refresh\ndb=iberonesia3.db\nnoproxy=yes<\/pre>\n
brewerid=<\/code> line.\n<\/p>\n\ninput=<\/code> line, write the full path to the folder containing your B files.\n<\/p>\n\n
\n\n– No: then do not change the line noproxy=yes<\/code>
\n\n– Yes: change the line to noproxy=no<\/code>, and write the proxy’s address and port in the proxy=<\/code> line\n<\/p>\n\nclient.ini<\/code> in the same folder where refresh.exe<\/code>, refresh<\/code> or refresh.py<\/code> reside.\n<\/p>\n
\n\n<\/div>\n\n1.1.4. Execute the client<\/h3>\n
refresh.exe<\/code>, and in Linux run .\/refresh<\/code> from a terminal inside the refresh directory. \n<\/p>\n\npython refresh.py<\/code>. \n<\/p>\n\nrefresh.exe<\/code> in Windows. \n<\/p>\n\nrefresh.exe >client.log<\/code>. If using the Python script, use the command python refresh.py > client.log<\/code>\n<\/p>\n
\n\n<\/div>\n\n1.1.5. Create an automated task<\/h3>\n
\n
\n\n<\/div>\n\n\n\n\n1.3. Frequently Asked Questions<\/h2>\n
\n
input=<\/code> which includes the Brewer ID number at the end of its name is now also checked for new files<\/div>\n<\/li>\n<\/ul>\n\n
input=<\/code> has been added<\/div>\n<\/li>\n<\/ul>\n\n
\n
\n
\n
\n
client.ini<\/code> file.\n<\/p>\n
\n\n
\n\nSyntax error: Invalid syntax<\/code>\n<\/p>\n\n
\n\n
\n\n
\n\ninput=<\/code> line of your client.ini<\/code>\n<\/p>\n\nclient.ini<\/code>‘s input=<\/code> line and run Eubrewnet’s software once. \n<\/p>\n\n-r<\/code> flag to look for files in all the subdirectories hanging from the one specified in the input=<\/code> line. Just run the software with refresh.exe -r<\/code> or python refresh.py -r<\/code> to enable this functionality, but note that this might take a lot of time!\n<\/p>\n
\n\n
\n\n.py<\/code> files, no other files besides those are used to generate the executable version of the client.\n<\/p>\n\n
\n\nrefresh.exe > client.log<\/code> or python refresh.py > client.log<\/code>, depending on the package you donwloaded.\n<\/p>\n\n
\n\ninput=<\/code> line of the client.ini<\/code> file \u2013 just take a look at the information printed on the screen.\n<\/p>\n\ninput=<\/code> line and run the client once.\n<\/p>\n\n
\n\n xmlrpclib.ProtocolError: ProtocolError for rbcce.aemet.es\/refresh\/xmlrpc\/: 403 Forbidden<\/code>\n<\/p>\n\nError response\n\nError code 501.\n\nMessage: Unsupported method ('GET').\n\nError code explanation: 501 = Server does not support this operation.<\/pre>\nclient.ini<\/code> must include the line noproxy=no<\/code>, and the proxy’s address and port must be written in the line proxy=<\/code>\n<\/p>\n\n
\n\nxmlrpclib.Fault: (Fault1 : \u201c(type \u2018exceptions.AtributeError\u2019): \u2018NoneType\u2019 object has no attribute \u2018last_online\u2019<\/code>\n<\/p>\n\n
\n\n
\n\n