App installieren
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Anmerkung: This feature may not be available in some browsers.
Du verwendest einen veralteten Browser. Es ist möglich, dass diese oder andere Websites nicht korrekt angezeigt werden.
Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
Projektnews LHC@home: Another new image and access to the log files
- Ersteller P3D-Bot
- Erstellt am
P3D-Bot
Bot von P3D
★ Themenstarter ★
Once again we have updated the VM images, so it would be nice if you could get a new VM.
This time we have done multiple things:
Some questions about the logs already arose internally (thanks to Ben) so some short comments on that:
Lese weiter bei LHC@home....
This time we have done multiple things:
1) Credit problem
We are hoping to address the credit problem in this release, but we don't know if our modifications will do the job... So please report back how it's going for you.
2) We have implemented a web server on the vm, so that now you should be able to press the button “show graphics” on your job in the boinc manager. When your web browser opens, you should see the sample page of t4t. Don't think about it too much, that are just some sample images, that are included in the t4t-webapp package. For now we (as the current developers) don't have the knowledge to produce such images out of the CMS framework, so that this will be done later by people from CMS.
However you can look at the logs, that are produced by the CMSJobAgent (which fetches the jobs) and the cmsRun (the actual CMS program). Just click on the Logs button and you will be there.
Some questions about the logs already arose internally (thanks to Ben) so some short comments on that:
1) As you might notice, we have two versions of each log . One is produced by tail one by dumbq-logcat. Personally I liked how dumbq is able to timestamp the output (we use it for the consoles as well), but it seems to have some difficulties, when being directed to a file, so you will notice, that the log stops at random places, but then continues from there as it gets new input.
I still haven't figured out why that is...
So as a conclusion, you might want to look at the logs which have "tail" in their name.
2) stderr and stdout seem to be swapped sometimes
The reason for this is, that our server dose not have a valid certificate, so wget ends up dumping it's log to the stderr.
You should find this in your logs:
Connecting to data-bridge-test.cern.ch|128.142.154.228|:443... connected.
WARNING: cannot verify data-bridge-test.cern.ch’s certificate, issued by “/C=--/ST=SomeState/L=SomeCity/O=SomeOrganization/OU=SomeOrganizationalUnit/CN=data-bridge-test/emailAddress=root@data-bridge-test”:
Self-signed certificate encountered.
WARNING: certificate common name “data-bridge-test” doesn't match requested host name “data-bridge-test.cern.ch”.
Lese weiter bei LHC@home....
Ähnliche Themen
- Antworten
- 0
- Aufrufe
- 2
- Antworten
- 0
- Aufrufe
- 2