Contribute to Open Source. Search issue labels to find the right project for you!

XML constraint file issues


I created a composite profile and exported as XML. I see a few issues: - I have two MSH segment contexts in my constraint file (the one from the composite profile and the one from the original conformance profile) - there is a conformance statement missing from my composite MSH (id = MSH_GU_FRU_1_2-5-1)

IGAMT screenshot of the “original” MSH image

The LRI-6 conformance statement is missing from the constraints associated with “MSH_GU_FRU_1_2-5-1”

Updated 26/06/2017 21:05

Problem with calibrations in 90X MC?


Dear @rekovic, @bundocka, @gomber

With Aaron we have observed a degradation of the tau and jets resolution in 90X.

We observe this running the following command: -s RAW2DIGI – -n 100 –no_output –no_exec –era=Run2_2017 –mc –conditions=92X_upgrade2017_TSG_For90XSamples_V1 –customise=L1Trigger/Configuration/customiseReEmul.L1TReEmulMCFrom90xRAWSimHcalTP –customise=L1Trigger/L1TNtuples/customiseL1Ntuple.L1NtupleRAWEMU –customise=L1Trigger/Configuration/customiseSettings.L1TSettingsToCaloStage2Params_2017_v1_9_inconsistent_mean –filein=file:…

The degradation is a factor 2 worse RMS when looking at the L1T(jet)ET/genJetET or L1T(tau)ET/recoTauET distributions, w.r.t. what we usually observe (e.g. in 2016 data or 80X MC). We see this degradation already before applying Layer-2 object-level calibrations (so looking at a clustering of the TTs sent by Layer-1). Deriving new Layer-2 calibrations for jets and taus does not seem to be helping.

We also observed the same problem with the RMS in unpacked L1 taus and L1 jets: 2x degradation of the RMS w.r.t. 80X and 2016 data. We also tested setting the Layer-1 HCAL SFs to unity, which in principle should create a further large degradation of the RMS. This led to neither a degradation nor an improvement of the RMS, which means the problem seems to be more profound.

We are currently testing the L1REPACK recipe to check if the RMS improves. Please note that while this might teach us something, we cannot use L1REPACK to derive Layer-2 calibrations (due to missing courtesy variables that are internal to Layer-2).

If you could have a look into what is going on, we would really appreciate it.

Cheers, - Aaron & Olivier

Updated 26/06/2017 17:28

Use CustomElements


Right now we don’t actually use the CustomElementRegistry, which is standard in the WebComponents draft. Technically none of the Yoru components are currently valid. Use this opportunity to completely rewrite the component instantiation system, it is badly designed and will get hard to maintain (it already is, even for me, who wrote it in the first place)

A better design in the ShadowMaker - Component couple would also fix the broken Preloader. Maybe just get rid of ShadowMaker alltogether, it should now have the responsibility to create shadows in the first place, Components should, as they own the shadowRoot.

Updated 26/06/2017 10:16

Add tests


This is like, super needed!! Unfortunately I’ve had quite some troubles with module imports in tests. Tried Jasmine, Mocha and Ava, not sure for which to go and how to configure the module resolution to work properly. Usually if I get the resolution to find the module I want to import, the module’s own imports fail since they are configured to work with the current Babel + Webpack configuration.

Updated 26/06/2017 10:09

Fix debug mode


Looks like changing dashboard access permissions work using groups etc., it has broken how debug mode is able to access the admin interface

Updated 26/06/2017 09:12

About the second phase of LNA


Hey @cdparra,

Hey Christian,

I talk with LNA and everything seems to be working well now except from the Etherpad. When I was talking about issues, It is more about design and the organization of the website, and that why I was telling you last week that we could talk about this later, it was not the most urgent at the moment. I saw that Melonnie send us a draft, I will make comment on this ! Sorry if there was some miunderstandings, it is my mistake :)

At the end of June, they will launch the second phase about deliberation. They are going to add new user. The list of the account that need to be create is in the attached files. Can you prepare those user account for the end of next week ? Also, we will have a meeting with LNA on the 10th of July, about deliberation and voting. Do you think it is possible to go through with you on what the platform offers during those steps.

  • [ ] I want to be sure that I can answer all of their questions, and the best way to do that is to talk to you. Do you think we can have a small online meeting (20 minutes) to review those steps next week ? It will be very nice of you 😊

We need your help to create new accounts :)

  • [ ] This one is urgent :

  • [ ] All the e-mail adresses that are in the attached files, for the beginning of July (let’s say for the 3 or4 :))

Autres membres CTS-1.xlsx

Updated 26/06/2017 16:11 1 Comments

.dll error upon launch.


I don’t know if this is a problem that is independent of your installer or just my machine. The only .dll in the folder after install is the openvr one. No fmodex64, no libmpg, no libsndfile. It’s calling for zlib.dll when I open it but after putting a copy of zlib.dll in the install directory I try to launch it and nothing happens.

I’ll try building from the source to see if it still happens…

EDIT: I’m on Windows 10

EDIT2: Okay, built from source, and I can’t get VR_MODE 10 to work. I tried other vr options, and they work fine (sbs etc.). I tried both changing it in the console with vr_mode 10 and with the launch option flag -vr_mode 10. With the launch tag it won’t load, when booting it recognizes my vive, but then crashes before the loading bar reachus full. And with the console nothing happens. Should I make this a different bug report?

Updated 25/06/2017 18:49 2 Comments

Phone Auth - It not that expensive. it's worth enough.


It not that expensive. it’s worth enough.

Prices are per successful verification.

On the Blaze plan, Phone Authentication provides a perpetual free tier. The first 10K verifications are provided for free each month. You are only charged on usage past this free allotment.

All other Firebase Auth features are free to use on all plans.

Updated 24/06/2017 11:21

Round off errors in data model 2->3 conversion


Some values end up with 15 decimal places but most don’t for some reason. Need to keep the original number of sig digits. This is urgent if you want to start the data base from scratch to fix it or not so urgent if you can craw the current data store and fix them.

Examples below:

tab ages age age_sigma age_unit citations location magnetic_reversal_chron method_codes sample site 16.72 0.105 Ma This study Pueblo Mountains C5Cr GM-ARAR-AP 03PM10C pm10 16.51 0.021 Ma This study Pueblo Mountains C5Cn.2r GM-ARAR-SC-1050 03PMA pma 16.72 0.14 Ma This study Summit Springs C5Cn.3n GM-ARAR-AP 03SS02 ss02 17.14 0.18 Ma This study Summit Springs C5Cn.3n GM-ARAR-AP 03SS09G-1 ss09 16.71 0.19 Ma This study Summit Springs C5Cn.3n GM-ARAR-AP 03SS09G-2 ss09 9.81 0.011000000000000001 Ma This study Summit Springs C5n.1n GM-ARAR-SC-10 03SS17A-o ss17 9.756 0.01 Ma This study Summit Springs C5n.1n GM-ARAR-SC-10 03SS17A-y ss17

tab contribution author contributor description doi id magic_version timestamp @njarboe @njarboe Upgraded to MagIC Data Model 3.0 by the MagIC Database Team 10.1029/2008GC002067 12463 3.0 2011-07-19T09:28:14.000Z

tab locations citations continent_ocean country elevation_high elevation_low geological_province_sections lat_n lat_s lithologies location location_type lon_e lon_w region scientists This study North America United States 1795 1653.0 Columbia River Basalt Group 42.089 42.085 Basalt Guano Rim Stratigraphic Section 240.541 240.53400000000002 Oregon Plateau Nicholas A. Jarboe This study North America United States 1628 1308.5 Columbia River Basalt Group 42.77169 42.76763 Basalt North Mickey Stratigraphic Section 241.70432000000002 241.70202999999998 Oregon Plateau Nicholas A. Jarboe This study North America United States 2336 1343.0 Columbia River Basalt Group 42.06293 41.91142 Basalt Pueblo Mountains Stratigraphic Section 241.31400000000002 241.26377000000002 Oregon Plateau Nicholas A. Jarboe This study North America United States 1843 1540.0 Columbia River Basalt Group 43.11242 43.10825667 Basalt Summit Springs Stratigraphic Section 241.75512 241.72974 Oregon Plateau Nicholas A. Jarboe

tab samples citations geologic_classes geologic_types lat lithologies lon sample site This study Igneous:Extrusive Lava 41.96818 Basalt 241.28107999999997 03PM10C pm10 This study Igneous:Extrusive Lava 41.876999999999995 Basalt 241.248 03PMA pma This study Igneous:Extrusive Lava 43.11234 Basalt 241.73002999999997 03SS02 ss02 This study Igneous:Extrusive Lava 43.109190000000005 Basalt 241.73859 03SS09G-1 ss09 This study Igneous:Extrusive Lava 43.109190000000005 Basalt 241.73859 03SS09G-2 ss09 This study Igneous:Extrusive Lava 43.1108 Tuff 241.74917000000002 03SS17A-o ss17 This study Igneous:Extrusive Lava 43.1108 Tuff 241.74917000000002 03SS17A-y ss17

Updated 23/06/2017 21:07

Annual depreciation are not working anymore


The annual period and linear depreciation option doesn’t create as many depreciations as wanted.



1- How to reproduce?

Input a fixed asset with 50 000 €, linear option and annual period. started_on 2017-01-01 and stopped-on 2020-12-31

2- What is really expected?

Having 3 depreciation instead of 1.

3- How to test it?


Updated 21/06/2017 13:45

Media cloning bug


When cloning an animal, the media entries are cloned, but the DBFS entries aren’t. This means that the media items point to the same DBFS elements and if the original animal is later removed, the clone is left with dead links for media.

The DBFS items need to be cloned as well.

Updated 20/06/2017 17:04

Cooling v Luminosity revamp, including bug in bound-free photon generation


We have discovered a major issue with bound-free photon generation, in that we currently use lum_fb as our “bound-free wind luminosity” – i.e., actual radiative energy emitted by the wind, but lum_fb is calculated from total_fb which gives a “bound-free cooling rate” – i.e. energy transferred from the thermal pool.

@kslong , myself and @Higginbottom are going to work to improve the code both in terms of clarity and commenting, but also we are generally going to distinguish explicitly between cooling rates and radiative luminosities. As a result, new variables are required in the geo and plasma structures, and we will probably n

The actual bug in bf photons will require that lum_fb gets the integrated bound-free emissivity from

A few examples: * lum_adiabatic should really be cool_adiabatic * lum_fb should give the radiative luminosity, cool_fb should give the cooling rate * lum_ff and cool_ff would be the same. It is not clear yet if we should have both variables in this case.

This work is being carried out in the low_temp branch. Nick is going to start working on the process of converting variables. I will be responsible for making sure everything works with macro-atoms. We should try and document here.

This is pretty much priority A for me Knox and Nick at the moment as it needs to be fixed before new meaningful science can be done.

Updated 23/06/2017 16:30 15 Comments

Le site est stable en production


Le site en production tombe régulièrement depuis quelques temps. Lors du développement des nouvelles fonctionnalités, l'erreur a été assez facile à reproduire, quasiment à chaque fois que le site redémarre suite à la modification du code.

Updated 19/06/2017 21:11

Export für Kurse Anpassen


Es gibt im Moment einen XML Export dieser passt jedoch nicht ganz genau auf unsere Bedürfnisse. Folgende Dinge sollten noch angepasst werden

Fehlende Felder

  • Kursniveau
  • Zielgruppe
  • Arbeitsweise
  • Umfang (ich habe duration gesehen aber das ist wohl etwas anderes)
  • Max. Teilnehmer
  • Anmeldeschluss
  • Kosten Teiln. Kt. ZH
  • Kosten ausserkantonal
  • Kosten Lernende
  • Meta Keywords für Web-Suchmaschine

Bitte um Ergänzung

  • Ich bekomme unter category/id eine Kategorie. Woher bekomme ich alle Namen zu diesen ID’s? Ich glaube es müsste pro Kurs wie zwei Kategorien geben. Zum Beispiel: “Berufsorientierte Weiterbildungskurse” und darin gibt es dann “Publishing, digitale Medien, Animation, BIM”
  • Ich bekomme unter sessions/sessions/venue/address/city einen Ort. Woher bekomme ich alle Namen zu diesen ID’s?


  • Die Felder Hinweisund Weitere Informationen sind im Export unter remark vereint. Bitte einzeln exportieren.
Updated 19/06/2017 13:16

Responsive for mobile users

  • [x] Tableau graph height
  • [x] Reduce hero title size
  • [x] Header menu font size
  • [x] Hero subtext background
  • [x] European cities icons adapted to mobile
  • [ ] Footer without columns
  • [x] Map settings on top
  • [ ] Map not scrollable for mobile
  • [ ] Map and cost graphs bigger handles for mobile
  • [x] Life cost graph smaller sizes
  • [x] Content width relative
  • [x] Content max-width
  • [x] Reduce map settings width
  • [ ] Section titles background and size
  • [x] Quotes
  • [x] Mad/Bcn boxes
  • [ ] Mad/Bcn boxes titles top margin
  • [ ] Images higher in mobile
  • [x] Social icons width
Updated 18/06/2017 20:12

ORDER region_topg and meta_topg working as region_top and meta_top


Differently from before, now ORDER region_topg and meta_topg do not perform correctly, as they work as region_top and meta_top

Expected behavior: From the documentation “The clause meta_topg (region_topg) implicitly considers the grouping by identical values of the first n − 1 ordering attributes and then selects the first k samples (meta_topg) or regions (region_topg) of each group.”

Using the following query: DATA = SELECT(cell == “Urothelia”) HG19_ENCODE_NARROW; THETOP = ORDER(composite, treatment_type; meta_topg: 1) DATA; MATERIALIZE THETOP into res;

I expect that samples are grouped by ‘composite’, whose values are: wgEncodeAwgDnaseUniPk wgEncodeOpenChromDnase wgEncodeOpenChromFaire and then the first sample (by treatment_type) in each group is selected. Thus, I expect in output 3 samples with ID = 966/968 to be selected for composite=wgEncodeOpenChromDnase ID = 1006 to be selected for composite=wgEncodeOpenChromFaire ID = 39 to be selected for composite=wgEncodeAwgDnaseUniPk Yet, currently only a single sample is given in output! (as it would be by using meta_top).

Updated 20/06/2017 15:48 3 Comments

Unable to create Points [Geodata]


<!– Thanks for reporting issues back to Spacialist! This is the issue tracker of Spacialist.

To make it possible for us to help you please carefully fill out the information below. –>

Steps to reproduce

  1. Create new point-object in map-view

Expected behaviour

New point should be created

Actual behaviour

Error: $points must contain at least two entries

This error message can be traced back to: /lumen/vendor/phaza/laravel-postgis/src/Geometries/PointCollection.php Line 23-24 (see as well PointCollection.php#L23)

Server configuration

Operating system:

Web server:


PHP version:

Lumen Version:

Spacialist version:

List of activated modules: <details> <summary>Module List</summary> </details>

Are you using external storage, if yes which one: local/ftp/aws/…

Client configuration


Operating system:


Webserver error log

<details> <summary>Webserver error log</summary> Insert your webserver log here </details>

Lumen log (lumen/storage/lumen.log)

<details> <summary>Lumen log</summary>

[2017-06-12 11:44:36] lumen.ERROR: InvalidArgumentException: $points must contain at least two entries in /var/www/html/spacialist/oasen/lumen/vendor/phaza/laravel-postgis/src/Geometries/PointCollection.php:24
Stack trace:
#0 /var/www/html/spacialist/oasen/lumen/app/Http/Controllers/ContextController.php(665): Phaza\LaravelPostgis\Geometries\PointCollection->__construct(Array)
#1 [internal function]: App\Http\Controllers\ContextController->addGeodata(Object(Illuminate\Http\Request))
#2 /var/www/html/spacialist/oasen/lumen/vendor/illuminate/container/Container.php(508): call_user_func_array(Array, Array)
#3 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(743): Illuminate\Container\Container->call(Array, Array)
#4 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(709): Laravel\Lumen\Application->callControllerCallable(Array, Array)
#5 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(683): Laravel\Lumen\Application->callLumenController(Object(App\Http\Controllers\ContextController), 'addGeodata', Array)
#6 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(645): Laravel\Lumen\Application->callControllerAction(Array)
#7 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(625): Laravel\Lumen\Application->callActionOnArrayBasedRoute(Array)
#8 [internal function]: Laravel\Lumen\Application->Laravel\Lumen\Concerns\{closure}(Object(Illuminate\Http\Request))
#9 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#10 /var/www/html/spacialist/oasen/lumen/vendor/tymon/jwt-auth/src/Http/Middleware/RefreshToken.php(40): Laravel\Lumen\Routing\Pipeline->Laravel\Lumen\Routing\{closure}(Object(Illuminate\Http\Request))
#11 /var/www/html/spacialist/oasen/lumen/vendor/illuminate/pipeline/Pipeline.php(137): Tymon\JWTAuth\Http\Middleware\RefreshToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#12 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#13 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#14 /var/www/html/spacialist/oasen/lumen/vendor/tymon/jwt-auth/src/Http/Middleware/Authenticate.php(32): Laravel\Lumen\Routing\Pipeline->Laravel\Lumen\Routing\{closure}(Object(Illuminate\Http\Request))
#15 /var/www/html/spacialist/oasen/lumen/vendor/illuminate/pipeline/Pipeline.php(137): Tymon\JWTAuth\Http\Middleware\Authenticate->handle(Object(Illuminate\Http\Request), Object(Closure))
#16 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#17 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#18 /var/www/html/spacialist/oasen/lumen/vendor/illuminate/pipeline/Pipeline.php(104): Laravel\Lumen\Routing\Pipeline->Laravel\Lumen\Routing\{closure}(Object(Illuminate\Http\Request))
#19 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(780): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#20 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(626): Laravel\Lumen\Application->sendThroughPipeline(Array, Object(Closure))
#21 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(529): Laravel\Lumen\Application->handleFoundRoute(Array)
#22 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(783): Laravel\Lumen\Application->Laravel\Lumen\Concerns\{closure}()
#23 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(535): Laravel\Lumen\Application->sendThroughPipeline(Array, Object(Closure))
#24 /var/www/html/spacialist/oasen/lumen/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(476): Laravel\Lumen\Application->dispatch(NULL)
#25 /var/www/html/spacialist/oasen/lumen/public/index.php(28): Laravel\Lumen\Application->run()
#26 {main}


Browser log

<details> <summary>Browser log</summary>

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...


Updated 21/06/2017 13:22 3 Comments

wesnothd forum user handler does not support phpBB 3.1/3.2


The wesnothd forum user handler (both in 1.12 and master) does not support the new password hashing algorithm used by phpBB 3.1 and 3.2, and therefore fails to authenticate all users with the following error:

Even though your nickname is registered on this server you cannot log in due to an error in the hashing algorithm. Logging into your forum account on may fix this problem.

Users can still join the server but they are handled as if their account is inactive/non-existent, so they cannot claim ownership of their nickname or (in the case of server moderators) be automatically granted mod privileges.

This is a pretty serious issue as it’s setting back the upgrade process for the infrastructure right now. If fixed, it needs to be fixed both on 1.12 and 1.13.x/master even if 1.14 is released first until the 1.12 server average population becomes sufficiently low for it to be a non-issue.

Updated 22/06/2017 00:14 10 Comments

Add Event Calender Page


We want to add an event calendar page in the menu under My Dashboard. It would be called Event Calendar. It should be a calendar where I can go and edit events for photographers. If we can also send photographers notification when an event is coming up, that would be great. As we expand to other cities, there would be more than one calendar, so the calendars should be sorted out by cities. And photographers can open the calendar under their city.

Updated 06/06/2017 21:08

Implement Raw API


Just simple gets and inserts and updates to the db

User Accounts

  • [ ] Create
  • [ ] Archive (Flips a bool in the db, can’t login after set to true)
  • [ ] Ban – Think Of More

    groupFields Student

  • [ ] Set Schedule(new key: groupFields.schedule Will include student’s schedule

    groupFields to usergroups with pass groups assigned to them

  • [ ] Set Limit
  • [ ] Change Limit


  • [ ] Add New pass to DB
  • [ ] Cancel a pass (include who did it)
  • [ ]


  • [ ] Pass Tally to any pass group
Updated 06/06/2017 04:13

Fix some issues in my resume and website


Take into account some issues in my resume and website reported by a great manager:

You should try to get rid of the ellipses (“…”). They give a vibe of incompleteness, impreciseness and even sloppiness. In addition you should write out the first occurrence of every acronym where you can’t expect the average reader to be aware of its meaning (i.e. HMI).

While “Drag&Drop configurator for alarms” was always kind-of the internal terminology, a more accurate and understandable description would be “an interactive configuration program for an alarming solution using a drag & drop user interface”.

Updated 03/06/2017 13:36

Contact form for photographers


Hi Eugene,

Here are a few things that are not working about the contact form on photographer’s profile page. 1. date format. I entered 6/1/2017, it tells me it’s invalid. Can you use calendar on anywhere that needs to input date on the website? That will save a lot of time for our customers. 2. There is not enough information to actually book a photoshoot. Please create a big blank space titled Details. 3. When a customer fills out the contact form, where would this actually go? The photographer’s email on file or our file?

Updated 15/06/2017 18:50 1 Comments

L1T re-emulation on 90X MC does not get the correct HCAL TP Digis


@rekovic @bortigno

Using the standard recipe for L1Ntuples production: -s RAW2DIGI – -n 50 –no_output –no_exec –era=Run2_2016 –mc –conditions=auto:run2_mc –customise=L1Trigger/Configuration/customiseReEmul.L1TReEmulFromRAW –customise=L1Trigger/L1TNtuples/customiseL1Ntuple.L1NtupleRAWEMU –customise=L1Trigger/Configuration/customiseSettings.L1TSettingsToCaloStage2Params_2017_v1_4 –filein=/store/mc/PhaseISpring17DR/VBFHToTauTau_M125_13TeV_powheg_pythia8/GEN-SIM-RAW/FlatPU28to62HcalNZSRAW_HIG07_90X_upgrade2017_realistic_v20-v1/100000/004D4A52-A62C-E711-B518-848F69FD2853.root

I observed the HCAL TPs are empty, which in turn creates towers without an hadronic component. It seems L1Trigger/Configuration/python/ is not reading the correct HCAL TPs in 90X.

We tried to solve but did not manage. Can someone have a look?

Cheers, - Olivier

Updated 13/06/2017 13:20 15 Comments

Fork me on GitHub