labofsahil/github-event-dataset-2012 huggingface dataset:
Some combination of fields should be `unique`, no? Like for each combination of `sign` and `language` should only one entry exist? Check [unique_with](http://mongoengine-odm.readthedocs.org/en/latest/guide/defining-documents.html#field-arguments).
Don't hard-code this. Pass in your top-level variable.
I removed that line, we don't need different font for the textarea...
Dot at the end!
It is strange that `get_full_node_id` is in nodes, but `parse_full_node_id` is models.
Don't build HTML manually. Use jQuery. See how we are doing that for posts, for example. Or elsewhere. This is error and security prone (you are not escaping anything!).
You can pass this as an argument to the field above, no? Even just as a class?

`forms.IntegerField(required=False, initial=0, widget=forms.HiddenInput)`

This does not work?
Only `\n`. Is not enough? You can put all into one line.
Uh, why are there no spaces around `=`? Please fix also this. ;-)
Hm hm. :-0
OK, but still use FormView to use its workflow. ;-)

But you said that something does not work for you?
Actually, the mock instances are created by NSubstitute not Moq.
It's a bit too abstract for my taste, because it takes an `object`, but `NSubstituteBuilder` only makes sense for `Type`. Furthermore, this is in line with AutoFakeItEasy.
I think we should use `Precedence.Sequence`. For example, if verbatim target `10, 20` is expanded as array element,
```js
[a, b, c, verbatim]
```
becomes
```js
[a, b, c, 10, 20]
```
and it is invalid.
not sure about this fully qualified name
Should be ``null === $stepName``.
thank u. don't think about it. i'll do sending it only on vehicle.
Indeed it does.  Tried with pg-0.13.2 and pg-0.14.1.  Using Rails 3.2.8

    ActiveRecord::StatementInvalid: PG::Error: ERROR:  invalid value for
parameter "search_path": "unknown_schema"
    DETAIL:  schema "unknown_schema" does not exist


On Tue, Sep 25, 2012 at 12:56 PM, Bhavin <notifications@github.com> wrote:

> In lib/apartment/adapters/postgresql_adapter.rb:
>
> > @@ -88,7 +88,11 @@ def reset
> >        def connect_to_new(database = nil)
> >          return reset if database.nil?
> >
> > +        unless ActiveRecord::Base.connection.schema_exists? database
> > +          raise SchemaNotFound, "The schema #{database.inspect} cannot be found."
> > +        end
>
> Sure. Will do.
>
> Just curious, does this statement throw any error ActiveRecord::Base.connection.schema_search_path
> = "unknown_schema" when run from rails console?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/bradrobertson/apartment/pull/53/files#r1686437>.
>
>
``assertTrue``
Doing this should also avoid the need to check if properties is an object (see comment above).

Anyway, not a deal breaker. Having an automated test however is - so once you get that added I'll merge.
This part is where I copied from `/hibernate-ogm-ehcache/pom.xml` blindly and now realized that it doesn't do anything and it's not necessary. Yes,  the part doesn't have be there and can be removed. I'll delete the part and commit the change.
> So what is this Lucene?

don't think this is needed
Whoops. Thanks. I see I made the same mistake below as well.
`_before_search` may override default functionality and return something like `jsonify(['foo', 'bar'])` which would be a valid response. My thinking here was such response should be sent back without any further processing. But `if not proceed` would evaluate to `False` in this case and default processing would carry on.

Actually here I was thinking about _falsy_ values, like `[]`, `{}`, or empty string. Now I remember that view function has to return either a string or a tuple with response and status code, but anyway, empty string would be a valid result as well.
I'm not sure this would help much here, as we have no meaningful estimation of the max size of all section. If your shell was a browser, I would output an html table :)
Humm, it should not be needed to do this.
Working with package relative import doesn't work?
The order of the imports is not accordingly to the Style Guide.
Checking `ls` directly is probably the best way to do it, but I see of no instance where you would have GNU `ls` without GNU `dircolors`, and since we need to evaluate *~/.dircolors*, if present, just checking for `dircolors` removes one if statement.
check compliance with numpy doc format

```
m1_l: float
    Minimum value of the mean for variable 1
```
```
This is definitely not supposed to be a `<`, right?
Why do you use an underscore for the pysrc version?  I see that you also did that for _CppShear and _CppEllipse, although I hadn't noticed them before.  I'm not sure why any of these would be the desired class name in python.  Why not make them match the C++ class name like we do with everything else?
For this, I added an optional parameter for the weight field: `include_obj_var`, which defaults to False, but which the user can set to True to include the object variance in the calculation of the inverse variance.
Sorry for the delay!!

OK by me :)


--
Barnaby Rowe
Postdoctoral Research Associate

Department of Physics & Astronomy
University College London
Gower Street
London WC1E 6BT
United Kingdom

On 13 Aug 2012, at 18:34, rmandelb wrote:

> In galsim/base.py:
> 
> > +    -------
> > +    The DoubleGaussian is a GSObject, and inherits all of the GSObject methods (draw, drawShoot,
> > +    applyShear etc.) and operator bindings.
> > +    """
> > +    
> > +    # Defining the descriptors for storing object parameters
> > +    flux1 = descriptors.SimpleParam(
> > +        "flux1", group="optional", default=None,
> > +        doc="Flux for the first of the two Gaussian components of the DoubleGaussian.")
> > +
> > +    flux2 = descriptors.SimpleParam(
> > +        "flux2", group="optional", default=None,
> > +        doc="Flux for the second of the two Gaussian components of the DoubleGaussian.")
> > +
> > +    sigma1 = descriptors.SimpleParam(
> > +        "sigma1", group="optional", default=None,
> Barney is checking e-mail while he's away, so let's wait for him to respond. If he agrees, then I'll get rid of it on this branch (from galsim/, tests/, and examples/)
> …
> —
> Reply to this email directly or view it on GitHub.
> 
>
In short: yes, the descriptors survive changes to the `SBProfile` contained by the `GSObject`: the problem is that they are not necessarily a non-misleading description of the object (FWHM will be wrong after most transfomations, for example).  This is why I mentioned it above, but it would have been better to post how I thought to work around it!

My nascent and not yet fully-formed solution / suggestion was going to be to treat shears / transformations / dilations etc. differently to the initialization parameters I've currently been concerned with, and to store with each object a record of what transformations have been applied and in what order.  This could be as simple as an ordered list of transformations stored by each class instance, e.g.:
```
>>> gal = galsim.Gaussian(sigma=4., flux=30.)
>>> print len(gal.transformations)
0
>>> gal.applyShear(e1=0.5)
>>> print gal.transformations[0]
Shear(g1=0.267949192431, g2=0.0)
```
... Or something similar.

Contrary to the example above, the ideal way to do this generally might be by simply writing a unified `Transformation` class at the Python layer that is like an `Ellipse` but also stores rotations.  Each element of the `.transformations` attribute would then be such a class object, and this attribute would be automatically updated by use of `applyShear()` etc.

Finally, I would also alter the descriptor classes to make it the default behaviour to raise an `AttributeError` if the `.transformations` attribute was of `len()` > 0.  I had hoped that this would then allow me to uncomment the above, and would recover the former behaviour almost completely - I think it's easier than trying to calculate what an arbirtrarily-transformed FWHM becomes...


Alas, time, inefficiency and moving house prevented me so far from opening an issue to suggest this change, but having spelt it out here I might simply do it!  Before I do this formally, what would you think of the proposal above?
In the C++ wrapper code for `pysrc/Bounds.cpp` these arguments are still all lower case, as I think is still our general policy for python arguments (at least in the case of GSobjects.  Here I think it might be clearer to use these lower-case form arg names.
Is __all__ special? Because if it's not I wonder if doing two from foo import * causes it to be overwritten multiple times?
yes and no. To use the gem, you only have to have an access token. To get an access token you need oauth2 (or you can generate it through the UI). So in practice, you'll generally use the two together (the specs use them together, which is why is only required in development), but the gem doesn't strictly depend on it.
Phighcharts uses, or The Phighchart library
I suppose it's reasonable for large powers of 10 (not having to count the zeroes in 100000) is good. For 1000 I find it easier to to just read the number written out, and for 1300 there's no question. 

I think for large powers of 10 it has value, and where you draw the line of 'large' is preference.
@paulmillr 

Yeah just found that testing: `Uncaught TypeError: Number.prototype.valueOf is not generic`
So this is a "conventional" table, not an "Examples:" table for the scenario outline.
CSS variables like `$white` are not very useful. Maybe for easy ready, but not for a better maintainability.

You could create something like `$header-color`.
It seems dirty to have a hidden depedendency on RACK_ENV. Could we add another parameter to S3Helper.init() to control whether subdomains are used?
Was this causing a problem?
Changing src= on video used to not work, hence the hack. This has been fixed, so I moved the video element in the html file.
So for reference here is where https://github.com/PhoenixPilot/PhoenixPilot/issues/86 would alternatively generate the objects on the fly
The version of instantiate_collection() from Tim did not work for me.  I tried using it in isolation (replacing the version I had), and then also adding the other methods that Tim overrides, but still no luck.  Here is the type of error I ran into:

    /home/cwolfe/bundle-cwolferh-thor-cli/ruby/1.9.1/gems/activeresource-3.2.8/lib/active_resource/base.rb:1470:in `method_missing': undefined\
 met\
    hod `deltacloud_driver' for #<AeolusCli::Model::ProviderType:0x0000000207c2e8> (NoMethodError)
            from /home/cwolfe/rb/thor-cli/lib/aeolus_cli/common_cli.rb:91:in `block in provider_type_hash'
            from /home/cwolfe/rb/thor-cli/lib/aeolus_cli/common_cli.rb:90:in `each'
            from /home/cwolfe/rb/thor-cli/lib/aeolus_cli/common_cli.rb:90:in `provider_type_hash'
            from /home/cwolfe/rb/thor-cli/lib/aeolus_cli/common_cli.rb:80:in `provider_type'
            from /home/cwolfe/rb/thor-cli/lib/aeolus_cli/provider.rb:26:in `add'
            from /home/cwolfe/bundle-cwolferh-thor-cli/ruby/1.9.1/gems/thor-0.16.0/lib/thor/task.rb:27:in `run'
Please add curly brackets around the one-line block.
It's required in the interface, if you need want to allow it in the implementation, otherwise it would be incompatible declaration. I added it to the implementation.
Если это функция назови с маленькой буквы. Конструктор с большой.
So uhh I can't pull this in until you give me a reason as to why we need a datetime argument, as well as why you are not attempting to detect this instead of specifying Paris time.
if someone's going to go to the extent of making a jar, how much more effort is it for them to simply just write a plugin, hook in, extend the Spell class and add it that way?
Well this is a locator variable, so in my opinion you're mixing intentions. Do you want to locate an element or do you want to verify that an element has an attribute matching a value? The following (untested) examples will do the latter:

    return '"bodyclass": "home"' in self.selenium.find_element(By.ID, 'page').get_attribute('data-context')

    return 'home' in self.selenium.find_element(By.TAG_NAME, 'body').get_attribute('class')

    return self.selenium.find_elements(By.CSS_SELECTOR, 'body.home') > 0

Also, using the body class would make more sense to me than what looks to be a meta tag in another element that relates directly to the body class.
Why don't we use the search term declared at the beginning? https://github.com/mozilla/marketplace-tests/pull/200/files#L5R16
We're not planning to do that at the  moment.
The only time we will test in a different locale is in the test that changes the locale. but even then it loads in en-US and then tests that it changes, rather than running the whole suite against it.
Assignment is assignment, always use a space.
Minor comments about docstrings: Remove blank lines between parameter definitions. Also, some of the indentation is a bit inconsistent in the definitions (some wrapped sentences are indented, some aren't); I'd remove the extra indentation. Finally, I generally avoid writing default parameter values in docstrings because it's already in the function signature (and they're often neglected if the default is changed).
I played around with the parameters passed to both `tv_denoise` and `denoise_bilateral`. The comparison between the two may be a bit fairer if you used the following:

```python
ax[0, 1].imshow(tv_denoise(noisy, weight=0.1))
ax[0, 2].imshow(tv_denoise(noisy, weight=0.2))
ax[1, 1].imshow(denoise_bilateral(noisy, sigma_color=0.05, sigma_range=1))
ax[1, 2].imshow(denoise_bilateral(noisy, sigma_color=0.10, sigma_range=2))
```

I noticed something strange during this comparison: `tv_denoise` seems to de-saturate the image. Just thought it was noteworthy (obviously, this doesn't affect this PR); I'm not sure if it suggests a bug.

Also, can you comment on the drastic difference in values of `sigma_color` and `sigma_range`?

I also tried this example using a grayscale image. I was surprised to find that `sigma_color` affects the denoised result. I haven't looked into this enough to know if that's expected.
My gut feeling is that `np.lexsort` is a better way of doing this, but it
remains to be checked.
forgot to change that - thanks for spotting
backslash. Try building the docs.
use assert_true rather than assert as assert can be disabled on some production python code.
отличное решение :+1:
Can't you use ```rake -f ${foreman::app_root}/Rakefile trends:counter```?
IIRC it preserves the relative path of the source files for the output directory. So it also works with `-Hd`.
Let's shorten the error message for the user:

```C++
    if ((f->mod & (MODconst | MODimmutable | MODshared | MODwild)) && !isThis())
    {
        OutBuffer buf;
        MODtoBuffer(&buf, f->mod);
        error("without 'this' cannot be %s", buf.toChars());
    }
```
int8 should be byte, etc. for the rest of the types. Use the D type names. In fact, use TypeBasic::dstring.
I fixed some identation problems on the files I modified. There a lot more around in the project.
bar-descriptor.xml file is also part of the structure. I'm thinking of blackberry.py not as new project, but project itself, which can render template upon request.
update API doc.
If we don't specify e.g. PICKER_TYPE_PLAIN, we get run time crash in case if java script contains that property.
For the PLAIN_TYPE, I'm gonna implement it in part 2
Plus nécessaire une fois que tu auras fait le changement du @ManyToOne
Une fois cette configuration effectuée, mettre à jour la configuration de
I didn;t mean move this code. I mean you need to add code there too. At present CMAKE_COMPILER_IS_CLANG will never be set, only CMAKE_COMPILER_IS_CLANGXX
Maybe, the function references almost equal number of members of owner as this though.
Ok, yes I see, so it will treat "thordata::regress" as relative tail dir name.

I looked/looks confusing because it's a scope spec. 
I would be better as just:

fdesc->setDefaultDir("regress");
Yes, true, should do, I'll change.
coco changes the behavior of `delete`, allowing to do `track.sc_id = delete track.id`
Is this ``var-`` thing a convention or something imposed by less? I don't really like it, I think the ``@`` is enough.
sorry when I wrote this I was just getting started with node
I know we discussed many times :)
But I'm not sure limpyd scode include this kind of abstraction: the lighter it is, the better it is. And so the closer to redis-py it is, the lighter it will be.
I'll not block this PR for this at all. But this should join the reflexion about making/keeping a light core.
Or could we make it an optional value, and use `ADMINS` by default?

The OAI-PMH app attempts to resolve this problem too:
https://github.com/mytardis/mytardis/blob/master/tardis/apps/oaipmh/server.py#L213

@steveandroulakis Maybe a common way to determine admins might be worth codifying? In this case, probably as a fall-back value.
I'm with @ralphschindler and @DASPRiD. I really see no reason to keep this is Stdlib. This is classic [YAGNI](http://en.wikipedia.org/wiki/You_ain%27t_gonna_need_it).

Based on a quick grep, there's only a couple places in Zend\Mvc where this is even used within the framework, and I'm sure there's ways to work around it, or like @ralphschindler said, if it's absolutely needed, just do the iteration there.

In the case of the usage in this PR, I think @DASPRiD demonstrated with [PR 882](https://github.com/zendframework/zf2/pull/882) that this is really not necessary in a function like this, where it's better to simply check on each key individually. (Yes, it needs a better name than replerge.)
hdghdgfhdgfh
please don't use this. This is a good thing to have to limit the amount of code we import and don't use. not a big deal just moving forward I think we should not use this.
I know we can combine all of these in a one line script now but this makes it more clear of what is actually happening
will fail for xml_id starting with '-' or '+'
need to be stripped (as well as spaces) before calling `get_xml_id_or_raise`
Lightweight code review on a line can go here
style nitpick: i'd move this in by another level of indent
Info block needs a ```'Stance' => Msf::Exploit::Stance::Passive,``` to make this a passive module that runs in the background.
Would be a better idea to return nil, and check against nil on get_output calls
I don't see what would be the problem with that, after changing to:

<pre>
		if not res or res.body.empty?
			print_error("#{peer} - File not found or empty.")
			return
		end

</pre>

I put a not existent file and it works well:

<pre>
msf  auxiliary(symantec_brightmail_logfile) > set FILENAME /testnonexistent.txt
FILENAME => /testnonexistent.txt
msf  auxiliary(symantec_brightmail_logfile) > rexploit
[*] Reloading module...

[+] 192.168.1.199:41080 - Logged in as 'admin:symantec'
[-] 192.168.1.199:41080 - File not found or empty.
[*] Scanned 1 of 1 hosts (100% complete)
[*] Auxiliary module execution completed

</pre>
why @?
OK, thanks :-).
actually there is a problem indeed here. there is also getRouteByName(). that is easy to fix. but the route could also be fetched from the content in the DynamicRouter. 

also its kinda sucky in terms of performance

so a better approach would be to do this on write. however i dont really see a reliable ODM event to use here.

of course this could also be set manually. but then i would have to add the necessary logic to both the admin class and the create rest controller.
I'd say "non-Rails-related code" instead of "plain ol' Ruby objects".
I assume this is to test the failure message - why not do:


```ruby
matcher = delegate_method(:deliver_mail).to(:mailman)
matcher.matches?(post_office)
matcher.failure_message.should == "Expected ...."
```

That way you're not using exceptions for control flow. The same applies for the next `it` block.
I'll have a look - this is a cleaner approach.
It could be 1 method but we could add another test in here to make sure the cache bypasses keystone when it goes down.
We're following the JPA here...
Hibernate does the same and it seems pretty valid for us, since is allows not only flexibility, but also reusability.
Just an after thought, if possible could we move the volume resizing tests to instance_actions.py. I should have put the test there in the first place. :(
This leaves currentTime at a meaningless value though. they're either going to have to specify it through the constructor or modify it after the constructor.
This should be moved up to the breaking changes in b10.
I suggest names of:
```
scene3D.boundingVolume
columbusView.boundingVolume
scene2D.boundingVolume
```
See the `Polyline` design before the `PolylineCollection`.  The idea is an object can have a default property (think material, for example) that can be over-ridden in 3D, Columbus view, or 2D if that property is also on the `scene3D`, `columbusView`, or `scene2D` objects.  Here, the default value isn't really needed I suppose.

I'm also open to other designs since we need to do more work on Columbus view.
I changed it to `widget.cbLighting.set('checked', true);` instead.  It's unfortunate that that turns off the sky atmosphere as well as the surface lighting, though.
Seems like overkill - is this leftover from when we were supporting 1.7 and 1.8?
The problem was that the previous example was wrong.

First off, because the offset applies to the buffer, not the stream. And second, because the stream isn't closed and reopened before the second read, so the second read should actually return -1.

I was trying to make the new example really clear about how offset and length are used, but perhaps I should reintroduce a simple example.
Technically, we'd known the simulator's also from Apple. Is this unknown for consistency?
isLayoutPass should be renamed here.
Shouldn't this be 'myAlertMessage' too?
The idea is to test against the latest (or current) SDK version.  The normal use case in mind was checking out a branch, working on changes, running anvil and them pushing changes back into git (the drillbit model).  I can see value perhaps in specifying a different version but should that be included as part of the hub push or a new PR for enhancements (which there will be)?
We should probably mention that 'undefined' is useful for the default bar color, and 'transparent' is the see-through black bar style.
So there are (or may be -- we don't actually know) modules out there which have their "source provider" class with only the non-arg method.
@etano Can you replace this with 3 equal signs? `===`?
First comment! Start it with a capital letter ;)
I see the case for encapsulation.  But since we are overloading SignatureType as an OAuth signature and an OAuth2 authentication we would have to add more behaviour to cover both cases and probably we don't want to clutter it with too much stuff.  So on balance I prefer to keep it as a low level simple data holder, but it's your choice.
clarify this docstrings, it's confusing

creation should work, running `eb.run_all_steps` should fail because `EasyBlock` is an 'abstract' class (although abstract is not exactly the correct terminology here)
Fixed in 08d0a16d0b43e0d16a94007f3e574376f75555a3
I've added themeroller to a bunch of $() selectors to limit its scope. Should I change them all to .find? Why find instead of the above?
Ну смёрдж в эту ветку мастер и поменяй.
Окей!
Seems this line is unnecessary.
better to serate with a blank line to separate declaration from the rest.
And this should probably be changed to something like.

> xsformat is a version of $(LREF sformat) whose behavior matches that of $(XREF stdio, writef). $(LREF sformat) will be changed to use this implementation in January 2013. In the interim, xsformat is provided for those who need the improved implementation. It will be scheduled for deprecation once `sformat` has been updated.
It may be what `Sequence` has on its actual `opDollar` at present, but `@property` makes no sense on `opDollar`, because `opDollar` is never called explicitly - either as a property or as a function. It wouldn't make any more sense to make `opDollar` a property than it would be to make `opEquals` a property. They're operators.
Instead of looping through each commit, checking it, and then appending to an array, you can use Array#select to pick out the files you want.

```
file_names.select do |file_name|
  files_to_watch.include? file_name
end
```
remove "(will be auto-generated)" from these comments?
`TestStageComputation`?
Maybe add `putAll` to `ExtendedJSONObject`, if it isn't there already?
Could we try to come up with some sort of filler for when nothing is selected?
Should be a different function name for the select map operator.  Should possibly rename the existing one to buildSelectNth().
the formatting of this array should not have changed
don't resolve it here. It makes no sense as the container does it anyway when needed.
I revert it for now however if we revert it, we should update the doc not to accept mixed. MQ issue 523 is filed.
You just need ```yield if video.now_playing?```.
don't do this, as the arguments passed through trigger must be an array, see .trigger() docs http://api.jquery.com/trigger/
Need to fix "is all the is"
Velvet is still listed as a build dep, it shouldn't be, see https://github.com/hpcugent/easybuild-easyconfigs/pull/52/files#r2357160 .

The easyblock also doesn't run `make` for Velvet first, and still sets `VELVET_DIR` based on the fact that Velvet is a build dep in the easyconfig...

Can you clean that up/fix that?
This class doesn't seem to do any validation. Actually even the write skew chek is not performed here, but further on the chain. Perhaps total order manager would be a better name?
You can apply `nothrow` to the whole module like you did with `extern(C)`.
Hmmm - I don't think we should copy the data into memory; why can't we copy from the sourceFileInputStream directly to the appendable FileOuttoutStream???
We believe that all the filters should be immutable, as a result, we are removing the setters.
There's no currentChar variable - you should probably define one, or replace with the full expression.
Oh, tabs are the style here? I will change it.
which threads do you think are involved? it's been a long time since I looked at the mcompositor source, but I don't remember seeing that many of them
Please move that to the previous line, and also add a space after the closing ).
Explains the change
self is for static methods but setRegion is not static
You can test internal stuff by adding an `InternalsVisibleTo` attribute to the assembly.  See Core/CustomAssemblyAttributes.cs in any Components branch for an example.  Note that for this to work, both assemblies must be signed, which ours currently are not (but arguably should be).

But at a glance, most of these methods seem reasonable to make public to me.  What's the concern?
Fixed next page to play ( if any )
I'm not sure, but since one can create a facebook account with any email address, wouldn't this allow any one to login to any account ?
I would assume if a property is null, you just don't add it
The words "the" and "an" appear together.
explained : this is the latest fix that Ayoola did to make the field "required" and display that error message on the form! :D
Yes. I've also worried about it. I added a new commit to avoid shallow copy in response to your comment.
0108c04
And, you reference "result" now, but does this match what's in the framework code?  Has the property there been changed from "return" to "result"?
comments? :-)
just $this->previous, yes ?
I was wrong, since this is only iterating through the final array (ie the array of listeners themselves and not the 3 dimensional one). It will be sequential and splice will be a better choice as it will not leave a gap
Или вообще detectOgg
this should be initialized using the typedef already defined
sorry, not this one, but the one at the root of the tree.
Czemu towar ma cenę? Chyba, że w każdym mieście cena jest taka sama.
I propose `Enregistrer et retourner à la liste`
Also (<= 13 age 19) :). The expression also returns a boolean.
Pas d'accord avec cette traduction. Le terme "commit" est encore pire que "build". Lorsqu'on parle d'envoyer les modifications au serveur de build, on parle (oui, ce n'est pas joli) de "committer".
Sinon, on voit parfois le terme "valider" comme traduction, mais je n'aime pas trop non plus et autour de moi en tout cas ce n'est pas un terme utilisé non plus.