Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User setting of NULLCOST parameter #155

Open
nicolaslhuillier opened this issue Jun 6, 2024 · 0 comments · May be fixed by #159
Open

User setting of NULLCOST parameter #155

nicolaslhuillier opened this issue Jun 6, 2024 · 0 comments · May be fixed by #159

Comments

@nicolaslhuillier
Copy link

Describe the current behavior

The NULLCOST parameter prevents using cost values lower than its value. Currently this parameter is set to 0.5 (in order to avoid having costs set to 0) and it is not possible to modify it.

Describe the expected behavior

It should be possible to modify the value of the NULLCOST parameter via the DSL configuration file.

Describe the motivation

Currently if a user wants to set negative costs, this is not possible. Moreover, if negative costs are set, these are silently replaced by the NULLCOST value (though the ADEQUAOF et REDISPOF parameters are meant to deal with negative costs). Therefore the default value of the NULLCOST parameter should probably rather be set to negative infinity.

Extra Information

This implies modifying metrix DSL and generation of fort.json. Modification of metrix executable should not be required as this already seems supported (to be confirmed)

@marifunf marifunf linked a pull request Jul 12, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant